4 ms·
I wouldn't have as much immediate issue with this if Twitter's own clients were acceptable - they are not. And this is an asinine move either way.
by lancewiggs 14y ago
I wouldn't have as much immediate issue with this if Twitter's own clients were acceptable - they are not. And this is an asinine move either way.
- k-mcgrady 14y agoTwitter's own clients are fine. You can read tweets and send tweets. That's the basis of the service. It's supposed to be simple. Why don't you like it?
- rcknight 14y agoThe mac client has not been updated since June 2011 ... hardly well supported!
- chris_wot 14y agoNot really a valid reason. What is it about the client that needs to be updated?
- smackfu 14y agoAmusingly, it doesn't even use Twitter's own picture service for photos attachments which is a year old at this point. It still uses yfrog.
- jcromartie 14y agoI never would have noticed, since it continues to work without any issues for me.
- Tichy 14y agoTweetDeck used to do Facebook+Twitter. Will they continue to work on the Facebook part? Unlikely - and there won't be other clients that do both...
- jopt 14y agoIs that really all there is to it? Are all apps equal provided they have CRUD?