• eskimofry@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    4 months ago

    Probably arrange it such that not one person/server knows what the stored bytes are. There can be a server where the bytes/blocks get reconstructed where one can check for the bad stuff.

    • Skull giver@popplesburger.hilciferous.nl
      link
      fedilink
      English
      arrow-up
      2
      ·
      4 months ago

      I’m not sure if that makes it better. “I’m sorry officer, I have set up this elaborate cryptographic system to make sure I can’t see the files I host on my website” probably doesn’t violate any laws, but you’d better learn the phone number of a lawyer before you set it up.

      Standard encrypted-at-rest data is probably a better solution. You probably don’t want to go look for illegal content until you’ve read up on the laws of the country you’re hosting in and your own so you know what to do, and what is or isn’t illegal.

    • LostXOR@fedia.io
      link
      fedilink
      arrow-up
      2
      ·
      4 months ago

      That doesn’t solve the cost problem. Now all the traffic is going through that intermediate server, and someone has to pay for that.

        • LostXOR@fedia.io
          link
          fedilink
          arrow-up
          1
          ·
          4 months ago

          Still, hosting costs were the reason for discussing legal liability. Such a server also increases centralization which isn’t ideal.