Twitter already betrayed their entire dev base all those years ago when they effectively killed off all 3rd party clients by setting a lifetime cap on oauth tokens per developer just so they could force users to use their clients which inject ppa/ppc ads into the stream (and then didn’t even bother keeping those clients up to date, pissing both the developers and their users off in one go). Stupidest move ever on their end. All they’d have had to do is mandate the inclusion of promoted tweets in the firehouse and they’d have kept developers loyal to their platform while raking in the cash.
A few years ago, the free search API could retrieve tweets since the beginning of twitter (although twitter did not guarantee completeness of the results): https://web.archive.org/web/20150311065138/https://dev.twitt...
Twitter then limited this API endpoint to data from the past seven days only, and now just introduces a paid version for only last 30 days data.
I find it fair to charge for elevated API access. On the other hand, the 30 days limit for the paid version is pretty ridiculous. Makes it more worth to just scrape the free online advanced search...
> I wish these premium APIs were available during our first few years. As we grew, we quickly ran into data limitations that prevented expansion. Ultimately, we raised a round of funding in order to accelerate our growth with the enterprise APIs. With the premium APIs, we could have bootstrapped our business longer and scaled more efficiently.
Quoting a company that is essentially saying they had to seek funding because of twitter limiting API access is an odd choice for this announcement.
I wish it were true pay-as-you-go rather than starting you in a sandbox and then jumping immediately to $150. Working on a small side project, $150/mo is a lot of money in the beginning, especially if I'm doing a relatively small number of requests. I guess I need to see what the sandbox entails, but if it's not real live twitter data, this still feels like a big step function in cost from free to premium. Just charge me per-API call or on the amount of data transferred with no minimum.
I don't know that the testimonial in the post makes me feel better about the product to be honest "they couldn't provide us what we needed so we had to give away part of our company to pay through the nose for the privilege for that feature, so it's great they've released this now, years after it'd have been useful. How's that feature you're waiting on working out for ya?".
I know it's the current thing to bash on Twitter, and I'm sure there are decent use cases out there, and glad they're finding extra revenue streams outside of ads, but the speed and level of iteration seems rather low considering the resources they have.
Of course, I'm just a username on a website and have never scaled anything to 300m users, but like a lot of people, think Twitter could still be great... but seemingly still has a lot of miles to go. And highlighting that in an announcement post seems... strange
Twitter's biggest mistake was hiring thousands of people when they only needed 30. It doesn't need thousands of people. It doesn't even need 100.
Twitter is not a technological marvel. It's something Oprah promoted, and Donald Trump bitches on.
And now, it's an API with a (social) class-based access, and without irony, also promotes itself as a leader in conversation and exchange.
I always find it humorous that Twitter was the creator of the HTTP response code:
Returned when an application is being rate limited for making too many requests.
420: Enhance Your Calm
As the pricing appears to be based on # of requests and/or # of tweets consumed, does it have a `include_spambots=false` filter or do we have to pay for the pleasure of wading through spam?
Is there an available history of Twitter's APIs over the years? IIRC it was initially open, and then they locked it down so many 3rd party apps for Twitter had to shut down, and now they're sort of opening it up again?
What's the deal?
My experience with Twitter API has been horrible to say the least. Plenty of API errors, service over capacity, and instability. So now I have to pay to get access to an API that's stable?
Step 1 - build a product. make sure it has lots of bugs and is unstable.
Step 2 - roll out a premium product that's the same product, just stable, and less buggy.
How is charging for an API not a finger to the developer community? Facebook for example doesn't charge for their API access. They charge for the products that the API has access to. If I have access to a product, I shouldn't need to be charged for the APIs to access that product
Absolutely not. Never again will I trust Twitter as a developer.
Good for them, I honestly hope it works business-wise as they want and it makes developers satisfied. However, I'm afraid Twitter the company has got the same sort of trust issues as Google from the developers POV. They need to address this specifically, if they want people to believe their premium API move is for real.
This is a good start. Gnip seems to basically be invite only (I've tried contacted them multiple times and have not once received a response) and the public API is so limited it's near useless.
I'd still rather everyone move to Mastodon.
I immediately checked the date on the article after reading the headline.
Thought it was a relic from the third party client days.
Is everything starting around $149+, or only search?
I suppose that's understandable, but I think it would be cool if they implemented something more akin to the AWS pricing model (S3, for example, as tweet streams remind me more of this than of enterprise-level pricing).
Twitter's current plan is to execute on all the ideas their user base was talking about 5+ years ago.
I'm still waiting for that webhook API they talked about 2 years ago.
Until info about the new endpoints and queries is released, I'm not rushing to get out my wallet, but at the very least it's encouraging to see any movement regarding the API. This seems like a vote of confidence that the basic API will be around for at least a few more years.
> However, this left a gap that made it painful for growing businesses to deliver scalable solutions to customers
How about this: close your monetization gap yourself instead of pushing the problem downstream?
I wonder how many people "we came up with a new way to sell your data!" will send away from Twitter.
Anyone knows how much they charge for the gnip enterprise access.
Is there a way to get copy of twitter entire dataset?
I have a feeling in my gut that it's too late.
Why is Twitter API so open ? I have been playing with it for a few weeks and I can find almost every data I want. How does it benefit them ?
twitter is out of ideas.