• @Valmond
    link
    4
    edit-2
    19 days ago

    Ha ha yeah if there were only more competition :-D

    The idea is people run nodes (the hard part: routing incoming internet traffic to your PC) and nodes chit chat (any new nodes? Hey I just changed IP address!, … etc) so that there is a lots if known nodes. Identities rely on RSA keys (like ssh does).

    Then on top of that (thus making it useful) you can propose a deal for another node: you share my data and I’ll share yours.

    Which means people can access your data from your PC or from that other node sharing it for you.

    Share it with several nodes (you obviously are sharing theirs) and there will be a very high probability your data is accessible all the time.

    The sharing is completely trust-less, if a node stops sharing your data, you just stops sharing theirs and gets a new partner, no hard feelings.

    Added bonus is that it might be shared all over the world, so hard to take down.

    All traffic and data is encrypted, so no node even knows what they are sharing.

    You can change IP:port address, and update your data easily (that was the big work to be fair).

    That’s about it, the implementation is written in python3 + cryptodome and uses RSA & AES-CTR.

    The basic use could be to host a website, or a chat for example.

    What do you think?

      • @Valmond
        link
        318 days ago

        Now this is interesting, I know about Tor ofc, with all problems surrounding it (exit nodes etc) but I guess an onion website could be made well protected and shared & updated. You have to host it yourself though I guess.

        Freenet, gotta dig down and see how it works under the surface, it looks very promising but it’s kind of complex and I haven’t yet figured out if it is all benevolent sharing for example and what happend if some random node sharing your stuff goes offline.

        Very interesting!

        I think (I’ll dig more to see if it stands) my advantage would be the redundancy (so the data always stays up and is hard to take down), the no need of benevolent nodes, and potentially the ease if use.

        Thanks!

      • @Valmond
        link
        218 days ago

        Interesting!

        I poked around in the (slightly verbose) documentation and stumbled onto this:

        Servers should not re-use URIs, regardless of the mechanism by which resources are created. Certain specific cases exist where URIs may be reinstated when it identifies the same resource,

        So I wonder if it has the same inbuilt limitation that IPFS has, which means you cannot just update the data you are sharing, without also having to create a whole new link (I know IPFS are trying to work around that, but have seen no decentralised solution yet).

        I’ll poke around some more!

        Thanks for the link, I hadn’t heard of them before.

        Cheers