4 ms·
That actually strikes me as anachronistic, because it became popular to drop "www" (not only in print media, but also in the canonical FQDN) well before these s
by hunter2_ 6y ago
That actually strikes me as anachronistic, because it became popular to drop "www" (not only in print media, but also in the canonical FQDN) well before these sort of TLDs became available.
- moehm 6y agoThis is correct, though I still believe most people understand the meaning that it's a website if I prepend the "www". On the other hand, I guess most people probably aren't typing the url out anyway but googling it instead.
- walrus01 6y agoAlso correct, though using my example and weird new TLDs, let's say in a theoretical example I see a bus stop outdoor advertising board on the street that says: "BURRITO.CONSULTING" I'm going to think, "uhhh, is that a website? Well, I recognize .consulting as a TLD. I guess it must be. But that's weird..." but then if i see the same sign "WWW.BURRITO.CONSULTING" I'm going to think: "Well that's definitely somebody's website, but what a weird and anachronistic way of printing it, and why is it using one of those new long generic TLDs anyways..."
- deepstack 6y agoyeah it is a techy thing. Most people who are not techy use "WWW", we just got to go with this. Edit your web server config to handle that.
- stephenhuey 6y agoExactly. There is plenty of discussion to be found online in techie circles, but in short, if you’re going to use a naked domain to host your website, at least redirect www to it.
- fogihujy 6y agoYes, 'www.burrito.consulting' looks akward, but most people born after 1960 will recognize it as the URL for a web site. People outside tech generally don't realise that domain.tld and www.domain.tld are two separate hostnames, and adding www. makes it much more recognizable to the general public.
- deleted 6y ago[deleted]
- toshk 6y agoOn sites for government we always have lot of confusing emails if we don't also make the www in front of subdomains work: So for subdomain.burrito.com, we redirect the wwww.subdomain.burrito.com People are just so used to it.
- Mauricebranagh 6y agoNo that was just idiots being fucking lazy
- hunter2_ 6y agoLazy? Running without www can actually be a decent amount of work: 1. Avoiding the relatively common pairing of {a host whose IP address changes without warning so you need to CNAME it; a DNS provider that doesn't offer CNAME flattening a.k.a. ALIAS a.k.a. ANAME}. 2. Scoping session cookies so user agents don't also send them to your subdomains. And maybe even more stuff I'm forgetting.