Hi all. Due to the news of the illegal images being hosted on lemmy, I shut down my instance. I read some comments from people stating that they were able to selfhost lemmy without pictrs, they just can’t upload or cache photos. I think this is what I am interested in doing at this time.
I tried commenting out the pictrs section of my docker-compose.yml and removed the “depends on pictrs” sections. However, I get the error message in the attached screenshot when I go to my page.
Does anyone have any info on how to selfhost lemmy with image hosting completely disabled?
For now, you can just route /pictrs/ path to 404 so nginx won’t serve any image from pictrs:
location ^~ /pictrs/ {
return 404;
}
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| DNS | Domain Name Service/System |
| HTTP | Hypertext Transfer Protocol, the Web |
| PiHole | Network-wide ad-blocker (DNS sinkhole) |
| SSD | Solid State Drive mass storage |
| nginx | Popular HTTP server |
3 acronyms in this thread; the most compressed thread commented on today has 5 acronyms.
[Thread #91 for this sub, first seen 29th Aug 2023, 23:55] [FAQ] [Full list] [Contact] [Source code]
I wonder if you instead of disabling Pictrs you could just block image uploads to your Lemmy site, or maybe use a PiHole or Adguard on your network to block them.
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.
Wants to remove pictures from his own Lemmy, asks for help with that via picture on Lemmy
You could just set the upload limit to 1kb?
The caching is probably the problem, not the uploads on a personal lemmy instance.
I wrote a patch for Lemmy a week or so ago if you want to skip the caching: https://github.com/LemmyNet/lemmy/pull/3897
