:Symbolism - Since you’re not going to fucking help with Paws ...

Archive

Aug
4th

Thu

<+elliottcable> Since you’re not going to fucking help with Paws
<+elliottcable> would one of you colossal cunts write me a command-line Twitter client that ISN’T FUCKING RETARDED?
<+elliottcable> My requirements are so minimal as to be laughable, and yet NOT A SINGLE CLIENT CAN MEET THEM. OH MY GOD FUUUU.
< devyn> elliottcable: well, what are your criteria?
<+elliottcable> A) streaming API. I need tweets *as soon as they happen*.
<+elliottcable> A1) the user-data portion of the streaming API (and since this is a command-line client, we can break Twitter’s rules, and I expect to see unfollowed/deleted actions bubbled to the surface!)
<+elliottcable> B) *sane* conversation-threading-handling (read: Tweetbot-style)
<+elliottcable> C) support for using lists instead of the timeline, but in the exact same way (i.e. “select a given list, and that list becomes your timeline”)
<+elliottcable> THAT’S IT.
<+elliottcable> oh
<+elliottcable> and D, E, F, G, H, and I): DON’T.
<+elliottcable> FUCKING.
<+elliottcable> T.CO.
<+elliottcable> MY.
<+elliottcable> FUCKING.
<+elliottcable> LINKS.
<+elliottcable> Some of these are against Twitter’s terms-of-service for client devs nowadays
<+elliottcable> and you know what? I DON’T CARE.
<+elliottcable> Give me a client where I can put my own “application” keys in there, and I’ll just keep generating new ones when Twitter bans them. They can fuck the hell right off with their retarded, Apple-esque “We hate all of you client developers!” shit.
< devyn> elliottcable: how's Tweetbot's conversation threading work?
<+elliottcable> t.co can suck a dick; then the inability to bubble-up tweet deletions or unfollow events can take that dick up the ass. Finally, t.co can suck the shit off of aforementioned dick when it’s done with aforementioned inability to bubble.