Technology

The final piece is that often each of those services would be on a different computer entirely, each with a different public IP address. Otherwise the port is sufficient to sperate most services on a common domain.

There was a good long while where IP addresses were still unutilized enough that there was no reason to even try being conservative.

Well also at one point www.domain.com may have actually been a single physical server. That hasn't been true for sites of any size in a long time.

That's a 5-minute workaround in the server config. Hate it when idiots skip that. I'm no dev, but I've done it many times.

www is just a host name, totally arbitrary.

I prefer it, so I just redirect HTTP requests my root domain to the www version. I think it makes a ton of sense, since I www is merely one of the many services I host at my domain.

Oh thank god that last word was “winking.”

Wonmiserating?

I don't remember that episode, but that's a good pull. I imagine coach did not understand.

and then I sign it "Movie Guy"

is Movie Guy your pseudonym?

no it's just a name I use instead of my real name

I love Home Movies

You can return multiple A/AAAA records for the root, the TLD delegates the whole thing to your nameservers and it's free to return whatever you want. Registrars actually do let you set records on the TLD's zone, it's called glue records and they're typically used to solve the nameserver chicken and egg problem where you might want to be your own nameservers. Mine's set that way:

~ $ drill NS max-p.me
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 32318
;; flags: qr rd ra ; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; max-p.me.    IN      NS

;; ANSWER SECTION:
max-p.me.       3600    IN      NS      ns2.max-p.me.
max-p.me.       3600    IN      NS      ns1.max-p.me.

The me registrar will give you the IP for those two so you can then ask my server for where max-p.me really is.

The bigger issue is usually there's a bunch of stuff under your root domain like MX records, TXT records, potentially subdomains. That's a huge problem if you need to CNAME the root to a hosting provider, as the CNAME will forward the entire domain including MX and TXT records. Cloudflare sort of works around that with server side flattening of CNAMEs, but that's not standard. But if you have a www subdomain, then it's a complete non-issue. And really, do you want to delegate your MX records to WP Engine?

The main reason people went without the www is the good old "it looks cooler and shorter" while ignoring all the technical challenges its brings, and that's probably why browsers now hide the www so that website designers don't have to do this atrocity.

Archie and Veronica.

Plus domains should've gone left to right in terms of root, tld, domain, subdomain, etc., instead of right to left.

They even don't support HTTPS on the older articles for that authentic 2009 internet

i like how saying "word wide web" is faster than saying "www"

My favorite part of watching WWE is the way their main commentator says "WWE". You can tell he savors every syllable of it

How else would you say it?

"Wwwwuuuuhh dot Google dot com"?

Edit: or I guess, "world wide web" would make more sense?

Same thing in French. Doublevédoublevédoublevé. So. long.

Ideally you want to do one or the other unless you really like the redirect loop error page in your browser.

In the earliest days you absolutely did, it became optional later; especially once gopher:// stopped being a thing