Hacker News
new
|
past
|
comments
|
ask
|
show
|
jobs
|
submit
login
lancewiggs
on Aug 17, 2012
|
parent
|
context
|
favorite
| on:
Twitter to Client Developers: Drop Dead
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.
basisword
on Aug 17, 2012
[–]
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?
Tichy
on Aug 17, 2012
|
parent
|
next
[–]
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...
rcknight
on Aug 17, 2012
|
parent
|
prev
|
next
[–]
The mac client has not been updated since June 2011 ... hardly well supported!
chris_wot
on Aug 17, 2012
|
root
|
parent
|
next
[–]
Not really a valid reason. What is it about the client that needs to be updated?
smackfu
on Aug 17, 2012
|
root
|
parent
|
next
[–]
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.
jcromartie
on Aug 17, 2012
|
root
|
parent
|
prev
|
next
[–]
I never would have noticed, since it continues to work without any issues for me.
jopt
on Aug 17, 2012
|
parent
|
prev
[–]
Is that really all there is to it? Are all apps equal provided they have CRUD?
Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4
Guidelines
|
FAQ
|
Lists
|
API
|
Security
|
Legal
|
Apply to YC
|
Contact
Search:
