11 ms·
This seems very similar to cjdns[1] [1] https://github.com/cjdelisle/cjdns https://github.com/cjdelisle/cjdns
by SomeoneWeird 11y ago
This seems very similar to cjdns[1]
[1] https://github.com/cjdelisle/cjdns https://github.com/cjdelisle/cjdns
- jMyles 11y agoCJDNS is amazing. I've been working on a python frontend for it; I call it Cirque. https://github.com/jMyles/cirque https://github.com/jMyles/cirque
- joeyh 11y agoNot realy. cjdns seems to need an invite to get onto its network. Not saying that's necessarily a bad idea; cjdns seems to be useful to the people that use it. But if I want to build an app that communicates P2P over such a network, a manual step to join the network won't fly.
- thescriptkiddie 11y agocjdns does not exactly need an invite. If you want to peer over the internet you'll need to swap public keys with someone already part of the network. But most people have turned on autopeering, which will discover peers on the local network and take care of peer swapping for you. Keep in mind that the intended purpose of cjdns is not to be a p2p library, it is to be a mechanism for connecting local mesh networks together into a mesh internet.
- kpcyrd 11y agocjdns dev here, the network has been opened a while ago. There are some public peers floating around. There's nightfall[0] to find/announce public peers, but I consider it very beta (quickly hacked together on a bus trip). [0]: https://github.com/kpcyrd/nightfall https://github.com/kpcyrd/nightfall
- gabeio 11y agocjdns can be used as a private mesh also so it completely depends on the application. A private mesh could be more appealing to some.