But I'm talking about physical links.

Reply to this note

Please Login to reply.

Discussion

Yep, that works (I used to setup corporate networks back in the 2000s).

But you are trusting the operator of each hop along the way.

Aren't we trusting the operator of each hop in the current world?

We are. And we shouldn't be.

What can we do about it besides encrypting and/or signing messages?

I don't think there is a solution for IP without pubkey cryptography. There are too many third-parties to interfere.

DNS is a lot easier thought. I'd love to get to your website by typing nostr://`d-tag`.npub1.../ in the browser. You can just keep d-tag -> IPs in a replaceable event.

"Reticulum is the cryptography-based networking stack for building local and wide-area networks with readily available hardware. It can operate even with very high latency and extremely low bandwidth. Reticulum allows you to build wide-area networks with off-the-shelf tools, and offers end-to-end encryption and connectivity, initiator anonymity, autoconfiguring cryptographically backed multi-hop transport, efficient addressing, unforgeable delivery acknowledgements and more."

https://github.com/markqvist/Reticulum

A private connection with an alert message to approve or deny?!

I think the trust should get permissions.

Are you aware of any "decentralized internet" proposals that do something like that? As far as I know all the alternatives to centralized IP (like cjdns, for example) always make use of some DHT for discovery, which to me sounds like it will never work, but having big routing services maybe could.

If you know the endpoint's key (because you are typing it on the browser) then I am ok with central routing services. In the end you can verify what's coming by yourself. The routing service can try to play you, but you have the information to verify it.

If we know keys, we can always use petnames to simplify their use. But the important part is to have the keys themselves.

cjdns is cool. I am not deep enough to know if it would work or not. But they should try.

Pretty sure the newest version of Yggdrasil (0.5.x) removed the DHT and is using CRDTs and bloom filters to route traffic.

https://yggdrasil-network.github.io/2023/10/22/upcoming-v05-release.html

Have you taken a look at #reticulum?

For bootstrapping such a network, the links can also be logical initially:

You can be connected to x-router via IP itself, which is physically connected to let's say the most active community of this protocol.

You start connecting to y-router directly when Y Inc starts supporting this protocol and sets up an ISP in your locality