5 ms·
How long until .exe, .app, .apk, and .ipa follow? I don't really get why you'd pick a popular file extension as a TLD. It was bad enough when .java got registe
by jeroenhd 4y ago
How long until .exe, .app, .apk, and .ipa follow?
I don't really get why you'd pick a popular file extension as a TLD. It was bad enough when .java got registered, though that's worse because Oracle decided that the name of an island inhabiting over 150 million people was actually theirs to register (and ICANN want along with it).
- rozularen 4y agodidn't know about the .java tld. maybe because tld are assigned to countries and not provinces?
- TheSpiceIsLife 4y agogTLDs are not assigned to countries.
- jeroenhd 4y agoTLDs have been assigned to cities (.amsterdam, .london, .nyc) and provinces (.frl). They're not ccTLDs though, but TLDs bought by a registrar.
- CydeWeys 4y ago> They're not ccTLDs though, but TLDs bought by a registrar. Registry, not registrar.
- dragonwriter 4y ago> How long until .exe, .app, .apk, and .ipa follow? Well, we’ve had .com, for a while (though its no longer that popular as a file extension, but…), so…
- crazygringo 4y agoI can't imagine those would ever be made available. Fortunately, .zip seems less worrisome from a security perspective -- you don't execute a zip file. (Unless I'm missing where clicking on .zip files is an intermediary step in a common exploit?) It's more just confusing from a usability perspective. Like, I don't want domains ending in .jpg or .mp4 or .doc or .txt either, you know? It's a benefit to be able to look at a string and usually be able to reason with high confidence whether it's a domain name or filename. It definitely feels weird to me.
- chakalakasp 4y agohttps://twitter.com/_mg_/status/1658528430588317696?s=46&t=-j7Johk1IPELSG5tOtBrPw https://twitter.com/_mg_/status/1658528430588317696?s=46&t=-...
- CydeWeys 4y agoDevil's advocate -- what exactly is the attack vector here, even for TLDs that share names with executable file extensions? .com already exists, the biggest one of them all, and that doesn't seem to cause problems? https://en.wikipedia.org/wiki/COM_file https://en.wikipedia.org/wiki/COM_file
- arp242 4y agoThe reason .java was approved is because the ISO-3166 designation is the Indonesian "Jawa" rather than the English "Java".[1] Thinking about this, I can follow their reasoning, although I do find it a little bit too much following the letter of the rule rather than the spirit and perhaps some more thinking might have been prudent. On the other hand, do we really want to give a special status to English? Using the local language seems to make sense to me – after all, Indonesian people will want to type "gojek.jawa" and not "gojek.java". And there are some questions: should we also consider placenames in Spanish and other widely used languages? Is a small town of 100 residents enough to prevent registration? etc. [1]: https://gtldcomment.icann.org/applicationcomment/commentdetails/8044 https://gtldcomment.icann.org/applicationcomment/commentdeta...
- account42 4y ago> On the other hand, do we really want to give a special status to English? Yes. English is the lingua franca of the computing age. Having a common reference language is a good thing even if not popular with the professionally outraged.
- derefr 4y agoPerhaps .java and other English-language equivalents of domestic-language gTLDs should be reserved to act as proxies for the underlying domestic-language gTLD. I.e. the root nameservers should direct requests for .java to the same nameservers responsible for .jawa; and the nameservers for .jawa should be required to respond to queries for any record of A.B.C.D.java. by rewriting the request to be for A.B.C.D.jawa., and then resolving that, rather than treating it as a separate zone. Domain owners of domains in gTLDs like .jawa would only get one DNS zone file to control — the canonical one — but they'd be free to do something different on the application layer in response to differing e.g. TLS SNI in the request. (So if they're running a webserver on A.B.C.D.{jawa,java}, then they could make the .java version do an HTTP redirect to the .jawa version; or make both serve the same page, but with a rel="canonical" header pointing to the .jawa version, etc.) Personally, I feel like it'd make sense to add all sorts of proxy gTLDs for every existing two-letter ccTLD, both in their own language and in other languages. So e.g. the .de ccTLD could have both .deutschland and .germany acting as proxy gTLDs, where a domain owner who registers a .de domain is "getting" those others as well, for free. This would obey the Principle of Least Surprise for both people visiting domains, and people buying domains: if you own example.de, and a .germany gTLD were to exist, then it would be surprising if you didn't also own example.germany, since the two TLDs serve the same purpose.
- meragrin_ 4y ago.app has been out.
- CydeWeys 4y agoIts five year anniversary is this month, in fact. https://blog.google/products/registry/5-apps-you-should-know-about/ https://blog.google/products/registry/5-apps-you-should-know...