4 ms·
I think another big problem with ICAAN and our DNS is the TLD. The fact that somebody who wants to represent their self on the internet might not be able to do
by NHQ 16y ago
I think another big problem with ICAAN and our DNS is the TLD. The fact that somebody who wants to represent their self on the internet might not be able to do so in a manner of their choosing because the domain they want is "owned" across all major and minor TLDs is very anti-internet-philosophy.
Top-Level is anti-web, because the web is not meant to be a top-down system. To me, this is a fundamentally flawed implementation. And why not? In terms of mass web, it was the first. When are first iterations ever correct?
Destinations are IP addresses. We all have em. What you want to call yours should be up to you. Ever since there was a postal service, people could be reached at the address they had. Even phone numbers weren't top-down (area codes), so that you could reach a local address, even it was the same as one in another county, without pre-(or post-) fix. I don't have the solution, but it wouldn't hurt for the public to learn and understand their IP address same as they do their home one.
Google alone, or with the help of other major "linkers", could go a long way in changing our DNS structure, by indexing different systems.
Decentralization is every nerd's dream, aint it? Eventually the serving capacity of consumer devices should be adequate to resolve standardized requests.
I think this holds promise: telehash.org
- pak 16y agoIP address blocks are allocated by IANA, which is managed by, you guessed it, ICANN. Just sayin'. http://en.wikipedia.org/wiki/Internet_Assigned_Numbers_Authority#Oversight http://en.wikipedia.org/wiki/Internet_Assigned_Numbers_Autho... It all is top-down at the core. (And it kind of has to be, because as much as we think of the Internet as "decentralized", it is a communication network, and so centralized administration is often the most efficient and sane way of doing things.)