The internet was designed around a very specific human readable taxonomy of distinct objects, namely hosts, files, and users. We technically could cause the hos

The internet was designed around a very specific human readable taxonomy of distinct objects, namely hosts, files, and users. We technically could cause the host and file namespaces to collide on purpose, but other than creating a market for products and services that unknot the mess this makes, what makes it a good idea? I think it's probably time to abandon the platform dominated internet for new cryptographic protocols, as the beneficiaries of this inconsistency are the intermediaries who will charge you to manage the chaos and inconsistency they have themselves created. If you have to do file scanning in email or do any security/governance work at all, TLDs that collide with filenames look like a disaster. An example would be, given a string in a file draft.temp.zip, does it refer to a local filename or a domain? I'd even suggest muddying the namespace like this is a kind of subversion of the internet, which was effectively a social contract about consistency and end to end connectivity. Breaking internet namespaces like this separates the user and person from the network and makes them completely dependent on mediation in the OS for reasoning about basic endpoints. If there is no distinction between files on your machine and on platform company machines, you are in a walled garden. Adding well known file extensions as TLDs will add a fundamental inconsistency that is just injecting chaos as a means to manage it. Yes, MSFT always had .com files and the internet survived, but that's an exception from a company that has never solved a problem they hadn't first caused.