TweetDeck Preview doesn't (won't?) have it, and there's no good way to replicate this feature with Twitter's API. This is something I could do, but no plans yet. Clients like Spring and TweetBot have made it work by polling metrics, and tweets are a regular interval and dispatching notifications accordingly. NotificationsĪs of now, there are no real ways to get notifications about likes/retweets/tweets in the Twitter API.
Reserving this post for future addendums: Addendum about API limitations and how Skyla could/might work around them. That's not even an exaggeration, and I have been told it's by design to avoid running into a situation where TweetDeck has to wait months before it gets a new Twitter Web feature ↩ My gut feeling says it'll be sometime around early next year but don't quote me on that as I'm (obviously) not a Twitter employee! ↩ When this rollout exactly happens hasn't been communicated. Thanks for reading, and thanks for the support for all those years! Footnotes I definitely couldn't imagine it being so big when I started working on it as a student in 2014, and it's been a wild ride ♥️ Conclusionįirst of all, I want to thank everybody who used BTD, spread the word about it, or contributed to it in any shape or form. Notably, the "biggest" change that's on the way is updating the tooling of BTD to support Manifest V3 because Google will require it for any updates to existing extensions, so I can't escape it. Any changes I do/accept to the codebase will be bug fixes when I can gather the motivation to do so. What now? For Better TweetDeckįirst and foremost, as of writing this, I'm considering Better TweetDeck to be in a feature freeze state. As much as BTD has been fun as a project, it involved a lot of stress because overnight, Twitter could (and did!) break BTD without any warnings, and it doesn't sound like TweetDeck Preview would be less of a moving target.Īdd to this the annoyances/support issues that come with working on a browser extension for all the major browsers, and honestly? I think I want to chill for a bit. I have been working on Better TweetDeck for more than 8 years at this point, so the thought of having to throw out all the shared knowledge of the internals of TweetDeck to start over is, at best, annoying and, at worst, kind of depressing.Īfter thinking about it for a long time, I've concluded that I do not want to start over on even less stable grounds. However, some of the issues I have with TweetDeck Preview aren't technical.
#Better tweetdeck gif button mod#
All of this means that any UI or CSS mod is hard to make and maintain.
#Better tweetdeck gif button code#
The new TweetDeck is the Twitter Web App + some code to handle multiple feeds/columns 2.Ī year ago I had said I'd poke around and see what I could do, and around the beginning of this year, I started digging more seriously into how I could feasibly rewrite BTD for it. It completely breaks BTD due to how it's built.It brings feature parity with Twitter Web, which is a great thing because I had to do a lot of that with BTD.Here's how it will affect Better TweetDeck: How you feel about it isn't relevant since it will be rolled out generally at some point anyway 1. I'm opening another issue to replace #653 because quite a lot has changed since I commented there, and I figured it would act as a better redirect point for future questions/discussions about this topic.Īs you may know, Twitter has started rolling out a new version of TweetDeck. If you want to find me, I'll still be on Twitter but I'm also (more) active on Mastodon and Cohost these days. EDIT: As of February 2023, it is clear Twitter's new management doesn't give a shit about 3rd party developers so I am NOT going to invest any energy about building on top of Twitter's platform anymore.
0 kommentar(er)
