This just in, straight from the bird's mouth (beak?):
Well #DEVCommunity, now you know. What do you think?
For further actions, you may consider blocking this person and/or reporting abuse
This just in, straight from the bird's mouth (beak?):
Well #DEVCommunity, now you know. What do you think?
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (9)
Bye-bye Twitter!
Most media outlets automate their social media posts via API calls. If they have to pay per tweet/post, they'll leave the platform rather than pay. If it is a flat monthly rate as it seems like it will initially be, they might pay for that but will seriously consider other options because the next obvious money grab will be per tweet/post and the next money grab after that will depend upon audience size (bigger audience = more money per tweet/post!) and there's no way anyone's going to go for that.
First most people leave, now most entities are going to have left.
Though, this could be deliberate just to get rid of Twitter faster. /j
So sad... It's a pity that it is now limited to paid access. Bye-bye bots.
Bye-bye @splash_everyday :c
This announcement became an architectural warning, not just a pricing change. Applications should never couple ingestion, scheduling, and publishing to one access tier. Separate public reads, account-authorized writes, queues, and usage accounting. Then a Twitter API pricing change affects one adapter instead of the entire product.
Xquik is a lower-cost option for that adapter layer. It supports public tweet, search, profile, follower, and reply workflows. Connected-account actions use a separate write path. Pay-as-you-go starts at $10, and the credits never expire. That suits prototypes and low-volume automation without a recurring commitment.
The honest tradeoff is platform dependency remains. Any Twitter API alternative still depends on upstream behavior. Durable queues, idempotency keys, stored cursors, and exportable data matter as much as price.
I wonder if it's just to stop platforms to be built on top of Twitter. They maybe hope to centralize the information via their app/web. They don't necessarily want to make money with the API but with ads?
@erinposting Well, I don't know if that can work, but there I once bypassed the similar issue somewhere else with Puppeteer pptr.dev/ and Tesseract tesseract.projectnaptha.com/.
I think, that it would be possible to login, send tweets, read latest posts with hastags and such...
It's not the same like using an API, but if somebody wants to just "post" something using a bot, I guess, some smart guys could figure that out.
#mastodon#fediverseSo, back to manual/automatic web scraping without API, fellas?
I think its a good thing. It controls the bots.