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?

@eleitl@lemmy.ml
link
fedilink
English
401Y

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

Dandroid
creator
link
fedilink
English
221Y

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
link
fedilink
101Y

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

@eleitl@lemmy.ml
link
fedilink
English
3
edit-2
1Y

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

knoland
link
fedilink
71Y

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.

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
link
fedilink
21Y

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

Create a post

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!

  • 1 user online
  • 127 users / day
  • 422 users / week
  • 1.16K users / month
  • 3.85K users / 6 months
  • 1 subscriber
  • 3.68K Posts
  • 74.2K Comments
  • Modlog