3 ms·

I wouldn't trust the stewardship of ICANN either. This group of muppets has been turning the top-level into a wasteland of garbage ever since they got control:

I wouldn't trust the stewardship of ICANN either. This group of muppets has been turning the top-level into a wasteland of garbage ever since they got control: https://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#ICANN-era_generic_top-level_domains https://en.wikipedia.org/wiki/List_of_Internet_top-level_dom... While reasonable gTLDs like .inc, .corp and .ltd get ignored, instead we have .aerospace and .google for reasons that have never been properly explained. They've also handed over .app to Google simply because Google was willing to pay a stupid amount of money for the rights, and Google can't even figure out how to sell these yet: https://www.registry.google https://www.registry.google

jmelloy 10y ago
.ltd is available now
- astrodust 10y ago
  That only took forever, but good to know.
marvindanig 10y ago
Exactly! They gave away the .book TLD to Amazon too and now no one can publish their own book using a .book domain name for their work.
- eridius 10y ago
  They did? That sounds pretty awful, but I don't see .book listed at https://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#ICANN-era_generic_top-level_domains https://en.wikipedia.org/wiki/List_of_Internet_top-level_dom...
  - deleted 10y ago
    [deleted]
  - kej 10y ago
    See http://nic.book http://nic.book
- zokier 10y ago
  No one could publish their own book using a .book domain before either.
zokier 10y ago
Frankly I think the middle-road that we had for a while was pretty much the worst of all worlds, and I like the mostly-liberated relatively flat model better. You either have hierarchy or you don't, and DNS/ICANN never really manged to create (and enforce!) true hierarchy at TLD level. Personally I would like a strictly hierarchical model (e.g. ccTLDs only with restricted 2nd level) more, but to enforce such system would have meant essentially a complete reboot of DNS which obviously would never happen. gTLDs were imho a mistake (probably caused by not being to able to predict the explosive growth of internet), but if we can't get rid of them then just liberating them makes lots of sense.
deleted 10y ago
[deleted]
walrus01 10y ago
https://cocks.corporation https://cocks.corporation https://dicks.wtf https://dicks.wtf https://why.does.icann.sucks https://why.does.icann.sucks
markdown 10y ago
Not to take away from your argument, but I'd argue that Automattic's acquisition of .blog is worse than .app
justinlardinois 10y ago
Is this really a problem? No alternate TLDs have ever caught on. .com continues to be the only TLD that most people care about. Even a .net domain makes you a second-class citizen on the web.
- astrodust 10y ago
  It's really a problem because there's no telling what might be a domain tomorrow. Will ICANN sell `.x` to buy everyone on the board a new car? Will they start issuing gTLDs in Klingon language? What about Emoji? This makes writing code that vets a fully qualified domain name a lot more complicated. If anything could be a domain name they you need to lean on DNS to do testing, and if that's not producing concrete answers, you have no idea if it's valid or not. Is clownpenis.fart a possible domain? Twenty years ago, no way that would ever happen. Now I'm surprised it hasn't. Ideally you want a root namespace that's clean, orderly and predictable so that people can comprehend it. microsoft.com looks legit. microsoft4u.info feels sketchy, and it should. microsoft.xyz is...legit? Or not? I can't tell any more, the waters are so muddied. Plus, ICANN doesn't seem to consider the ramifications of some of their decisions. The right-to-left gTLDs are obviously a great thing for speakers of certain languages like Hebrew and Arabic, but they also carry severe security hazards: http://www.rafayhackingarticles.net/2016/08/google-chrome-firefox-address-bar.html http://www.rafayhackingarticles.net/2016/08/google-chrome-fi...
  - Senji 10y ago
    TLD/SLD should never have been a paradigm. I say merge SLDs from .com into TLDs and start selling TLDs only. With all pre existing TLDs grandfathered in.

jmelloy 10y ago

.ltd is available now

astrodust 10y ago
That only took forever, but good to know.

marvindanig 10y ago

Exactly! They gave away the .book TLD to Amazon too and now no one can publish their own book using a .book domain name for their work.

eridius 10y ago
They did? That sounds pretty awful, but I don't see .book listed at https://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#ICANN-era_generic_top-level_domains https://en.wikipedia.org/wiki/List_of_Internet_top-level_dom...
- deleted 10y ago
  [deleted]
- kej 10y ago
  See http://nic.book http://nic.book
zokier 10y ago
No one could publish their own book using a .book domain before either.

zokier 10y ago

Frankly I think the middle-road that we had for a while was pretty much the worst of all worlds, and I like the mostly-liberated relatively flat model better. You either have hierarchy or you don't, and DNS/ICANN never really manged to create (and enforce!) true hierarchy at TLD level. Personally I would like a strictly hierarchical model (e.g. ccTLDs only with restricted 2nd level) more, but to enforce such system would have meant essentially a complete reboot of DNS which obviously would never happen. gTLDs were imho a mistake (probably caused by not being to able to predict the explosive growth of internet), but if we can't get rid of them then just liberating them makes lots of sense.

deleted 10y ago

[deleted]

walrus01 10y ago

https://cocks.corporation https://cocks.corporation https://dicks.wtf https://dicks.wtf https://why.does.icann.sucks https://why.does.icann.sucks

markdown 10y ago

Not to take away from your argument, but I'd argue that Automattic's acquisition of .blog is worse than .app

justinlardinois 10y ago

Is this really a problem? No alternate TLDs have ever caught on. .com continues to be the only TLD that most people care about. Even a .net domain makes you a second-class citizen on the web.

astrodust 10y ago
It's really a problem because there's no telling what might be a domain tomorrow. Will ICANN sell `.x` to buy everyone on the board a new car? Will they start issuing gTLDs in Klingon language? What about Emoji? This makes writing code that vets a fully qualified domain name a lot more complicated. If anything could be a domain name they you need to lean on DNS to do testing, and if that's not producing concrete answers, you have no idea if it's valid or not. Is clownpenis.fart a possible domain? Twenty years ago, no way that would ever happen. Now I'm surprised it hasn't. Ideally you want a root namespace that's clean, orderly and predictable so that people can comprehend it. microsoft.com looks legit. microsoft4u.info feels sketchy, and it should. microsoft.xyz is...legit? Or not? I can't tell any more, the waters are so muddied. Plus, ICANN doesn't seem to consider the ramifications of some of their decisions. The right-to-left gTLDs are obviously a great thing for speakers of certain languages like Hebrew and Arabic, but they also carry severe security hazards: http://www.rafayhackingarticles.net/2016/08/google-chrome-firefox-address-bar.html http://www.rafayhackingarticles.net/2016/08/google-chrome-fi...
- Senji 10y ago
  TLD/SLD should never have been a paradigm. I say merge SLDs from .com into TLDs and start selling TLDs only. With all pre existing TLDs grandfathered in.