I was gonna ask why images weren't showing and now I know. I wish you success in your administrative endeavors!
this post was submitted on 10 Feb 2026
71 points (100.0% liked)
Announcements
724 readers
1 users here now
For community-wide announcements, such as new subs, etc.
founded 5 years ago
MODERATORS
Me too.
Thx!
Hey, no sorries, comrade! This instance is an oasis in the desert, we are grateful.
I was wondering why Stalin abandoned me...
Good luck and patience with your work.
Re-uploading the profile picture is not working for me 😔 It still shows the broken-image-fallback.png
Seems like you maybe got it working, sry about that.
I had to upload a different picture. Not sure why it didn't work with my old profile picture.
The image uploading service (pictrs) has some deduplication feature. I am assuming it saw that the checksum of your image already exists in the database and just gave you an alias instead of storing the image your uploaded. Uploading a new image with a new checksum bypassed this feature.
Thank you for your work and dedication in managing this service.
Yeah something wrong
Thats unfortunate, I realise I no longer have my original profile image anywhere, guys I'll have to set aside some time to make a new one
The wolf with the hammer and sickle over it? Sometimes federation isn't super fast so I checked your user page via lemmy.ml and it's still visible there: https://lemmy.ml/u/commiewolf@lemmygrad.ml
On my end I can't see it. I use Lemmy off my phone, I wonder if there's got something to do with it.
Other instances have local copies of profile pictures, so anyone who hasn't changed theirs since the image issues began should be able to access it through lemmy.ml. You might need to edit the image slightly to prevent the de-duplication feature from triggering
Much appreciated
It's fine!
Are there any updates on how progress is going? I'm not exactly sure what the issue is, but I still see a bunch of missing images even from other instances, such as Hexbear emojis, for example. I'm not sure if they're cached, and the cached image is not available or what exactly.
Would appreciate a clarification :)
The old service let me know that there's no chance of re-opening it back up, so we're stuck with what we have unfortunately.
I'm not sure how to handle missing images, other than them needing to get re-uploaded.
That's unfortunate. But then what about the images from federated instances?
This is a screenshot of the !communism@lemmy.ml community from lemmygrad's side on a private session, so it's not browser cache on my side. These images should already be hosted on their side, no?
Its complicated but before we were using a local image mode setting, so its gone now.
helloite
is there a way to basically replace the files easier due to the most likely 3 image file rate limit? the rate limit never shows up with a sort of timer or anything so i never have a proper time posting images
is the host change affecting the very long rate limit that i usually get since i post many many images? i understand the change, don't get me wrong :thumbs up:
Its 3 per hour, it wouldn't be a good idea to change because image spam is a problem.
understandable reason, my gripe was that the rate limit never showed up nor with a timer. i do not have a github account (and frankly never will) so i cannot report this
this is genuinely good info to have, thanks a lot. i find it funny that i guessed the rate limit half-way
Rate limits are independent of the image storage backend. The rate limit for uploading images are probably a bit conservative.
ahh, so it's lemmygrad's config then. thanks