I guess I am not explaining well enough. I am offering a great solution, and it is completely compatible. You do not need to connect to hyberbora.
You failed to understand that you need IP Address to connect to the network with other peers. Maidsafe does not produce IP address. It is not a meshnet in itself. It is decentralized software on top of monopolized ISP. This means you now have two options here; Use the draconian ISP and hope they don’t block your packets. Or use cjdns, and control your packets.
The key here is the packets and how it is transmitted.
Of course there are other mesh such as batman but that is not encrypted, nor the ip address are encrypted. It is just an open packet bouncing everywhere, unsecured. Cjdns is the only alternative solution.
You should really read the whitepaper. From the introduction,
Imagine an Internet where every packet is cryptographically protected from source to destination against espionage and forgery, getting an IP address is as simple as generating a cryptographic key, core routers move data without a single memory look up, and denial of service is a term read about in history books. Finally, becoming an ISP is no longer confined to the mighty telecoms, anyone can do it by running some wires or turning on a wireless device.
This is the vision of cjdns.
Here is an important detail…
Another issue is how are we going to route packets in a world where the global routing table is simply too large for any one router to hold it all? Despite the heroic efforts of core network engineers, the growth of the global routing table seems an unstoppable march. Cisco router company has proposed a plan called Locater/Identifier Separation Protocol, or LISP which aims to solve this by re-aggregating the routing table without forcing people to change their precious IP addresses. A different view of this problem is IP address allocation, currently it is done by a central organization which assigns IP addresses in such a way as to make the routing table as small as possible. Unfortunately this creates a bar of entry to the ISP sphere because aspiring network operators must register with the central organization and apply for an allocation of IP addresses while demonstrating that they will not be wasted. It is always easier to show that you need IP addresses if you already have a network.
And another most important detail…( from the whitepaper. I emphasis that you should really read every bit of it. )
A more technical issue with the Internet, and one of which many people are unaware, is address space deaggregation. Every computer connected to the Internet needs an address, a number which uniquely identifies it and which is attached to every piece of data which is to be sent to that computer. At every
stop along its path through the Internet, a packet (unit of data) has its address field examined by a router so it can decide which wire that packet should be sent down. Routers have an easier time if addresses are in big blocks so that a router can look quickly at the first numbers in the address and know, for example, that it is destined for somewhere in China, not exact but enough to know which wire to send it though. People naturally want as many addresses as they can possibly get and they want them in the smallest blocks possible, this is so they can then control (or buy and sell) these small blocks independently. The smaller the blocks of addresses which are announced, the larger the routing
tables become and the more work the Internet’s core routers must do in order to send a packet in the right direction. There have been attempts to aggregate addresses back in to groups but nonetheless, the number of small announcements in the global routing table has grown every year.
cjdns is built on the idea that the ISPs and hosting providers which exist now will never upgrade, not to LISP, not to DNSSEC, not even to IPv6 in any meaningful way. Building new systems to be compatible with old systems is catering to the audience you will never have. Asking existing ISPs to upgrade
for the common good is asking them to take a risk with no immediate benefit. cjdns is about throwing out the book and redefining the specifications in a way that will be fast, secure, and most importantly, easy for the next generation of ISPs to deploy and use.
I never said it was anonymous. It is simply a friend to friend meshnet with awesome perks. This design removes the entire concept of OSI model, and uses a new model. It uses it’s own packets, not draconian isp packets. you control your own packets. It gives every user a encrypted IPV6 private key, and public key. Users(ISP) can now connect to any other users(ISP). Now think about that for a second here. Can maidsafe do that at all, no. Again, Maidsafe is a decentralized software on top of the network. CJDNS is a decentralized IP routing table, and decentralized physical network. It takes chuck of physical wires and shift to house to house. Friends to Friends.
So really, we do not need to build another solution which already exist, and is stable. It works on majority of devices, and modems/routers/switchers. There is a dev working to get cjdns on android devices. LoT benefit greatly from this amazing piece of technology.
As you see, I explicitly stated that if you want a community mesh, you need a network protocol that provides IP address. The only option is Cjdns. Do you understand now?
CJDNS = Provides encrypted IPV6 routing table, and controls your own encrypted packets. Nothing more.
Maidsafe = Provides XOR address table, requires IP address. Packets are either controlled by Dracions ISP or cjdns.