8 ms·
New developer requirements to protect our platform
- ttepasse 8y agoThe new default limits for each endpoint are outlined below and will apply in addition to existing user-level rate limits for these actions. By default, an app (across all of its users) will be limited to: - Tweets & Retweets (combined): 300 per 3 hours - Likes: 1000 per 24 hours - Follows: 1000 per 24 hours - Direct Messages: 15,000 per 24 hours They write that they can lift this requirements for certain apps. But any new 3rd party twitter client is pretty much toast.
- mrbill 8y agoThis is per-user, not per-entire-app-user-base, AFAIK
- jasonlotito 8y agoNo, this is per app.
- deleted 8y ago[deleted]
- urda 8y agoRTA, "By default, an app (across all of its users) will be limited to: - Tweets & Retweets (combined): 300 per 3 hours - Likes: 1000 per 24 hours - Follows: 1000 per 24 hours - Direct Messages: 15,000 per 24 hours"
- giarc 8y ago>But any new 3rd party twitter client is pretty much toast Unless they take the time to go through the review process and get a rate limit increase, in which case this theoretically should improve the app quality overtime as only those willing to put in the work will make it through.
- syrrim 8y agoWhat a joke. The only thing that will improve app quality is evolution by natural selection. Shitty apps bleed users and bleed cash. Increasing friction lowers the number of new entrants and raises the cost of iteration ie the two things that increase the speed of evolution. The only viable apps will be incumbents, who are incentivised to not change anything and increase monetization ie ads and tracking.
- chipotle_coyote 8y agoAny old third-party Twitter client is pretty much toast unless Twitter deigns to lift the requirements for them. I'm not entirely sanguine they will.
- sctb 8y agoWe've updated the submitted title from ‘Twitter introduces new developer requirements “to protect our platform”’. Submitters, please leave out the editorial.
- ColinWright 8y agoI'm the submitter: This wasn't intended to be an editorial, it was intended to provide context. I believe that it's not clear from the title alone as you've included it here that it was Twitter. Yes, it's on the twitter blog platform, but so are many other things that aren't actually from twitter. Personally, I spent some time trying to make sure the submitted title was more accurate and informative than the one on the post. I freely acknowledge that it's your call. I think you got this wrong.
- brlewis 8y agoThe "please leave out the editorial" part makes me think it was the scare quotes, not the word Twitter, that led to the title edit.
- ColinWright 8y agoThey weren't "scare quotes" - that was the part that was directly quoted, the other was to provide the context for the exact quotation. Perhaps I should've put: Twitter introduces “new developer requirements to protect our platform” To be honest, I do what I think is right, and I don't care to second-guess the mods. But I'm slowly being trained not to care at all.
- sctb 8y agoAccording to https://news.ycombinator.com/from?site=blog.twitter.com https://news.ycombinator.com/from?site=blog.twitter.com it's the Twitter blog site, is it not? The quotation marks seemed to convey something else, whether you intended them to or not. But since the original title was neither misleading nor click-bait it's besides the point. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- css 8y agoInstagram did this a long time ago with their API - they require you pass a Permissions Review [0] where you submit your featureset along with a website landing page (ex. for a product offering) for review by a human who then can accept or deny your application. [0] https://www.instagram.com/developer/review/ https://www.instagram.com/developer/review/
- nkozyra 8y agoThis is also the approach Facebook has taken in the wake of the Cambridge Analytica debacle. Everything has shifted back to the walled garden approach. Twitter had destroyed a wide ecosystem of applications that promoted their brand several years ago via a similar approach. FB has done (and may be again doing) the same. The message remains clear: don't build your business on another business without contracts and guarantees. When the utility of having you as a promotional instrument wears off, they will dump you.
- css 8y ago> don't build your business on another business without contracts and guarantees Or even with them: https://techcrunch.com/2018/06/21/twitter-smytes-customers/ https://techcrunch.com/2018/06/21/twitter-smytes-customers/
- meesterdude 8y agoThat's... amazing. These two tweets really show just how WTF this was > A vendor notified us of their acquisition at 6am this morning and shut down their APIs 30 minutes later, creating a production outage for npm (package publishes and user registrations). The sheer unprofessionalism of this is blowing my mind. > It takes weeks to negotiate and sign an acquisition. You didn't find out at 6am. You couldn't give us a week? Even a couple of hours to take your service out of our critical path and avoid an outage? Fucking shocking behavior.
- thoughtpalette 8y agoThe number one reason I stopped developing an Application based on IGs API. The hoops you have to jump through was insane. Full paragraph explanation for each permission you're requesting. (meh) Video of the app working. Only can use personal account for testing/polling API.
- detaro 8y agoThat sounds like the end of a lot of API use for small players... Review is noticeable hurdle for small/private projects, and at the same time services serving many small users will easily have trouble with the rate limits, unless they make it easy to get those raised (which is possible, but I'd be skeptical).
- kevin_b_er 8y agoThe translation of this is: We're trying even harder to kill any and all 3rd party applications. 300 tweets per 3 hours global rate limit is bonkers. My favorite twitter app for android is probably dead after this.
- toomuchtodo 8y agoOn the plus side, signal to noise is about to skyrocket on Twitter.
- urda 8y agoExtremely doubtful in reality though, it's still going to be all noise.
- mevile 8y agoIt's always been about how you follow people. I have a few twitter accounts: one where I follow people I know and devs and it's very noisy. It's nearly unusable, it's full of political rants, even from well known devs, angry tweets, just not very useful. I don't read it much. The other twitter account I follow people who write funny tweets, and that account is a goldmine. I love it. I like almost every tweet. Nobody follows this account, it's just like a read only twitter and it's amazing. I have a third twitter account for local news, I follow the local fire department, police, local news, local businesses, and it's also super great. Twitter's android app makes it easy to switch between accounts, it's basically just like different feeds.
- strken 8y agoHow long before we go back to dodgy apps that just ask for the user's email and password, if regular API access is so heavily restricted? I know there's an npm package out there for my bank that runs a headless browser and requires full credentials, which is terrifying.
- jonny_eh 8y agoIs there anything stopping dodgy apps from doing that now?
- Angostura 8y agoNo, but users tend to think twice and avoid them if there is a less dodgy alternative
- richdougherty 8y agoIt's more costly so it probably changes the economics of spam.
- moonka 8y agoI've noticed both on Coinbase and Ally recently that connecting other accounts for transfer lets you do it instantly in a little popup window that asks for credentials for other banks. Seems like a big step backwards in training users.
- radicaldreamer 8y agoThis is because the vast majority of banks don’t have APIs and Plaid is the service which builds these connectors.
- kalleboo 8y agoAt least the EU is trying to fix this https://www.cnbc.com/2017/12/25/psd2-europes-banks-brace-for-new-eu-data-sharing-rules.html https://www.cnbc.com/2017/12/25/psd2-europes-banks-brace-for...
- Macha 8y agoA common workaround after Twitter attempted to kill third party client apps was to have users register their own "app" and insert the API keys. So this will put a stop to that.
- pnevares 8y agoI don't think I understand how the rules will affect that, won't the 300 per 3 hours limit on tweets still only affect the "app" a user generated their keys for?
- Macha 8y agoBecause $JOE_AVERAGE_USER is not going to convince Twitter's account approval team that they are a legitimate developer (because they're not).
- notatoad 8y agoThese new limits seem specifically designed to continue allowing that workaround. 300 tweets per three hours is about the upper limit of what a single user would do, so if you're registering a developer account just for personal use you can do that without any manual review or having to demonstrate having a real product. You only require approval from twitter and a product website if you have higher usage than that, which is what would prevent you from using that workaround.
- pnevares 8y agoI think I see what the OP meant, here are relevant excerpts from the article. New API access: > Beginning today, anyone who wants access to Twitter’s APIs should apply for a developer account using the new developer portal at developer.twitter.com. Existing API keyholders: > Eventually, all developers with existing access to our APIs will be required to complete a developer account application in order to maintain their apps.
- notatoad 8y ago
- jhabdas 8y agoNo more free $ETH giveaways. Just darker, more deceptive black hats.
- AznHisoka 8y agoHow would this impact a service like Buffer? Limiting posting 300 tweets per 3 hours certainly wouldn't be feasible, given the number of customers they have...
- beberlei 8y agoThe post mentions heavy API users will get exceptions based on their use-case.
- detaro 8y agoThe existing large players probably already have their exceptions worked out, or will very soon. Want to join that space? Gotta be lucky with review/limit raise request I guess. It's possible they just want services to start small and act legitimate to raise the bar for "bad apples" and will raise the limits easily afterwards, we'll have to see.
- taytus 8y agoMeantime: https://www.dropbox.com/s/hb7c0l54r8m0zoy/Screenshot%202018-07-24%2015.34.08.png?dl=0 https://www.dropbox.com/s/hb7c0l54r8m0zoy/Screenshot%202018-... I know that fixing/changing/upgrading things at scale is much harder that what most people think, but man... they have done nothing to fix these type of issues, and don't tell me is not something easy to fix. The other day a journo complained on twitter about the problem of dealing with crappy messages: https://twitter.com/sarahfrier/status/1020512187322789888 https://twitter.com/sarahfrier/status/1020512187322789888 So in less than an hour, I had a prototype to help to filter those type of messages: https://www.dropbox.com/s/z914olzgn68v660/Screenshot%202018-07-21%2008.57.01%20%281%29.png?dl=0 https://www.dropbox.com/s/z914olzgn68v660/Screenshot%202018-... If a random dev can do this, why they can't fix it? I like twitter, and I'm genuinely curious why some of these seemingly easy to fix problems are not taken care.
- acover 8y agoIsn't the issue with spam prevention is they adapt to your changes?
- pnevares 8y agoWhat are we supposed to be seeing in your second screenshot? I just see an array of DMs, what's being filtered?
- taytus 8y agoYeah, sorry. You are right is not showing anything else besides the API result. But is trivial to return a secondary, already parsed array. I haven't used the API in a while and was just seeing if I could achieve that.
- brailsafe 8y agoI could redesign my bank's website in a week if I didn't have to deal with their codebase, build processes, technical debt, internal politics, or the real world complexity of building a production ready website at their scale ;)
- saurik 8y agoAs someone who is apparently "old", I continue to not understand how Twitter has managed to trick an entire generation of developers into believing they need Twitter's permission to develop a third-party Twitter client. Has the law changed in some noticeable way to make reverse engineering the official Twitter client and extracting their first party keys for purposes of interoperability suddenly illegal? We used to do this all the time, at scale before Twitter's invention of the "API key", and the only recourse the service has is to try to detect weird usages of their backend and then punish the users... something that tends to be something of a PR nightmare. (FWIW, I am totally willing to believe the issue is that Apple won't accept them, but then that is Apple being the asshole, and we should be looking into ways of making that market collusion illegal, assuming of course that it isn't already.)
- dmitrygr 8y agoThey could claim copyright over the API key (unlikely) or (more likely) ask a friendly prosecutor to charge you with violating CFAA. You are accessing their systems, not in a way they authorized. Enjoy some jail time. Sadly, yes, it has come to this. Eg: https://www.newsweek.com/most-hated-law-internet-and-its-many-problems-cfaa-448567 https://www.newsweek.com/most-hated-law-internet-and-its-man...
- tptacek 8y agoThey don't need a prosecutor; CFAA includes civil causes of action.
- saurik 8y agoThe CFAA has existed since the 80s, and yet I have not heard of it being used successfully to stop all of the work we did in the 90s on third-party clients. Meanwhile, all of the recent stuff I have heard about the CFAA has been that precedent is being set that its super vague provisions can't be used to enforce a mere terms of service. https://www.eff.org/deeplinks/2018/01/ninth-circuit-doubles-down-violating-websites-terms-service-not-crime https://www.eff.org/deeplinks/2018/01/ninth-circuit-doubles-...
- dmitrygr 8y agoGiven how many times twitter has screwed developers attempting to build things on top of their API, does anyone still care? Does anyone still think developing on twitter's API is a good idea?
- hivacruz 8y agoWell, I guess my movie quiz bot (@whattheshot) which turns 8 in a few hours, is almost coming to an end then. I had to adjust so many things the last few years that the game lost completely interest to most of my players. I was shadow-banned anyway. My last hope is that the "review process" they talked about could really differentiate bad apps/bots and interesting bots and let them work. But I honestly doubt it will happen.
- tonystubblebine 8y agoI know a lot of the conversation about the API separates out good guys and bad guys, i.e. spammers. But I'm more and more thinking that Twitter and other platforms should consider marketing automation to be a form of spam. Once you start questioning that there isn't a human behind the human account you give up on human interaction. So yeah, maybe there's some vanity metric that marketing automation props up for companies like Twitter. But underneath that vanity metric, the real quality of the site is being diminished.
- adamw2k 8y agoThinking through this a bit... So the end result of this move is less SPAM and higher quality content. Great! But if SPAM is a form of activity (albeit a less desirable one) and activity represents feed liquidity - which directly impacts revenue - how does this not significantly hurt the bottom line? Time to short TWTR in Q4ish.
- skybrian 8y agoThis is basically "know your customer" for an API. It's episode N in "why the Internet can't have nice things." If you make a technology available at scale, it will be abused. Compare with email spam countermeasures making it more difficult to set up a email server that other email providers will accept mail from. Or malware resulting in the rise of app signing and app stores.