Shortest URLs on the Internet
21–30 of 208 posts
Re: Shortest URLs on the Internet
#22Earlier quoted context omitted.
Why does 1.1 resolve to 1.0.0.1? I don't recall this being in any of the documents about CIDRs. Are browsers implicitly mapping IPv4 addresses temporarily into IPv6 addresses during parsing, such that "1.1" becomes "1::1", and then gets IPv6 abbreviated-form expansion applied to it?
I suspect it gets mapped to 1.0.0.1 because no other resolution is possible. Any other locations for the two zeros results in an invalid IP (either starting or ending in 0).
Absolutely nothing wrong with ending with a .0.
I suspect you are confused by n.n.n.0/24 being a network address in a /24 network which is obviously very common. However there are way more networks of other sizes that have .0 addresses in them.
Re: Shortest URLs on the Internet
#23Cool to know, i guess. TIL that dotless record on newer gTLDs is forbidden, which explains my age-old question: "if google holds google., why are they only using it on domains.google? Surely having the url https://google would be desirable for the folks in marketing?". The answer is that they can't possibly because the ban was added precisely because of this.
Google actually serves a bunch of pages through their TLD:
Re: Shortest URLs on the Internet
#24At one point of time, ` http://to ` resolved to a "It works!" page [1]. I've always thought it would be cool to have a URL shortener with links such as ` https://to/library ` or something similar. Oh, how much fun running your own TLD would be... [1] https://web.archive.org/web/20150319211308/http://to/
unfortunately, it seems like ICANN rules prevent this for new gTLDs
Re: Shortest URLs on the Internet
#25Re: Shortest URLs on the Internet
#26I love short URLs! I found quite a lot are available for .cx (which is the Christmas Islands), so I got https://fh.cx for myself a couple of years ago.
Re: Shortest URLs on the Internet
#27Earlier quoted context omitted.
I suspect it gets mapped to 1.0.0.1 because no other resolution is possible. Any other locations for the two zeros results in an invalid IP (either starting or ending in 0).
Absolutely nothing wrong with ending with a .0. I suspect you are confused by n.n.n.0/24 being a network address in a /24 network which is obviously very common. However there are way more networks of other sizes that have .0 addresses in them.
We're also arguing that it ought to become usable even in a /24: https://datatracker.ietf.org/doc/draft-schoen-intarea-unicas...
It only requires changes within the LAN to accomplish this, since distant hosts are already not supposed to assume anything about how networks are or are not subnetted. (For instance, they don't know whether you're on a /24 or not.)
You can find some addresses ending a lot of zeroes that already work within
Re: Shortest URLs on the Internet
#28At one point of time, ` http://to ` resolved to a "It works!" page [1]. I've always thought it would be cool to have a URL shortener with links such as ` https://to/library ` or something similar. Oh, how much fun running your own TLD would be... [1] https://web.archive.org/web/20150319211308/http://to/
At Google and many other tech companies, internal machines are configured to have go/ work just like you describe. Looks like someone even made a whole company around it
Re: Shortest URLs on the Internet
#29At one point of time, ` http://to ` resolved to a "It works!" page [1]. I've always thought it would be cool to have a URL shortener with links such as ` https://to/library ` or something similar. Oh, how much fun running your own TLD would be... [1] https://web.archive.org/web/20150319211308/http://to/
I wrote myself a Chrome extension that does this, using http://l/foo style links, and using Chrome's sync to share across devices. Works well enough but limited to desktops.
Some large orgs maintain internal shorteners, like http://go links at Google.
Re: Shortest URLs on the Internet
#30At one point of time, ` http://to ` resolved to a "It works!" page [1]. I've always thought it would be cool to have a URL shortener with links such as ` https://to/library ` or something similar. Oh, how much fun running your own TLD would be... [1] https://web.archive.org/web/20150319211308/http://to/
At a previous employer, we used an internal link shortener that went like http://go/whatever. Very user friendly.