Live data from Hacker News

A URL Lengthener

aaa.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.com

161–170 of 313 posts

Re: A URL Lengthener

#161

Somewhat related https://news.ycombinator.com/item?id=19511735 (45 points | March 28, 2019 | 32 comments) https://news.ycombinator.com/item?id=24229085 (17 points | 8 months | 7 comments)

The multiple efforts thing is a lesson I should learn but refuse to do. It just feels so spammy. I don't want to touch that world intentionally but it works. It gets worse I had two similar services, one that used a page's meta information to create URL stubs so that the link would have the semantic meaning in it instead of say "id=27158278". It'd also (this is about 10 years ago) fill in opengraph holes if found and…

I don't understand. Are you the creator of the other service?

Re: A URL Lengthener

#162

Back in the early days of web hosting I recall that a customer had a domain name that was literally as long as ICANN would allow at the time. It was very nearly a full sentence. I don't recall the limit but this domain aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.com is 57 characters (not including .com) and I think that sounds familiar. One could have a lot of fun with that if they wanted to (and such as…

I remember this one: http://www.modestapparelchristianclothinglydiaofpurpledresse... - sadly, it appears they gave up the site, but Wayback Machine also remembers it.

Re: A URL Lengthener

#163
post #155

Earlier quoted context omitted.

I made a service to store arbitrary files as URLs that is similar. The hard part is files that are too large, I can handle files up to 5mb if you click on them all via local storage. Compression helps a lot as making them base64 increases the size quite a bit. https://podje.li

Could you make whole webpages just through urls? Such as they will completely portable? Portable being taken with a grain of sand ofc.

not the entire content, but a hash id is pretty common https://en.wikipedia.org/wiki/Magnet_URI_scheme

Re: A URL Lengthener

#165
post #36

fun fact. in the browser wars of 1993(?) i looked at the specs from netscape (mozilla dady for the young folks) and microsoft (what w3c? ha!) and netscape release a browser spec that said "X must support up to Y", as in "url must be up to 1024 chars", "cookies must be up to 1mb", etc... then microsoft release IE4 (or 6?) web spec. It was literally a copy of netscape's but with "up to" replaced with "at least". and fr…

Do you happen to have the exact wording? As far as I can tell these mean the same thing. 1. "You must support URL length up to 100 characters" -> your browser must support URLs that are 100 characters or less (and may or may not support longer ones) 2. "Your supported URL length must be at least 100 character" -> You must support URLs that are 100 characters or less (and may or may not support longer ones)

Didn't you confuse 'at least' with 'at most'?

Re: A URL Lengthener

#167
For the curious, aaa[...].com is just converting your string to hex, and then replacing the hex with various types of "A"'s.

If you wanted to use an alphabet other than 16 characters, you could do arbitrary base conversion: https://convert.zamicol.com/

This would allow you to use more or less characters.

Re: A URL Lengthener

#169
post #159
post #120

Earlier quoted context omitted.

But... it doesn't have a DNS record anymore!

You sure? $ dig +noall +answer ai. ai. 80534 IN A 209.59.119.34

Huh, this is weird!

The DNS record is no longer in the root zone itself (I think it used to be?) and some recursive resolvers seem to filter out the bare-TLD query or response. But the A record still exists inside the ai zone... so I'm not sure who is right, so to speak!

Post reply on HN