Twitter Cracks Down on API Abuse, Will Charge B2B Developers (techcrunch.com) 33
To prevent its own Cambridge Analytica moment and make sure it's getting paid for its data, Twitter said today it will audit developers that use its APIs. From a report: Starting June 19th, Twitter will require developers of any app that calls recent tweets from or mentions a user more than 100,000 times per day to submit their app for review. If a developer proves they have a legitimate consumer use case, like running a third-party Twitter client or doing research, they'll be granted free access to the API at the same rate they have today. If they primarily use the data to serve business customers as a B2B tool, like for customer service or social media monitoring, they'll have to pay to enter a commercial licensing agreement with Twitter with a custom price based on usage. Twitter refused to even specify the range those prices fall into, which won't win it any extra trust.
Developers found to be breaking Twitter's policies will be booted from the platform, while those that don't submit for review will be capped at 100,000 requests per day for the user timeline and mentions APIs. Twitter says it suspended 162,000 apps in the second half of 2018, showing it's willing to play hardball with developers that endanger its ecosystem.
Developers found to be breaking Twitter's policies will be booted from the platform, while those that don't submit for review will be capped at 100,000 requests per day for the user timeline and mentions APIs. Twitter says it suspended 162,000 apps in the second half of 2018, showing it's willing to play hardball with developers that endanger its ecosystem.
API abuse? (Score:4, Interesting)
How can you call any use of an API that you published as abuse? If you do, you're doing it wrong.
Re: (Score:2)
How can you call any use of an API that you published as abuse?
By violating the intention of the publication of the API. The intention here was to enable to user applications to post to and read Twitter. Abuse would be harvesting all of the information posted to Twitter.
If you do, you're doing it wrong.
Poppycock! Anyone can abuse an interface. Take for a second to consider HTTP. With HTTP if you have millions of computers request pages repeatedly from a single server while discarding the result you can deny other people the ability to access the page as well as drive up the cost of hosting the pa
Re: (Score:2)
Ever hear of throttling? If you write an API to consume bulk data like this unintentionally or you allow API consumers to beat the shit out of your service layer than then change the API or your infrastructure! If you publish an API that circumvents your policies then you're a dipshit for publishing it in the first place or your stakeholder alignment is fucked.
Re: (Score:2)
Ever hear of throttling?
Isn't that exactly what this is?
Re: (Score:2)
Throttling and Abuse has to be a paramount concern in public APIs, it needs to be mitigated and thought out from the beginning. Shit I see it enough in enterprise APIs and it's much worse.
Break up Twitter (Score:2)
They have got to be broken up along with Google and Facebook.
No, dummy. (Score:1)
[Twitter has] got to be broken up along with Google and Facebook.
I would be OK with breaking up Alphabet (since they are so diverse) but don't break up Facebook/Twitter. Instead, force their sites to support a cross-site API that allows people to migrate away while still being able to interface with people on Facebook/Twitter. It's a proven tactic that worked quite well with AOL Instant Messenger.
The fact that you want the FTC to bust up social media platforms but don't seem to give a rat's ass about banks is very telling. You only really seem to care about being able
Let me fix that headline for ya... (Score:2)
Re: (Score:2)
2. TechCrunch added the part about Cambridge Analytica - Twitter mainly said they want more money and they don't want other companies making money off their data without paying for it
So not fixing Nazis or adding Edit (Score:2)
Riight ...
Re: (Score:1)