Hmm, something seems wrong with #qoto's performance for me today, it takes over 10 seconds to show anything but a blank page due to a failing request (status 503) to `https://miy.pw/css/12.css`? Same happened when I was earlier today on mobile network though I can't really verify it's waiting for that request there as well.
I'm not sure what that resource is for but since the page eventually shows up and seems fine, does DOM rendering really need to wait for that request to end?
@trinsec great, that solved it! Do you know if the ticker system is shut down permanently?
@JakubKuczys Unfortunately it is indeed shut down forever.
https://qoto.org/@freemo/109356114825991682
@trinsec hmm, in that case, does qoto plan to eventually remove those themes so that the users get automatically switched to a different theme?
@JakubKuczys Users who never had set the theme manually have their default theme already adjusted to one without tickers.
I think you probably had adjusted the theme yourself before, that's probably why you couldn't get moved over as easily.
As to the existing themes with tickers.. I think it's probably a good idea to eventually remove them, @freemo ?
🇳🇱
@JakubKuczys Yeah, it's been addressed before. :) You will need to change your theme to sometihng that doesn't include tickers. The ticker system is shut down and that's what causes all those hang ups.