Jon, is there any possibility to check if this behaviour is still affecting you with gwibber 3.0.0.1? Thanks
Jon, is there any possibility to check if this behaviour is still affecting you with gwibber 3.0.0.1? Thanks