November 30, 2010 | SQL Server

[OT] : An open blog post to bit.ly

I am not sure when it happened, but at some point, bit.ly marked all URLs to connect.microsoft.com as dangerous.  So for example, I created this shortened link http://bit.ly/fKKQPT which just goes to http://web.archive.org/web/*/https://connect.microsoft.com/sql/.  When you click on the shortened link, you get the following warning (click to embiggen):

 

Unfortunately, bit.ly is the default URL shortening service in tweetdeck, and a lot of people don't even realize what is happening when people click on the links that have been shortened on their behalf. The clickers may not ultimately click through to the link because of the big red hand (or because they can't find the link way down the page).  In several cases I have seen quite knowledgeable folks follow up on a connect link suggesting that the link was bad or must have been mangled.  And worse yet, some people may suddenly think I'm a bad guy distributing phishing or other dangerous links.  Not cool.

Now, I like some of the benefits that bit.ly provides, such as optional link customization, API integration into tweetdeck, detailed stats and aggregation, etc.  But until the global "all connect URLs are poison" ban has been lifted I, for one, have changed my URL shortening service to is.gd:


 

5 comments on this post

    • cinahcaM madA - November 30, 2010, 9:42 PM

      Have you tried contacting bit.ly about this? If not, I will.

    • SQLvariant - November 30, 2010, 9:48 PM

      Since you're blogging about stuff like this would you mind pointing out to tweetdeck that when you switch over to the "light" theme > then go back into settings: the words "Minimize button should" are no longer visible on the General tab?
      😀

    • AaronBertrand - November 30, 2010, 9:52 PM

      Adam, yes I have sent them feedback, and have also pointed them to this blog post.

    • AaronBertrand - November 30, 2010, 9:59 PM

      Aaron, that's different.  The bit.ly issue actually disrupts me.  The other one does not.

    • Jason Coombes - December 1, 2010, 3:32 PM

      I believe this started happening around the time that the announcement was made that Drive Extender would be removed from Windows Home Server. This has generated a lot of tweets with shortened links to the same URL:
      http://web.archive.org/web/*/https://connect.microsoft.com/WindowsHomeServer/feedback/details/624029/add-drive-extender-back-to-vail
      This must have triggered some protection that bit.ly uses. As of writing that connect case has over 4,000 votes.

Comments are closed.