Hey selfhosted fam, we are looking for those interested in helping host a distributed, Tahoe-LAFS file share for at least 6 months. Looking for at least 5 more people, but there is no limit on the number of nodes you can add. Our loose plan is everyone (8 people minimum) will put a small data share of around 32gb, which we will distribute amongst the volunteers. Tahoe is designed to not require trust, so that is by design.

Inspired by conversations at Linuxfest Northwest this last weekend. If interested, please do follow up. The main goal is simply to put something online for the next 6 months, which will survive the inevitable people dropping off or being replaced, even after the experiment concludes. Cheers either way for considering! Here is a simple form or you can join our Matrix chat. We are half way there on volunteers, but more are always welcome! Will be discussed on next episode of Linux Prepper podcast.

  • neidu3@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 days ago

    This just sounds like seeding an encrypted torrent with extra steps.

    I’m noping out in this until I have a plausible explanation of what the data actually is, because I’m not hosting people’s CSAM collection for them.

  • HelloRoot@lemy.lol
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 days ago

    Am I blind? Where is the docker-compose? J find references to it in the doc and in the PR’s but I don’t see it in the files.

  • infeeeee@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 days ago

    How can you be sure someone is not storing CSAM on your server, if it’s encrypted?

    It sounds like storj from a decade ago, but you got at least some monopoly money for your storage there. I don’t follow what they are doing nowadays but it started similarly

  • Meldrik@lemmy.wtf
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 days ago

    Interesting. I’ve been thinking about something like this for instances that use PeerTube. People could donate storage to PeerTube instances.

  • Valmond@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 days ago

    Hello, interesting!

    So it is basically IPFS but you encrypt the data first?

    If a node changes address, how is that handled?

    Isn’t splitting up data making it just more vulnerable?