by Alec Muffett
Three simple steps:
1) Put the shortening in the twitter-client where it belongs, remove it from the server-side
2) Make it optional for the user to use
3) Encourage the above in the Twitter API documentation
Is that unreasonable?
Extracted from comments on the original blog post.
I would say that was quite reasonable and sensible.
If Twitter wanted to do that in the web interface it should be a web2.0 interface providing the same sort of facilities as the clients (i.e. personalised options and full control over things like shortening etc)
[…] http://www.crypticide.com/dropsafe/article/3423 <- How to address #stopshortening ; apology, twitter streams trash URLs in long tweets # […]
Leave a Reply