Seems so, at least it's the database which failed and not the web server. A web server failure on a site covering real-time web servers news would be too weird.
It is not supposed to be safer - it's only purpose is to help you let your friends know what kind of content they are going to see - I hate clicking bit.ly just to see it's a TechCrunch link, which I usually don't like reading, same goes for video links.
It is not supposed to be safer or easier to remember - it's just supposed to help you let your friends know what kind of content they are going to see - I hate clicking bit.ly just to see it's a TechCrunch link, which I usually don't like reading, same goes for video links.
This is also based on a great open source script (yourls.org) which also has a wordpress plugin but most content websites do not seem to care about this and keep using services similar to ShareThis which create bit.ly links.
I wish services like ShareThis would let site owners point an A record to their servers and host a URL shortening service for their domains.
URLs are longer than usual shortened URLs but are still much shorter than most sites' inner links.
Thanks! I changed it to cut names longer than 7 characters to 7 characters.
If anyone finds this useful then I might create a set of words and a shorter but understandable replacement.
('development' to 'dev', 'photography' to 'photo', 'technology' to 'tech', etc.)
I think that nowdays the 140 char restriction is for keeping Twitter clean and readable, making it harder on the writer and easier on the reader - links are not hard to read and therefore there is no reason to restrict their length.
Also, users who actually use Twitter via SMS would probably not be capable of viewing the link anyhow so it could just say "(+lnk)" or something.
Shortened links are misleading, I might have not clicked your links if you wouldn't be hiding it. (already seen it, hate that specific blog, etc) - this makes your stats wrong cause many people might have clicked the link and closed it right away.
Last time I checked, bit.ly's statistics were counting all kinds of bots and did not allow filtering by useragent - they might have fixed this but in case they didn't then your stats are way wrong.