There is a lot of concern over the control and policing of the Web in its current form. According to http://rt.com/usa/news/internet-provider
This is a vision of the Web-i of the future. It may not be technically correct but that's not the point, but it may inspire some developer out there to make a quantum leap in the way that the Web-i will work and be provisioned in the future. Think of the way a torrent works, many bits of information distributed across many machines. The torrent program assembles these, gathering pieces of the file you want and downloading these pieces simultaneously from people who already have them. Extend this logic to websites. Imagine that your website behaved in the same way as a torrent, many people having pieces or all of your website on their machines. You browse using your extended "torrent sentient" browser, searching for the website you wish to visit. You click and the website is "assembled", picking up the latest changes.
This gives rise to Web-i(independent) - A web that is independent of ISP, perhaps not even traditional server based, impossible to limit, subject to policing and censorship only by its users, independent of governments.
The implications of such a process are staggering. No central server required to host a website. No forced filtering mechanisms as the bits and pieces of the website and its content are distributed across the web, obviously to the people who are interested in the content. Difficult or even impossible to control or shut down. You no longer would require an internet address i.e. Dot Com, as the content would be IP based. Data would flow in an amorphous mass in the Web, changing the dynamics of web search algorithms. The Data itself would become the Web-i, the new web, independent of architecture and infrastructure. ISP’s would become redundant in their current form, after all, all you would need to be connected is a data access point.
You may argue, "What about sites that have extended functionality such as billing or trading? " I may well have a secure billing application running on Web-i, that the web recognizes as a valid billing engine, and picks up that component in the "assembly" process when a user views site. I could then feasibly bill that site for the use and provide a third party service. There is no need for a site to develop a billing engine, other than to connect to the sentient links I provide. Nonsense!! you say, well, we said that about the Wright Brothers. Welcome to Web-i.