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
    arrow-up
    21
    ·
    2 years ago

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

    • Dandroid@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      10
      ·
      2 years ago

      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.

      • eleitl@lemmy.ml
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        2 years ago

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

  • Lung@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    2 years ago

    Yeah it’s been obvious and foreseeable that normal admins won’t have the bandwidth to handle takedown requests and cp spam attacks. Sadly the only stable state I see for the fediverse is relying on centralized content hosts that can handle those problems. Well, maybe until AI can do it