News for hackers. Stuff that matters.
Re:Introducing Twitter premium APIs by porfirium on Tuesday November 14, 2017 @01:26PM (#15697742)
They never "locked it down", they just rate limited some vital endpoints and never bothered to add endpoints for new, important features.

My own recommendation: disassemble any official app (for example, the Android one with apktool) and get the tokens and endpoints and do whatever the hell you want without paying a cent.

Re:Introducing Twitter premium APIs by chimeracoder on Tuesday November 14, 2017 @03:11PM (#15698683)
> They never "locked it down", they just rate limited some vital endpoints and never bothered to add endpoints for new, important features.

More importantly: they introduced a lifetime cap on the number of OAuth tokens that applications could create, which meant a lifetime cap on how many different users a Twitter client could support. Once you hit your Nth user, you could never have a new person authenticate that client.

That killed off basically every decent third-party Twitter client.

Re:Introducing Twitter premium APIs by 0x0 on Wednesday November 15, 2017 @12:14AM (#15701619)
In the beginning you could post a tweet just by doing a http basic-authenticated post containing the tweet body, and there were unauthenticated rss feeds for most data feeds. These days you have to create app ids, tokens, etc etc etc. It really was a lot more open earlier.
Re:Introducing Twitter premium APIs by herbst on Wednesday November 15, 2017 @01:24AM (#15701822)
Twitter was part of the reason I fell in love with development. The easy interaction with the whole platform changed my view on data. It broke my heart when they introduced v2
Re:Introducing Twitter premium APIs by komali2 on Tuesday November 14, 2017 @01:33PM (#15697815)
I feel like you could do this just watching network traffic, and judging by the fact that nobody's done it, I also feel like there's some mechanism preventing this that I'm not knowledgeable enough in the subject to be aware of.
Re:Introducing Twitter premium APIs by porfirium on Tuesday November 14, 2017 @01:36PM (#15697844)
You can't do this just watching network traffic because the apps use HTTPS + certificate pinning.

And you can do it if you want. I do it. I'm sure many more people do it.

Re:Introducing Twitter premium APIs by passivepinetree on Tuesday November 14, 2017 @02:00PM (#15698072)
Out of curiosity, what do you use the decompiled tokens/endpoints for?
Re:Introducing Twitter premium APIs by praneshp on Tuesday November 14, 2017 @02:26PM (#15698307)
The official twitter app is possibly using these premium endpoints, so it's token has access to those. If you "grab" that token(s) somehow, you can go ahead and use it in your app, I presume. I don't know how this will work when your app wants to connect to someone else's account, however.
Re:Introducing Twitter premium APIs by __sha3d on Tuesday November 14, 2017 @05:17PM (#15699720)
You think all the russian bots are on the official API? Nope.
Re:Introducing Twitter premium APIs by porfirium on Tuesday November 14, 2017 @02:26PM (#15698305)
Nefarious purposes, mostly. I can crawl without rate limits (well, there are rate limits, but it's much harder to hit them), and I also can spam a lot without getting my account flagged (but it eventually gets flagged, of course).

By spamming I don't mean the usual "click on this link and I'll show you my tits" spam; if you create a useful bot that sends "expected" mentions (for example in response to mentions you receive, and not just spam) it will get banned in a matter of hours. With their "secret" tokens, it won't get banned.

Re:Introducing Twitter premium APIs by gsich on Tuesday November 14, 2017 @02:14PM (#15698194)
A rooted device should suffice, but it is a painful procedure.