pageoneresults - 3:23 pm on Mar 10, 2010 (gmt 0)

Since these attacks occur primarily on Direct Messages and email notifications about Direct Messages, this is where we have focused our initial efforts.

This only applies to DMs and Email Notifications. They've not yet interfered with URIs in public Tweets.

I've been thinking about what this does and it really opens up a can of worms. I saw an article yesterday discussing the benefits of this and that the 301 > 301 > 200 passed full link juice when the original URI Short is converted again via Twitters new service. They're just adding to the cluster, the hair on my neck was tingling when I saw that second 301. I don't know about you but I feel that second 301 is where loss begins, the first 301 is lossless.

If this ever does go to public Tweets, I think there will be some major fallout. The more I think about it, the more I KNOW they wouldn't do that. No, I think they need to address it further up the source chain, not with another layer of potential technical malfunction.