You can hit ctrl + shift + j to load the error console to see if there are any errors for Twitter. Maybe one of the error messages will reveal something.

In the developer tools, you can switch to the network tab, check "disable cache", and hit ctrl + r to reload the twitter page to test if the network log shows any errors.

Also in the developer tools, you can hit the 3 dots at the top right, goto "more tools", choose "network conditions", turn of the use of the default user agent and then set Opera to identify as Chrome or Firefox. Then, ctrl + r to reload the page again to test if that helps.

You can also test with Opera's VPN on to test if that makes a difference.

@prunadesiempre it works if you log in

@DanRhodesC Opera GX is still based on Opera 68 and Twitter on sidebar was introduced in Opera 69.

@Seele4rum Hopefully they jump directly to v70, which has already been released for more than a week.

Would be nice for GX not to lag so much behind the standard version, when it comes to the core version.

@mstfsat Right, VPN gives you a different IP address and the traffic goes through the VPN server, so you can access blocked sites.

Got it.. but really miss it.

@Nickzin Please use English here.