Hello,
I’m hoping to take the instance to 19.4 in the near future.
Before doing this, I need to take pictrs up a few versions.
This will take a while, so while 19.4 is in the works, it won’t happen for a week or so.
Major changes in 19.4 (It’s a big-un, and should bring a fair few useful improvements): https://join-lemmy.org/news/2024-06-07_-_Lemmy_Release_v0.19.4_-_Image_Proxying_and_Federation_improvements
If there are any things in this list you’re curious about whether we’ll be implementing, ask away.
Cheers, GA.
I wasn’t aware there were big issues, thanks for letting me know.
The pictrs upgrade was expected to take a lot longer, so the plan was to put 19.4.1 on when released.
However, if there are issues at the moment, we can jump a little sooner. I just fancied avoiding some of the 19.4 bugs!
Friday, possibly? I don’t like to do upgrades unless I can clear several hours in case of shit hitting fan midway through!
I didn’t twig it might be upgrade related. I tried to mod an account on 0.19.4 and it didn’t federate back, and I’ve changed descriptions on communities on 0.19.4 and they aren’t federating back either (two different instances). Seems OK with 0.19.3 so I’m making a bit of an assumption that it’s the version mismatch, but I know Lemmy has had issues with federation across versions before. I can’t even force it to fetch a post on lemmy.dbzer0.com which didn’t federate. (https://lemmy.dbzer0.com/post/22446189 if you want to try - I search for it and it doesn’t do anything, whereas that would normally pull it down). I checked the blocked instances on all the servers and nothing relevant is defederated as far as I can tell.
Info is much appreciated!
Normally, if we had a report like this, we’d just shuffle forwards after running it in the test environment.
Unfortunately, as there is a DB engine change, I’m expecting all hell to break loose as soon as we start, so it’ll be a few days before I can put the time into it.
No worries, it’s definitely better not to rush these things!