Hacker News Reader

Comment by jbverschoor | Hacker News Reader

Well, there's also .com which was confusing for me as a 12 year old thinking it had something to do with a .COM executable, and nobody could explain what it meant.

I hereby want the .exe, .arj, and .rar TLD :-)

View on HN

.jpg would make sense, if it's limited to domains only ever hosting a single image file, like goatse.jpg

That would be an hilarious restriction. And I’m sure it would also push clever devs to stretch the definition of what a single image file is. I now kinda want that to happen.

Domain names that are limited in their functionality by the TLD are really interesting to me. I know all of .dev is on the HSTS list, for example. I'm currently working on a subdomain registration service that only permits A/AAAA records in the private IP address ranges [1], but still supports certificate issuance over ACME DNS-01 via TXT rrecords.

For jpeg, that would be a terms of service agreement? Or would the TLD manage all hosting?

[1] https://www.getlocalcert.net/

I think at least my consumer router would block such DNS on grounds of DNS rebind protection.

Can you share which model? I think the better approach is to resolve the domain locally, using unbound or similar. That's extra setup that some people won't do, so I want to support multiple options.

Official OpenWRT builds do this by default (though you can turn that off in DNS settings), but many newer consumer routers that use OS based on OpenWRT might not have the option.

You also wouldn't be able to access it on grounds of the private IP address is not in the same private as your LAN.

Why stop at .jpg?

Imagine every file extension was a domain. Imagine all the public files of the world existing on the internet at their very own URL. It’s like the internet was just one massive directory of files.

Now wouldn’t that be amazing?

I hate read comments here, because they are always AIDS. People arguing about whether non technical people know what a zip file is for example. But this comment was a shiny diamond in a pile of turd, thank you.

`command.com` is owned by 3M now to advertise its Command line of removable adhesive strips.

URL prefixes were supposed to resolve this ambiguity (file:// vs. http[s]://), but I guess people got tired of saying "aych-tee-tee-pee-colon-slash-slash..." :-)

We already have the .sh TLD [1]. So I don't see an .exe as a stretch

[1]: https://en.wikipedia.org/wiki/.sh

That is a ccTLD. ICANN is not allowed to take it back even if they want to.

gTLDs can and should be held to a higher standard.

The standard gTLD registry operator contract does not allow ICANN to unilaterally yank delegated TLDs.

While that is a good point, I am seeing a term of 10 years in Article 4 of the contract. Not sure whether ICANN has discretion to renew or not renew at the end of the term (IANAL), but if they stated now that they have no intention to renew, it could crater demand for domains using the TLD and make the venture costly for Google, should they pursue legal action.

https://newgtlds.icann.org/sites/default/files/agreements/ag...

This is just flat out not how ICANN actually operates, though.

I was disappointed to find exe.zip was already registered.

I hope someone does what https://omg.lol did. I would pay for a subdomain.

This reminds me of being a kid in the 90s and installing the DOS version of Command & Conquer onto a parent’s laptop and then being asked to delete it. COMMAND.COM yep that must be it…

Notably, not a lot of computer users could explain what the COM in executables meant, either, even in MS-DOS times :) (A command [external to the CP/M command interpreter], IIUC.)

Wow - arj. Now that's been a while!

> I hereby want the .exe, .arj, and .rar TLD :-)

.exe to host web-assembly content?

.app has also been a thing for quite some time

Haha, thanks for reminding me of .arj - good times!

Reply on news.ycombinator.com