Yeah you are right. It’s here: https://ani.social/pictrs/image/78d05797-5b02-4c5a-bd86-132f0f41856c.webp
Thanks.
a cool (brr) dude
Yeah you are right. It’s here: https://ani.social/pictrs/image/78d05797-5b02-4c5a-bd86-132f0f41856c.webp
Thanks.
I get it. Thumbnails are cached. Thanks.
As far as I know, images should not be federating to federated instances, right? Image proxying is supposed to be added to pictrs version 0.5.0 but it is still in alpha.
You’ll have to check again. My guess is though you should not have deleted the pictrs folders. Just its contents. You can recreate the folder again though:
mkdir pictrs
sudo chown 991:991 pictrs
But check the logs first.
pictrs from subscribed communities in other instances
Dont worry about those. Those images are not stored by your pictrs instance. They are directly fetched from the native instances.
pictrs database is completely separate from lemmy database. If you want you just delete everything in the pictrs volume and start afresh. You will lose all images though.
Seems like your pictrs database is corrupted.
You can still see the logs using docker logs container_name>
. To get the container name you can use docker ps -a
. It should list the pictrs container there. The container name is usually the last column of the output.
What do the logs say?
Not everyone can spend +1000 dollars on a computer.
barley came to work
I thought Stalin ate all the grain
you lose money regardless
Except Nintendo does not lose any money either way.
Have you tried checking the logs of the lemmy container?