7 ms·
This 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 p
by moehm 5y ago
This 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 5y 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 5y 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 5y 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 5y 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.