this post was submitted on 29 Aug 2023
112 points (97.5% liked)

Selfhosted

39919 readers
231 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] eleitl@lemmy.ml 41 points 1 year ago (1 children)

Pictrs should have been an optional microservice by default. Commenting here to keep track of this thread since this is useful.

[–] dandroid@sh.itjust.works 22 points 1 year ago (3 children)

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.

[–] yukichigai@kbin.social 10 points 1 year ago

Same thinking here. Caching media pretty directly undermines any Safe Harbor protections you have running a site, not to mention the resource overhead required.

[–] knoland@kbin.social 7 points 1 year ago (1 children)

I don’t understand why lemmy caches photos in the first place? Like surely it’s quicker, easier, and lower bandwidth to just store a url to the original source.

[–] 0xc0ba17@sh.itjust.works 11 points 1 year ago (1 children)

Lower bandwidth for who? When images are cached on other instances, it allows two things:

  • Load sharing. The original instance doesn't have to serve the whole fediverse, but only its own users + 1 request per other lemmy instance.
  • Data availability through redundancy. If the original instance goes down, the cached image is still viewable on other instances.
[–] knoland@kbin.social 2 points 1 year ago

Bandwidth was the wrong choice of words. Storage space is more what I meant.

[–] eleitl@lemmy.ml 3 points 1 year ago* (last edited 1 year ago)

My primary consideration is all the expensive storage filled up by vapid image macros. 80 GB goes a long way for just text.