3 ms·
Why would you care about readability of URLs, when each client can just show the cached metadata? Which is what happens anyway, kind of, in your browser history
by EGreg 8y ago
Why would you care about readability of URLs, when each client can just show the cached metadata? Which is what happens anyway, kind of, in your browser history and anywhere you share the links. Most people won’t read the url.
Now, as for the incentives. In fact, DNS does get poisoned and that’s why DNSSEC was invented. The same exact thing can be done on a DHT with private keys and certificates authenticating the author of a document. Except you don’t have the kind of dynamics that lead to centralized databases and breaches. Instead, we can even have content addressing, so the same exact resource can be cached even if it would have been “on a different domain”. And you know that resource hasn’t been changes from under you. Talk about incentives — there is a huge incentive for hackers to access these giant centralized honeypots and change up what’s being returned from a URL, or do phishing based on a slightly similar domain name.
Look up the MaidSAFE project and tell me, how exactly is the Kademlia DHT there vulnerable against everyone willing to spin up hosts? You can still use certificates and domains can still sign everything. The domain system is basically a search engine, which also has its own incentives.
And finally, Capitalism is the 2nd best system for organizing people and information, the first being open source. The Web, Wikipedia, WebKit, MySQL, PHP and Linux have long ago beaten AOL, Britannica, MSSQL, ASP.NET and Windows NT Server.