6 ms·
So if it's a domain, you should fully qualify it: https://foo.zip https://foo.zip. Over time, this can become a convention. Part of the price you pay in using
by toomim 3y ago
So if it's a domain, you should fully qualify it: https://foo.zip https://foo.zip.
Over time, this can become a convention. Part of the price you pay in using a .zip domain will be that software doesn't auto-linkify it unless you prefix it with http(s)://.
- mike503 3y agoAnd with chrome leading it (IIRC) and other browsers following, end users don't even see http or https:// https:// prefixes in their browser bar anymore. Further adding to confusion. I don't see a reason for adding these new TLDs other than a cash grab.
- em-bee 3y agohiding the protocol prefixes was always a bad idea. the .zip domain would be an argument to revert that. but i don't have high hopes.
- dubcee349 3y agoW W W PERIOD FOO PERIOD ZIP
- mock-possum 3y agoSLASH DOT DASH DOT SLASH DOT DASH DOT SLASH DOT DASH DOT COM DOT COM DOT COM
- None4U 3y agoBut domains and protocols are orthogonal?
- simlevesque 3y agoThe domain has no relation to the protocol. I can own domains and never use http or https on them.
- CydeWeys 3y agoRight but if you're not hosting Web content then you wouldn't want it linkified in a Web context. If you're using it for something else, e.g. SMTP, then you'd represent the domain name differently as username@your.domain
- hammyhavoc 3y agoWhy wouldn't someone follow the standard of prefixing it with an appropriate subdomain? E.g., `smtp` or `imap` if it's something they're going to be discussing publicly? Furthermore, why not use port numbers as a suffix? That's how we can have umpteen services across different protocols on a single domain.