-
> casually drops his own routing mechanism
Damn, inet256 is actually very nice as well. I'm currently reading through its architecture, so far I like that it's just a layer that can reuse existing infrastructure.
Are there predefined ways for peer discovery? The architecture [1] document doesn't mention things like hole punching, TURN/TURTLE routers or NAT tracing via UDP TTLs and multicast, so I'm a bit curious how peers would discover themselves in such a setup with their necessary transport layer information (IPs, ports, punched holes, UPnP config etc).
In my case I decided to implement a custom DNS (over TLS/HTTPS) that's verifying the pushed updates of entries via the TLS client certificates, and those are namespaced via their own subdomain (which is also the subject part of the TLS certificate). This way the initial DNS answer that is sent from the peer to the server contains all information that's necessary for other peers to connect to them later.
[1] https://github.com/inet256/inet256/blob/master/ARCHITECTURE....
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
Related posts
-
SourceHut terms of service updates, cryptocurrency projects to be removed
-
INET256 is a 256 bit network address space for p2p applications
-
INET256: A 256 bit address space for peer-to-peer applications
-
Spork: Peer-to-peer socket magic in the air
-
INET256: A 256 bit address space for peer-to-peer hosts/applications