Bit.ly’s Grand Plans, And Their Inevitable Clash With Digg: Bitly Now
techcrunch.com
techcrunch.com
As it is, the actual producer of the content being linked to has no idea where that link is on the web. Is it in a tweet? A blog comment? Where?
Bit.ly and other url shorteners are robbing content producers of valuable traffic information and giving it to the linker, but I would argue that it is much more important for the producer of the content to know who is clicking links and from where than it is for the person who links to the content.
This, of course, is one problem in addition to the increased layer of indirection and reduced reliability of content acquisition in the future due to the disappearance of the shortener.
Also it's not tenable to scrape aggregate stats in real time, which is half the value.
Additionally, why doesn't anyone talk about doing URL shortening on the CMS side? Sure the host portion of the URL might be a little longer than say 'bit.ly', but the remaining portion could be compressed. You could have a blog, news article, or whatever with an unobtrusive "twitter link" on the side. That way content owners still have some view into who is linking to their content.
Some sites do this. I bought some shoes the other day on Zappos and noticed all their permalinks have a shortened URL ready. Example: http://www.zappos.com/product/126799/color/53739
Amazon should do this if for no other reason than most of their URLs are giant and unfriendly.
The article posits the theory that Bit.ly, with access to more URL submissions a day has an advantage over Digg for that reason. I don't but it. The killer app of social book marking is as a filter. Bit.ly will still have to lick the filtering issue, just as other social book marking sites have had to. I just find it funny that the article seems to state that Digg receiving 20,000 links a day is a disadvantage when in reality, it's sort of the entire point of a service like that.
"20,000 or so new links a day are submitted to Digg"