Apparently I was wrong, it’s decided it’s done and working again now.
Apparently I was wrong, it’s decided it’s done and working again now.
The pict-rs upgrade is ongoing.
From what I can tell it’ll be about another 5 hours. I’m going to have to go to bed and check on it in the morning.
Unfortunately the stock-standard lemmy-ui doesn’t like it that pict-rs is migrating to a new version of database and not serving images, so it’s stubbornly just not working at all.
Our best haj, Shonky (they/them) is available now, over at their own Github repository for use when referring to Blåhaj Lemmy.
I’m guessing we’ll need them to make an appearance for the Canvas template.
Not that I am aware of, and not that it’s not possible, but the protocols are quite different, the Lemmy API, the Misskey API (with various dialects for Sharkey, Iceshrimp and Firefish) and the Mastodon API (with Akkoma, Pleroma, etc) are all very different from each other and even making a third party UI that completely understands and implements a single API / dialect is an enormous undertaking.
Wow, okay that’s weird. It’s doing it for me too, must be some debugging option
I’ve been using alexandrite and haven’t noticed.
I’ll take a look tonight.
For a desktop client, it actually works pretty nice on mobile too.
okay, i’ll take a look… probably something to do with the media proxy or the pictrs config.
Yeah, you just need to login again and put in your totp code this time. Kinda annoying that it doesn’t provide a field for your totp code on the first page.
I also agree.
While I couldn’t care less (it’s their body and bodily autonomy is super important to me), I’d be a little hurt if they didn’t tell me about it.
In that case I’d be more interested in talking to my partner to try and understand why they felt that they couldn’t talk to me about it and needed to keep it a secret.
I asked my AI and that was its thought also.
So I’ve completed migration of the pict-rs server to our new infrastructure. I’m not sure what the issue was you were having, as I am unable to replicate.
Based on the father ambiguous error message, I presume it was returning a “Request timed out” or something.
Anyhow, after the migration, I’d be interested if you still see errors. Let me know.
Migration has been completed!
Fixed!
Okay, the new media cache server was locked up. Fixed the code and redeployed it. Images should come good after a page reload.
For transparency and posterity the maintenance log is here: lemmy-2023-09-03
Lemmy was running a bit slow on the new database due to too few slots in the pool.
I’ve increased and seems to be keeping up now.
The maintenance has completed and everything is now running from our new database.
Thanks for your patience while we performed this migration.
Poor li’l blighter got attacked by a bin chick’n and was limping away last we saw em… after goin’ the bin juice drinkin’ irrit of course.