• cogitase@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 months ago

      I’d love to be able to “seed” the fediverse through p2p hosting of some sort. I’d set aside 1 TB of storage and 20 MB/s for that.

      • TropicalDingdong@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 months ago

        Yeah I’ve thought a tiny bit about this but it gets dodgy with things like csam.

        How do we address some one uploading stuff that would get you arrested?

        • lambalicious@lemmy.sdf.org
          link
          fedilink
          English
          arrow-up
          0
          ·
          2 months ago

          I would hav thought stuff like Lemmy would have configurations to eg.: not allow to upload images locally, only hotlink.

          Anyway, an alternative is “zero knowledge” storage, where you don’t know what you are storing (hence, you can’t “choose” what to host or not host either). Another alternative is disjoint storage, where two different servers store different halves of a file (eg.: an Odd Bytes server and an Even Bytes server), but this means now it’s necessary to hit more servers to recover a file.

          But the sensible thing to do IMO is to apply “common carrier” concept. The water distribution company is not, to my knowledge, held liable when something happens like you fill a bucket of water and share it with someone else.

          • TropicalDingdong@lemmy.world
            link
            fedilink
            English
            arrow-up
            0
            ·
            2 months ago

            The water distribution company is not, to my knowledge, held liable when something happens like you fill a bucket of water and share it with someone else.

            No but they are liable if there is lead in the water, even if they don’t know it.

        • eskimofry@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          2 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.

          • LostXOR@fedia.io
            link
            fedilink
            arrow-up
            0
            ·
            2 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.

        • BrianTheeBiscuiteer@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          2 months ago

          There’s gotta be some kind of limited liability for this kind of thing. I mean, banks wouldn’t be liable if someone put csam in a safe deposit box or (assuming they don’t x-ray packages) UPS shipping csam in a sealed package. I think there just needs to be reasonable safeguards against it but I don’t know if any of that is built into the software.

          • SzethFriendOfNimi@lemmy.world
            link
            fedilink
            English
            arrow-up
            0
            ·
            2 months ago

            Issue here is that what’s in a safe deposit box isn’t also being shared/distributed. It is locked away.

            If, however, they made copies of the contents of a box and put it in other boxes … and it came out somebody used that for CSAM then there probably would be some kind of liability.

            Besides CSAM there’s also copyrighted material, etc which section 230 kind of covers but even then gets tricky since there’s a duty to respond to DMCA takedowns in order to get safe harbor protections.