5 ms·
I really dislike corporate brand TLDs. But I’ve long ago wished we had expanded the TLDs earlier to include a lot more obvious things like: .movie, .book, .mus
by erentz 8y ago
I really dislike corporate brand TLDs. But I’ve long ago wished we had expanded the TLDs earlier to include a lot more obvious things like:
.movie, .book, .museum, .news, etc.
This would have avoided this problem where you have “book-name-book.com” and “newblockbuster-movie.com” and so on.
- plibither8 8y agoCorrect! Even something as simple and obvious as '.api' is not a TLD.
- larkeith 8y agoTo be fair, due to the hierarchy of domains, it does make sense for api to be a subdomain rather than TLD. It would be a cool alternative to guarantee that example.tld owned example.tld.api though, as you could assume that any .api domain would be an API.
- kkarakk 8y agoit does not make sense, right now apis are hidden away under the domain hierarchy but are used as first class citizens of the web. lots of times you don't care about anything on a domain but the api
- kadendogthing 8y agoTLDs for things, not TLDs for trademarks.
- progval 8y ago.museum has been around for a while (~2001), but I have never seen any use of it.
- ebcase 8y agoI recently came across this! https://www.californiarailroad.museum/ https://www.californiarailroad.museum/ (no affiliation with them, but was pleasantly surprised to see it in the wild)
- empyrical 8y ago.coop for co-operatives has also been around for a while (2001), with domains like: https://chicken.coop/ https://chicken.coop/
- ghostly_s 8y agowhat, exactly, is the problem with having “newblockbuster-movie.com” ? These sort of domains are usually abandoned within a couple years, anyway.