Well, it’s come to this. Twitter is burning, a billionaire owes money, an API will soon get lobotomized, so Bridgy‘s Twitter support will die within the month is dead. Granary‘s and twitter-atom too. The Twitter API may now be effectively unmaintained, but they still managed to find an engineer somewhere to change a few numbers in the billing code and update some text on a web page.
What a waste. Plenty of ink has been spilled on all this already, I won’t belabor the point, but what an utter waste.
Right now, Bridgy uses a free tier of Twitter’s API, equivalent to what many other major social networks offer. By April 29th, this free tier will disappear. My options will be a $100/mo plan with a quota of 10k tweets/mo, roughly .1% of what Bridgy currently uses, or an enterprise plan with unknown quota that reportedly starts at $42k/mo.
Neither of these options is feasible. Bridgy can’t function with .1% of its current usage, and I won’t pay Twitter $500k/yr for a little side project.
The silver lining is, after all the chaos and destruction and flight to the fediverse, Twitter doesn’t feel nearly as important now as it did half a year ago. It’s always been Bridgy’s biggest user base, it had a great 11-year run, I never quite expected it to end like this, but here we are.
To everyone who used it, thank you for your interest and support over the years! It’s been a great ride. And who knows, Elon’s Twitter 2.0 is awful at comms and changes its plans all the time, so there’s a chance they’ll take this all back tomorrow. But assuming it sticks, Bridgy Twitter will stop working on April 29, if not before. I plan to leave it up and running until then. got unceremoniously suspended on April 4th. So much for the month’s notice.
A billionaire owes money, Twitter is burning, and the future is the IndieWeb and the fediverse. Try out Mastodon with Bridgy, classic or Fed, and join us there!
Thanks for all your work and support on this. Oh, and the Jetpack/Twitter connection seems to be broken already. What a farce….
@snarfed.org Thanks for keeping it going as long as you did. Was a brilliant service.
Without brid.gy, I would never had my blog / twitter POSSE setup working. From time to time I did a quick check to see if the brid.gy / twitter API thing still works after their announcement and following rescheduling of the free API’s end, and to my surprise I found brid.gy humming along nicely.
I, too, have moved my ‘social’ networking to Mastodon, and now with Matthias @pfefferle on board at Automattic, I’m optimistic that WordPress, Activitypub and the fediverse will move closer together.
But the quick exchanges, the reactions and ‘reach’ among my bubble in pre-Musk Twitter, I will miss this. Most of my timeline has moved over to Mastodon, but it is a different kind of interaction there, and I kind of miss the quick silliness that was part of ‘my’ Twitter experience. And brid.gy enabled me to have the best of both worlds, publishing from my blog into Twitter if and when I want to, but, more important for me, pulling back responses on Twitter as reactions under my blog posts here.
Well yes, thanks for all the fish, and again a huge thank you Ryan for all the work with brid.gy.
Wow. This post from 2018 anticipated the inherent problems of the POSSE indieweb principle of using your own site as the hub syndicating content into the “silo” networks, and the reliance of those silos’ APIs.
>
In reply to So long, Twitter API, and thanks for all the fish by Ryan Barrett.
Well, it’s come to this. Twitter is burning, a billionaire owes money, an API will soon get lobotomized, so Bridgy‘s Twitter support will die within the month.
A lot of the reactions on my blog come from Twitter thanks to Bridgy. A marvellous service. I really disliked it when Twitter swallowed comments, then Bridgy came to the rescue. Thanks so much for all of Bridgy.
In reply to So long, Twitter API, and thanks for all the fish by Ryan Barrett.
Well, it’s come to this. Twitter is burning, a billionaire owes money, an API will soon get lobotomized, so Bridgy‘s Twitter support will die within the month.
A lot of the… wp.me/p57zFQ-4CZ
04.04.2023 AI Powered Journal Maurice Renck Brid.gy Twitter Support It was foreseeable that it would happen: Brid.gy is discontinuing its Twitter support at the end…
04.04.2023 Open Web Maurice Renck Brid.gy Twitter Support Eigentlich war absehbar, dass es kommen wird: Brid.gy stellt seinen Twitter-Support Ende April ein. Brid.gy ist ein…
@snarfed.org Thank you, Ryan :)
@snarfed.org Thanks for your service o7. Sad to see but I’d do the same. Oh wait. I did the same. Pulling the plug on Twitter I mean 😩
@snarfed.org hey Ryan! Glad I follow so many indieweb people here because you just got boosted into my timeline. Thanks for continuing to run bridgy!
Looks like I timed this post just right. Got this email just now:
So much for April 29th.
Very crazy and sad 😥
I hope there will be some way…. for twitter and bridgy, going forward 🤷🏻♂️
Thanks Ryan for all you have done ! 🙏🏻
Thanks for supporting Brid.gy all these years! Twitter has ceased to be a platform I really interact with. It had a good run… Here’s to a federated future!
Twitter is evidently bending under the weight of all the complaints. They just announced a new Pro API tier: read 1M tweets, post 300k tweets, includes search and filtered stream, for $5k/mo. $60k/yr! Thanks but no thanks.
💩
Meanwhile, all of the legacy free API apps that weren’t suspended are still happily up and running on the old 1.1 API. A month later and they still haven’t turned it off yet.
I guess you may need this https://twitter.utools.me/
https://t.me/Yang0619