@chris_martin they'll use less ram per instance at least (it'd be difficult to use more)

@whitequark @munin I kinda feel like their dysfunction these days is mostly in management/product management not engineering so much, but also a fair point. Even relatively short (few days) downtimes could tend to kill a client though, I'd guess.

@whitequark @munin fair point. wasn't aware it was that popular.

@whitequark @munin sure sure. my point is just at twitter they're not actually dumbshits except in the obvious ways so if you get any sort of popularity on your combined client you'll certainly have periods of being blocked on it, which is kinda the death knell for a client even if you _can_ mostly keep up with countermeasures.

@whitequark @munin Back in the day, Twitter was blocking API keys from individual users (they blocked mine) if they used them with Falcon on Android (which was at token limit). Not that that would necessarily happen here, but they've done client detection beyond just the API key before. Can be worked around obviously by mimicing official client more exactly but then you're just in an arms race.

@whitequark @munin Yeah. Think that only works as long as Twitter doesn't notice and get you yanked from the app stores, though. And/or throws lawyers at you.

@munin @whitequark Twitter will revoke your API key as soon as they notice, unfortunately. They did it before with several app.net clients.

@HolicShot @0xdeadbabe and better let you set location where [show more] happens in that range.

@0xdeadbabe til