3 ms·
> What do you think? I think URL un-shortening should be done in the browser, on URLs that were shortened according to a standard hashing method, so your brows
by a3n 12y ago
> What do you think?
I think URL un-shortening should be done in the browser, on URLs that were shortened according to a standard hashing method, so your browser can tell you where the URL will go.
Shortening sevices are ridiculous and dangerous.
- dragonwriter 12y ago>I think URL un-shortening should be done in the browser, on URLs that were shortened according to a standard hashing method Hashing, by definition, is non-reversible. So if you use a hashing method as your shortening system, you'll have a fingerprint from which the actual destination is unrecoverable. > Shortening sevices are ridiculous and dangerous. Right, and there is no reason to use them in any situation where the target is a browser, anyway. It makes sense to use a shortening service if you are going to be sending a URL in an SMS message, but if its going to a browser, there's no reason not to use the full URL. So, really, a server based system that will send message both as SMS and to regular browser users should support a shortener and use it only when sending SMS.
- MichaelGG 12y agoYou're asking a 8-10 character string decompress to an arbitrary length string, and have the client be able to do the decompression. I think if you think about this for a few seconds, you'd find out that if you were able to create such a solution, you've have destroyed some information theory laws.
- a3n 12y agoYup, I was a technical loon for saying "hash". Nevertheless, I rarely follow a shortened URL (and I see many) because I don't know where they go.