Re:A URL shortener not shortening the URL but makes it look ...
by ohadron on Wednesday February 01, 2023 @07:29AM
(#34609573)
Nicely demonstrates why outsourcing link shorteners is risky - they go out of business and your link is dead.
[ Parent
| on HN ]
Re:A URL shortener not shortening the URL but makes it look ...
by vlan121 on Wednesday February 01, 2023 @07:48AM
(#34609715)
Infact this is a problem that we'll face someday.
Re:A URL shortener not shortening the URL but makes it look ...
by comprev on Wednesday February 01, 2023 @08:04AM
(#34609839)
vb.ly is an example of this happening.
https://www.theguardian.com/technology/2010/oct/08/bitly-lib...
Re:A URL shortener not shortening the URL but makes it look ...
by neilv on Wednesday February 01, 2023 @08:23AM
(#34610024)
This was predicted and warned about when the link shorteners first appeared, decades ago.
But people keep using them (for a while for Twitter, but maybe mainly for analytics, though they could self-host and accomplish the same thing).
Re:A URL shortener not shortening the URL but makes it look ...
by eythian on Wednesday February 01, 2023 @09:17AM
(#34610713)
There is an archiveteam project to index all the shorteners and where they direct to. I think it's the default project if you're running the warrior and there's nothing more important going on.
Re:A URL shortener not shortening the URL but makes it look ...
by osteele on Wednesday February 01, 2023 @10:48AM
(#34612151)
In the case of non-shortening modifiers such as the OP, this can be fixed by using a reversible encoding. (This doesn't address actual shorteners, because of the pigeon-hole principle.) https://blog.osteele.com/2006/04/wideurl/ does this, so even though the referenced service itself is down, encoded URLs can be decoded by hand.
My hosting provider took the service down, IMO justifiably, because it could be used to encode malicious URLs. 2006 was a different time, before it was as obvious that services such as this would be used for this.