| Note I mentioned the web and DNS only as an example of the bootstrapping issue, not as a solution for how to overcome centralization. (And to illustrate how I work with the web's bootstrap requirements -- using root.zone file.) The need to bootstrap is ubiquitous. Even a user's internet connection is "bootstrapped". She has to know at least an RFC1918 address to get started. Disseminating a list of addresses of working supernodes so users can form networks and connect to each other should not be an insurmountable problem. The list does not have to disseminated via the network. Remember the days of POP and dial-in numbers? If the user has no internet connection then how did she get the dial-in numbers? This is not a difficult problem. re: ability to "ban a domanin name" When authorities "ban a domain name" via DNS, they only ban lookups using certain DNS servers. The server at the IP address associated with the domain name could still be accessible. The reason banning DNS lookups in order to take sites "offline" is so effective is because usually these sites are doing something shady and need to keep changing IP addresses frequently. No one knows what IP address they will be using in the future. They are very reliant on DNS. Otherwise, if we are dealing with a legitimate site that changes its IP only infrequently, it would be futile to try to "ban" it via DNS. It would be like expecting every nerd worldwide to forget that ftp.internic.net is associated with 192.0.32.9 or that example.com is associated with 93.184.216.34. Some will have saved this information. There are publicly available archives of historical DNS data. |