StarTrek.website is back online and has restored full functionality!
StarTrek.website is back online and has restored full functionality!
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!
Thanks for the hard work keeping things running!
I'm glad to have startrek.website as my home on lemmy.
And we're glad to have you!
"As I experience certain sensory input patterns, my mental pathways become accustomed to them. The input is eventually anticipated and even ‘missed’ when absent."
Thanks for doing what you do you beautiful bastards!
Seeing some of the wonky slowness just getting to communities for the first time. Really appreciate the heads-up/acknowledgment.
In the silver lining category, it’s been nice to see a few of the regulars here get set up on the fediverse sister platform Mastodon, especially on tenforward.social. There’re nice Trek folks there. Guinan is a gracious host and assiduous in her care to protect the instance from everything many of us we never wish to see or read.
Which brings me to the last point. Over at the ‘alternatives’ subreddit, there was a fair bit of discussion over the long weekend about illegal content and how instances can protect themselves from it federating to them. I hope that this migration hasn’t turned up too much stuff that the mods and sysadmins should never have to look at, and hope that the new home will help support better tools to filter that out.
Thank you all for all of your hard work. I missed StarTrek.website something fierce. I could ponder the ramification of how integral StarTrek.website quickly became in my life. Self-reflection and growth. Nah. I just kept reloading your feed to check for when the site was up again. LLAP.
Watching Star Trek counts as self reflection and growth, right?
...right?That's my story and I'm sticking to it.
It looks like ever since this maintenance, no kbin instances can get images from startrek.website:
https://kbin.run/d/startrek.website
https://kbin.social/d/startrek.website?p=3
https://kbin.cafe/d/startrek.website?p=3
https://fedia.io/d/startrek.website/newest?p=4(the links atm go to ~3 days ago when maintenance happened but ofc will start to drift as more posts are made)
You can see the thumbnails disappear exactly at the mark of the maintenance and ever since then they're gone. If you see thumbnails after that, they're usually wrong ones that are being loaded from different posts (there's a separate issue in for that now). I was wondering if you were aware of any issues or changes that happened because of this maintenance that would prevent kbin instances from fetching thumbnails? I've raised this in the kbin matrix chat as well
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
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 difficultThis 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.
