Crazy-er, I mean.
I ask b/c I recently bought a .co domain for a side project which will depend heavily on the domain similar to bit.ly, and my surface impression is that Columbia is stable enough for TLD risk not to be an issue. But there is the FARC, drug cartels, and probabaly some unknown unknowns as well, and this .ly issue is making me wonder if I should reconsider before irreversibly locking in this domain.
I remember seeing that bit.ly and maybe tr.im had an "open" approach to URLs and formed some sort of service where they allowed anyone to easily replicate their URL database? I can't find any trace if it though, so I might have the wrong services, but that might be a possible solution, companies like Twitter could utilise that to "rescue" a large number of links.
The right way to fix this if it all goes to shit would probably be at the DNS or browser level. At least then you have fewer people that you have to convince to change.
Do people really use URL shorteners for anything other than Twitter? (and,perhaps Rickrolling?)
I suspect you could delete every url shortener database right now, and after a week nobody would even notice. I'm pretty sure the majority of shortener uses are for Twitter (for obvious reasons, and who reads tweets more than a few days old?) and for intentional hiding of destination urls (Oh look, I'm pretending to provide useful information, instead I'm linking you to a funny cat picture!). I find it hard to believe any information or knowledge hidden behind bit.ly links is of any real value in improving the human condition...
(but I've been seriously wrong about emergent behavior amongst the general public before... I fully expect to have someone point out phd research papers with all the citations done with bit.ly links now...)
Are you _really_ suggesting that IANA or Microsoft/Mozilla/Apple/Google ought to be allowed to "hijack" some of Libya's .ly domain space, just to prop up the flawed business model of some <soundfx accent='Arrington'>dipshit little company</soundfx> ???
That way lies madness...
But think down the path you'd need to go if you chose to block bit.ly at the DNS level... Right now, IANA's root name servers delegate all .ly requests to name servers under Libya's control. I'm pretty sure there's no mechanism in place for the root servers to change that to "send all .ly requests to Libya _except for_ bit.ly requests, and serve them ourselves or send them elsewhere", and in my opinion there _shouldn't_ be any such mechanism because of the potential for abuse at government levels - would you want the Chinese government to know IANA has the ability to redirect traffic from domains they don't like?
So the _other_ alternative seems to be to have IANA refer all .ly requests to a new tld authority. Same problem - if you do that once, especially if you do it just to protect a company's profits/business model, how do you refuse a request from China to assume control of all of Tibet's tld?
Suggesting DNS level changes for bit.ly seems to me to open a whole can of very ugly worms...
And this, kids, is yet another example of why URL shortening services should be avoided. They've single-handedly put ability to break the functionality of a growing chunk of the internet into the hands of one demonstrably unstable dictator in a developing nation.