Thank you for everyone’s patience while we were migrating hosts . I know I said “a few hours” and it turned out to be over a day. Clearly I need to work on my Scotty estimates. During transport the team found a backlog of extremely low effort memes caught in the pattern buffer and we had to go through the copies one by one determining which were the evil versions.
You may notice some wonkiness/slowness the next 24hrs as we get re-federated with everyone. Basically every other Lemmy instance will bombard us with traffic for a while.
Our new host is designed for Lemmy in particular, meaning in the long run we should see increased stability, improved load times, and better scaling as we inevitably become the dominant Lemmy instance!
There’s a known issue with any .website TLD, try adding this exception to your adblocker:
@@||*/pictrs/*$domain=lemmy.worldEDIT: It wasn’t this- the problem has been fixed
This isn’t really a me thing, this is kbin servers themselves. They all fetch the image from the posts and cache it to make thumbnails on their server which they host themselves. Ever since maintenance, the kbin instances appear to have trouble fetching the images to cache them. I’ll try to gather more data from instance admins, perhaps something changed with the request/response headers or something else that is causing them to get blocked.
Just to follow up on this, contributors to kbin investigated and found that startrek.website appears to block user agents that contain “curl” in it now.
Example:
curl -v --user-agent "curl" https://startrek.website/pictrs/image/3ff1b940-75da-4e6b-8948-834ebd4b454c.jpegtimes out while:
curl -v --user-agent "anything-else" https://startrek.website/pictrs/image/3ff1b940-75da-4e6b-8948-834ebd4b454c.jpegworks. kbin apparently sends
User-Agent: Symfony HttpClient (Curl)in its requests for images, which is different than how it handles other fetch requests. they’ve made a PR to change kbin to send the user agent it uses elsewhere in those image requests https://codeberg.org/Kbin/kbin-core/pulls/1098 once that is approved / merged they should start working again as instances update. It’d be nice if, assuming this is all accurate, the block on curl could be removed so people don’t have to wait for the PR / instances to update but I understand if that is difficultThanks for looking into this more! A fix is in the works.