4 ms·
Present these two domain names to the average person: 1) benedict.cumberbatch.name 2) drstrange.co.uk I expect the average person would assume that for the d
by jawns 1mo ago
Present these two domain names to the average person:
1) benedict.cumberbatch.name
2) drstrange.co.uk
I expect the average person would assume that for the domain 1, .name is the TLD, cumberbatch.name is registered by a private entity, and benedict (and any other subdomains associated with cumberbatch.name) is a subdomain fully controlled by that private entity.
Whereas for domain 2, I think the average person will view ".co.uk" the same way they view ".com", even though technically it is both a ccTLD and a second-level domain.
- swiftcoder 1mo agoLuckily the average person has no idea what a TLD or a subdomain are
- account42 29d agoThey do if they are employed in a non-tiny company where they work at least partially on a computer and paid attention during security training.
- angoragoats 29d agoEven if I agree with you that the "average person" meets the 3 specific criteria you list (which I don't), I don't believe the claim that the typical security training includes specific instruction in how TLDs and domain registration work, at least not in enough detail for a person to be able to follow the discussion we're having here.
- swiftcoder 28d ago> I don't believe the claim that the typical security training includes specific instruction in how TLDs and domain registration work Mine just has an animated llama telling me not to click suspicious links in emails
- angoragoats 29d agoThe average person doesn’t have the foggiest idea how TLDs, DNS, or domain registration work at all. The only people who will make the assumptions you state are people who are tech-savvy enough to be familiar with those concepts, but not well-versed enough in them to understand the nuances we’re discussing. And none of this does anything to advance the argument that .name is somehow nonstandard.