3 ms·

TLD-insensitive request sounds like a nice feature: when you type cia.org and is redirected to cia.gov

by GoblinSlayer 3y ago

Sophira 3y ago
Except when you want to find out more about the x.org X11 server and get redirected to Twitter (x.com).
- zamadatix 3y ago
  Was there ever a time someone who wanted to find out more about xorg x11 knew (without already knowing about it) to just type "x.org" instead of "x11.org" or "xorg.org" or "xorg.com" or "xserver.org" and so on, finding non-existent responses or alternative groups who call themselves x? Collision and needing to "divine" the domain seem inherent to having a name system. Both this and the need for a TLD-insensitive lookup were solved by making the address bar also the search bar so people can use search engines to find new things instead of DNS.
Joker_vD 3y ago
Of course, the actual solution to this minor problem turned out to be the web search engines.
- GoblinSlayer 3y ago
  Do you trust them to not send you to a phishing site?
  - Joker_vD 3y ago
    About as much as I trust the DNS to not send me to a phishing site.
delfinom 3y ago
Aka, all TLDS become worthless and the guy with the most money wins?
- GoblinSlayer 3y ago
  They already serve informational purpose at best, the site belongs to a tld with certain restrictions, but why tld restrictions should be expressed in the domain name?
  - Sophira 3y ago
    TLDs can be thought of as namespaces, and they have good reason to exist. For one thing, changing how domains work like this would massively drive up the cost of any one domain to the point where hobbyists and open-source projects would be priced out. I have a few domains, none of which are duplicated across different TLDs, and each of which serves a different purpose. It would have been pretty much impossible for me to do this if everything was under one namespace. In addition to the price aspect, it would pretty much force the system into being a much more restrictive version of the already-existing trademark system - except that there wouldn't even be any exceptions for different fields, as there is in the current trademark system. For example, one of my domains coincidentally (and unknowingly at the time I registered it over 20 years ago) collides with the name of a movie. It's in a completely different field (actually, it's a personal, non-commercial site for me and not much is public on it) but I almost certainly wouldn't have been able to get it if TLDs didn't exist.
    - GoblinSlayer 3y ago
      If you have no duplicates, why can't you have them under one namespace? Namespaces are supposed to separate duplicates so that they don't conflict. Without duplicates namespaces don't serve their purpose. TLDs can be kept as a supplementary technical information, like, e.g. cname.
      - Sophira 3y ago
        But there are duplicates. There are a vast number of cases where a domain name under one TLD isn't held by the same person/company who holds the same domain name under another TLD.

TLD-insensitive request sounds like a nice feature: when you type cia.org and is redirected to cia.gov

Sophira 3y ago

Except when you want to find out more about the x.org X11 server and get redirected to Twitter (x.com).

zamadatix 3y ago
Was there ever a time someone who wanted to find out more about xorg x11 knew (without already knowing about it) to just type "x.org" instead of "x11.org" or "xorg.org" or "xorg.com" or "xserver.org" and so on, finding non-existent responses or alternative groups who call themselves x? Collision and needing to "divine" the domain seem inherent to having a name system. Both this and the need for a TLD-insensitive lookup were solved by making the address bar also the search bar so people can use search engines to find new things instead of DNS.

Joker_vD 3y ago

Of course, the actual solution to this minor problem turned out to be the web search engines.

GoblinSlayer 3y ago
Do you trust them to not send you to a phishing site?
- Joker_vD 3y ago
  About as much as I trust the DNS to not send me to a phishing site.

delfinom 3y ago

Aka, all TLDS become worthless and the guy with the most money wins?

GoblinSlayer 3y ago
They already serve informational purpose at best, the site belongs to a tld with certain restrictions, but why tld restrictions should be expressed in the domain name?
- Sophira 3y ago
  TLDs can be thought of as namespaces, and they have good reason to exist. For one thing, changing how domains work like this would massively drive up the cost of any one domain to the point where hobbyists and open-source projects would be priced out. I have a few domains, none of which are duplicated across different TLDs, and each of which serves a different purpose. It would have been pretty much impossible for me to do this if everything was under one namespace. In addition to the price aspect, it would pretty much force the system into being a much more restrictive version of the already-existing trademark system - except that there wouldn't even be any exceptions for different fields, as there is in the current trademark system. For example, one of my domains coincidentally (and unknowingly at the time I registered it over 20 years ago) collides with the name of a movie. It's in a completely different field (actually, it's a personal, non-commercial site for me and not much is public on it) but I almost certainly wouldn't have been able to get it if TLDs didn't exist.
  - GoblinSlayer 3y ago
    If you have no duplicates, why can't you have them under one namespace? Namespaces are supposed to separate duplicates so that they don't conflict. Without duplicates namespaces don't serve their purpose. TLDs can be kept as a supplementary technical information, like, e.g. cname.
    - Sophira 3y ago
      But there are duplicates. There are a vast number of cases where a domain name under one TLD isn't held by the same person/company who holds the same domain name under another TLD.