No. But are you looking for purely an overlay network on top of the current internet or a new internet? FIPS was interesting to me because it at least claimed to be for replacing the current internet (by which I mean it is supposed to work on top of physical links), although now I see people treating it just as an overlay network like Tor, which is sad.
I had this idea a long time ago of how to connect and route between mesh networks potentially scaling through the entire globe, but I'm thinking here only about physical links and a new internet: nostr:naddr1qqyr2wpjvd3kgvtyqyghwumn8ghj7enfv96x5ctx9e3k7mgzyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze6qcyqqq823c53smcd
I have no idea of how bad this idea is, because I couldn't find anyone to criticize it or any other idea to compare it to and I have zero experience with any of this.
As far as I know all the mesh networks in the world are sadly much less ambitious than I want: they're all happy to just be a local thing. And in some cases they clearly state that their routing algorithms don't scale at all (they're either based on a centralized supernode, or nodes flooding the network with packets, or on everybody keeping a routing table of the entire network locally).
Projects like Meshtastic are just a stupid psyop. They get people to be excited about a completely useless thing, thinking they are contributing to creating a new decentralized internet, and that their stupid toy is actually a step towards that, but in fact it can never be more than that toy.
What I wanted to see was an actual meshnet project that employed some routing algorithm capable of easily adapting to new nodes joining freely, but also adapting to a new mesh network being connected by some new node, and then some other mesh connects to that, and so on, until you're able to route a message to someone a thousand miles away.
I think my method above works, and it is not magic because it has this important tradeoff: you can't route only with keys, i.e. your address can't be just your key like all these other projects do, you also need route hints in the address. It's like using an nprofile instead of an npub.
My method needs a lot of flushing, though. All the details are unspecified. And it would probably not work with any existing base network software, as it wouldn't deal with IP addresses at all (addresses would be much bigger than even IPv6 can support). It also needs a name, then we would have to adapt TCP and UDP to work on top of it (the name is important so we can call it TCP/<name> thing). I also didn't think about the incentives for routing at all.
I had this idea a long time ago of how to connect and route between mesh networks potentially scaling through the entire globe, but I'm thinking here only about physical links and a new internet: nostr:naddr1qqyr2wpjvd3kgvtyqyghwumn8ghj7enfv96x5ctx9e3k7mgzyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze6qcyqqq823c53smcd
I have no idea of how bad this idea is, because I couldn't find anyone to criticize it or any other idea to compare it to and I have zero experience with any of this.
As far as I know all the mesh networks in the world are sadly much less ambitious than I want: they're all happy to just be a local thing. And in some cases they clearly state that their routing algorithms don't scale at all (they're either based on a centralized supernode, or nodes flooding the network with packets, or on everybody keeping a routing table of the entire network locally).
Projects like Meshtastic are just a stupid psyop. They get people to be excited about a completely useless thing, thinking they are contributing to creating a new decentralized internet, and that their stupid toy is actually a step towards that, but in fact it can never be more than that toy.
What I wanted to see was an actual meshnet project that employed some routing algorithm capable of easily adapting to new nodes joining freely, but also adapting to a new mesh network being connected by some new node, and then some other mesh connects to that, and so on, until you're able to route a message to someone a thousand miles away.
I think my method above works, and it is not magic because it has this important tradeoff: you can't route only with keys, i.e. your address can't be just your key like all these other projects do, you also need route hints in the address. It's like using an nprofile instead of an npub.
My method needs a lot of flushing, though. All the details are unspecified. And it would probably not work with any existing base network software, as it wouldn't deal with IP addresses at all (addresses would be much bigger than even IPv6 can support). It also needs a name, then we would have to adapt TCP and UDP to work on top of it (the name is important so we can call it TCP/<name> thing). I also didn't think about the incentives for routing at all.