Mesh networking modules, auto-config, auto-peer
I recently published this module which is used for communicating with and configuring a CJDNS node over its admin interface. The admin interface operates over UDP and has a simple request/response pattern.
It’s my belief that modules like that will become more common for working with CJDNS and other mesh networks to provide an easy way of working with the network. My own goal is to use the admin module to facilitate peering private and public networks, rapidly expand coverage, and improve network strength.
Peering where it starts and there are always folk hollering in the chats for peer credentials. Rather than manually creating credentials for friends and associates the user can be provided an easy way to facilitate the peering process. Some would argue that making it easier for people is not a good thing and that lowering the bar will retard the conversation. These tools will offer us a way to objectively measure success and failure of mesh networks and that could lead to improvement in quality.
Since the admin module can also call functions to ascertain the quality of the connections, how many peers, routes, and more it will be handy to look at that info. Informed decisions can be made with evidence so if people can figure out how to intelligently display the network health information that would be useful.
There is a possibility that the mesh net apps and modules could also be used to deploy a secure network for their private desktops in an office, multiple offices, or even to create a distributed architecture for their public services. Sophisticated business owners might be willing to pay for individuals to setup these secure networks if there is enough value in it.
One group has a product and service called the Enigmabox. They are selling a device and network access so you can plug-in and gain the benefits that their network offers which is considerable. If you have purchased their device and network you will have anonymous and unlogged surfing. They also offer multiple locations in case your access gets blocked because of your country.
Even if you don’t care about leveraging technology for money some might be concerned about the risks of centralization or having all your eggs in one basket. The big services like IBM, Salesforce, Amazon, Microsoft, and Google offer benefits like not having to know as much about the system architecture or scaling.
There is a drawback to the cloud model other than having less server administrators on payroll. Every corporation, no matter what, is a government subsidiary. The owners and operators of the corporate fiction will comply with edicts issued by government agents or risk being harassed with letters, sued, and if they don’t comply with their orders force will be applied. What are the odds that a large, publicly-traded, lobbying, group of people are going to stand up to government agents with guns in order to protect user data?
If you accept that the initiation of force is immoral and you don’t want to participate in it then I could see how using the myriad of commercially available services would give you that slimy feeling all over. Yes, even down there. Plus exposing your users data to the risk of theft by agents working for the state may be more than you are willing to do.
These projects necessarily bring people together for discussion about topics important to the us. Because data security is a controversial topic I think mesh networks provide a solution and forum for discussion about important issues.