Y
Hacker News
new
|
ask
|
show
|
jobs
by
lancewiggs
5048 days 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.
1 comments
k-mcgrady
5048 days ago
Twitter'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?
link
Tichy
5048 days ago
TweetDeck 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...
link
rcknight
5048 days ago
The mac client has not been updated since June 2011 ... hardly well supported!
link
chris_wot
5048 days ago
Not really a valid reason. What is it about the client that needs to be updated?
link
smackfu
5048 days ago
Amusingly, 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.
link
jcromartie
5048 days ago
I never would have noticed, since it continues to work without any issues for me.
link
jopt
5047 days ago
Is that really all there is to it? Are all apps equal provided they have CRUD?
link