Live data from Hacker News

A URL Lengthener

aaa.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.com

181–190 of 313 posts

Re: A URL Lengthener

#183

you got a xss bro https://aaa.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa...

Thought I'd comment to note that (as of 2021-05-14T22:07:00Z) this just does the alert() POC and isn't nefarious, if anyone is deeply curious enough to click but cautious enough to avoid a deaddove.jpg situation

Just fixed this a few minutes ago, thanks to those who told me about it! (look for v1.4.2 on npm and the corresponding commit on github)

Re: A URL Lengthener

#184
post #10
post #3

Love it. This is going in the toolbox along with http://shadyurl.com

Lol. I clicked this on my (managed) work laptop, and immediately got a Compliance warning popup. I don't know what I expected...

Same. "Your organization's policy prohibits access to websites categorized as Tasteless & Offensive.". How rude!

Re: A URL Lengthener

#185
post #169
post #159

Earlier quoted context omitted.

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!

The A record was never in the root zone. The root zone has an NS record for ai TLD which delegates authority to ai nameservers.

You can try `dig @a.root-servers.net ai NS` to get the nameserver `a.lactld.org.` which is authoritative for ai. You can now try `dig @a.lactld.org ai A` to get it (that's how recursive resolves generally work)

Re: A URL Lengthener

#188

you got a xss bro https://aaa.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa...

doesn't work anymore >:) with the pure speed of replit i went from issue opened to closed in like 20 minutes

Wait could you explain a bit more how replit let you fix it so quickly

Re: A URL Lengthener

#189

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…

>http://llanfairpwllgwyngyllgogerychwyrndrobwllllantysiliogog...

Welsh place names can be brilliantly literal, Aberystwyth for example is "mouth of the river Ystwyth". Llanfairpwllgwyngyll... means "St Mary's church of the pool of the white hazels over against the pool of St Tysilio Gogo" but the name was completely contrived in the Victorian era to promote tourism to Anglesey.

Re: A URL Lengthener

#190

Earlier quoted context omitted.

doesn't work anymore >:) with the pure speed of replit i went from issue opened to closed in like 20 minutes

Wait could you explain a bit more how replit let you fix it so quickly

Well, I use Replit as an ide and just hitting the run button meant my fix was immediately deployed. didn't have to push to git or wait ssh into a machine to pull from master and restart
Post reply on HN