This was a major upgrade from lemmy 0.19.3 to 0.19.4 which upgraded postgres to 16. This also gives us federation to a few new 3rd party applications like Wordpress and also lets us have local only communities.
Clearly the image upload is broken, all I see is a QRP radio :-)
Seriously though, I feel your pain on the update and the process. I've not been game to even attempt to roll out an instance, let alone make it public and then go through the process of updating it.
One thing I did notice just then, as I was about to hit submit, there was a language pop-up at the bottom right of the textarea tht I'm typing this into, that wasn't set to anything. I've just set it to "English" for my reply.
Oddly enough, I think that’s supposed to not be set to anything. The way lemmy does language replies and filtering is kinda odd. If you set that to English, I think only people who have just English set can see or reply. Shrug
It seems like uploading animated .gif files may be currently broken. The server returns a 400 error with the message "Too wide".
Dunno if this was an issue before the upgrade, as I'm not sure I ever tried to upload a .gif file before; I usually upload .png files. Just wanted to give you a heads up either way.
Edit: And thanks for hosting this instance and putting in the effort to maintain it. I'm also happy to assist in any troubleshooting or other diagnostics that would help with its upkeep, should you want an extra set of eyes.
I’ll have to check if pictrs added some gif upload attributes to their settings. I think I remember seeing an option. I’ll try fixing this today!
Edit:
Yea it’s set to 256x256 max. Not sure what a great max size should be… I'll bump it to 512 for now, but we can always use external URLs as well that are larger.
Edit 2:
Bumped max size to 512 and removed pixel count all together. Tested below. If we need more than 512, we can bump it. Photo storage is sorta an issue but we should be good for a while.
Edit 3:
Also, it kinda sucks that lemmy-ui doesn't just bubble up that error in a toast or something. I get it on Voyager for iOS as an error "Image too wide/tall" or "Too many pixels" so I know it's in the response.
Hells yeah. Looks like the update fixed the issue with existing session cookies not always getting handled correctly in Firefox. A very nice quality of life improvement IMO