Yes! This worked! Thank you!
Yes! This worked! Thank you!
But then I wouldn’t be able to see photos on my instance. I want to see them, I just don’t want the federated cache being saved on my SSD.
That’s fine with me, as I’m the only user in my instance.
Though I do still think this is a huge miss on pictrs to not allow the admin to browse the photos stored on their own server. I mean, someone could upload an illegal photo, not post it, then send the URL that only they could possibly know to whichever relevant government agency anonymously and potentially ruin the life of the admin.
Thank you so much for contributing and making this much needed fix.
I actually thought of that. And it’s even hosted on sh.itjust.works via pictrs.
Awesome! Thank you for this link!
I agree! Or let us disable caching images from other instances. I’m not interested at all in rehosting images that other users on other instances upload. That’s too much of a legal liability to me.
I’ll try it out today. I’m about to start my workday, so it will have to be in a few hours. Fingers crossed I can have a PR in about 16 hours from now.
Thank you for this! Awesome work!
By the way, this looks easy to put in a container. Have you considered doing that?
Can you run lemmy without pictrs? What behavior is different?
I got lucky. I am not subscribed to this community, and I am the only person on my instance. But what if I was subscribed and hadn’t seen this post? This is too much responsibility for me.
I just shut down my instance until we can disable cached images. If that never happens, then I’m not bringing it back up.
Shout-out to https://github.com/wescode/lemmy_migrate. I moved my subscriptions over in a minute or two, and now, other than not having my post history, it’s exactly the same.
I’m a podman user, but what’s the point of using podman if you are going to use a daemon and run it as root? I like podman so I can specifically avoid those things.