• spiritedpause@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 year ago

    I get that the Lemmy devs are swamped with a lot of github issues, but how is this not one of, if not THE top priority for them right now? It’s mind blowing that instance admins don’t have the ability to disable the automatic caching of images from other remote instances.

    If any shit show instance that ends up having CSAM can then cause an admin’s instance to inadvertently cache/host that same content, why the fuck would anyone be motivated to host an instance and deal with the liability?

    • BlazeOP
      link
      fedilink
      arrow-up
      8
      ·
      1 year ago

      This is probably going to switch priorities

    • koper@feddit.nl
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Because people are blowing this way out of proportion. Users uploading illegal content is always part of hosting a platform and lawmakers realized this decades ago. Platform hosters legally cannot be held liable for the content of their users unless they have actual knowledge of specific instances of illegal content. This is both in the US (section 230 of the Communications Decency Act) and the EU (chapter II of the Digital Services Act, previously the eCommerce directive)