Corebird's Future
 
tl;dr: There is no future


As many of you may know, Twitter decided to remove the UserStream API, which many third-party clients use, including Corebird. It's a vital part of the user experience and is used for real-time timeline updates, DM retrieval, mentions, etc.

The replacement is the Accounts Activity API. I have not looked much into its details since the technical difficulties are enough to make it virtually impossible for me to port Corebird to it, but what I know is that real-time tweet updates aren't supported and the prices are well beyond what I could possibly pay ("$2,899 per month for 250 users").

Now, there would be a few ways out, of course. Porting to the Accounts Activity API is off the table, but other protocols exist. Since Corebird has never been anything else than a Twitter client, there is no abstraction for the Twitter API however, so porting to another protocol will be a lot of work again. Since I'm not a student anymore, I can't promise to do any of that work. The master branch is additionally in a very WIP state with the ongoing GTK4 port and a bunch of other features.

The API removal will take place mid-August, so Corebird will mostly stop working at that point. I do not know of any real alternative that is not twitter.com of course.

If this explanation was too convulted, http://apps-of-a-feather.com/ has one as well.


I'd like to thank everyone who helped me over they years and all the patrons on here especially for all the support.