Live data from Hacker News

The Problem with Vanity TLDs (2011)

templetons.com

21–30 of 71 posts

Re: The Problem with Vanity TLDs (2011)

#21
post #7

I would tolerate the ICANN TLD money-grabbing scheme, but the "new" TLDs are a little more than an indication of bad taste. I can't be the only one to dislike anything more than 3 characters in a TLD, like .cloud or .engineering.

What’s the problem with longer length tlds?

As non-native speaker, I always have to google how to spell `engineering`. And you can't really auto-correct domain name.

Re: The Problem with Vanity TLDs (2011)

#22
post #15

There is already http://microsoft.bing . See https://en.wikipedia.org/wiki/List_of_Internet_top-level_dom... .

Which redirects to bing.com, proving that they really have no use for the .bing TLD other than to prevent someone else from grabbing it.

Imagine the clamour of people who want to be associated with Bing

The real problem is can I still type weirdfilename.exe into the browser bar and get to a search engine?

Re: The Problem with Vanity TLDs (2011)

#23
Sorry, but *looks at my nails* .com is a boomer TLD, it's passé. Do you really want a domain from last century? Or do you want an exotic .asia? A cool .club? A forward looking .future? Or even joining the ranks of the celebrity media with a stylish... .xn--45q11c?

The answer is clear, if you want to stay in the past, then go with .com, but the .future is in vanity TLDs. For more information, check out my website https://ok.boomer and considering buying a .boomer domain today!

Re: The Problem with Vanity TLDs (2011)

#25
post #20

Earlier quoted context omitted.

In practice URLs often cannot be more than 2K characters. It's also more work to type and bytes to transmit and harder to see on small screens. For many use cases these are irreverent, but they do matter to some.

Where is 2K a limit these days?

Chromium based browsers!

> The Google Chrome browser supports a maximum length of a web page URL of 2 MB (2048 characters) in size.

taken from [0]. Do note that this is a restriction created by the browser developers. In theory a URL can be of arbitrary length. Some browsers (like Firefox) do comply with this, though they might now show the full URL to the user, cutting it off after a certain number of characters.

[0]: https://mywebshosting.com/what-is-the-maximum-url-length-lim...

Re: The Problem with Vanity TLDs (2011)

#26
post #5
post #4

Needs (2011): http://web.archive.org/web/20110321001950/https://www.temple...

It might even be older according to the main page ("mostly written in 2001")[0]. Sure would be helpful if the author included a publish date. Many blog entries (and stack overflow type solutions) need time context (it may have been the solution/a reasonable position at the time ) https://www.templetons.com/brad/dns/

Given the reference "I wrote a satire of issues around this some years ago" for a piece posted in 2005, I suspect the 2010 / 2011 year is reasonably accurate.

https://ideas.4brad.com/node/221

https://www.templetons.com/brad/dns/sell-english.html

Re: The Problem with Vanity TLDs (2011)

#28

I would tolerate the ICANN TLD money-grabbing scheme, but the "new" TLDs are a little more than an indication of bad taste. I can't be the only one to dislike anything more than 3 characters in a TLD, like .cloud or .engineering.

ICANN has clearly strayed from its charter of nonprofit root trustee, and is acting like any other for profit entity and arbitraging away their assets. I'd love to see a root-restandardization effort that aims to take anything that isn't (com/net/org, the country code tlds, and whatever other traditional ones I'm forgetting) and sticks it under a new .icann or whatever. So ICANN can "sell .google", but most everyone would end up referring to it as ".google.icann". The sooner this is done the better, to make it clear that attempting to use the root pollution will end up being a painful experience.

Heck, let Big Tech take .google/.apple/.amazon/.comcast etc if that's what it takes to get this done. Point being to keep the root pollution to a finite amount rather than the ongoing sell off of any name imaginable.

Re: The Problem with Vanity TLDs (2011)

#29
post #20

Earlier quoted context omitted.

Where is 2K a limit these days?

Chromium based browsers! > The Google Chrome browser supports a maximum length of a web page URL of 2 MB (2048 characters) in size. taken from [0]. Do note that this is a restriction created by the browser developers. In theory a URL can be of arbitrary length. Some browsers (like Firefox) do comply with this, though they might now show the full URL to the user, cutting it off after a certain number of characters. [0…

That would be 2KB (the error is in the reference material; you cited it faithfully).

Re: The Problem with Vanity TLDs (2011)

#30
post #20

Earlier quoted context omitted.

Where is 2K a limit these days?

Chromium based browsers! > The Google Chrome browser supports a maximum length of a web page URL of 2 MB (2048 characters) in size. taken from [0]. Do note that this is a restriction created by the browser developers. In theory a URL can be of arbitrary length. Some browsers (like Firefox) do comply with this, though they might now show the full URL to the user, cutting it off after a certain number of characters. [0…

What's interesting is how 2048 characters is 2 KB (a factor of 1000 difference) but this conversion of 2 MB = 2048 characters seems to have been copy-pasted around the web
Post reply on HN