The latter is an especially important feature: it’s long been exclusive to Twitter’s official app, so if you wanted to tweet something that only people you mention or people you follow could reply to, you simply couldn’t use Tweetbot. You can now control who can reply to your tweets in Tweetbot. Take this week’s 6.6 update, for instance: thanks to the new Twitter API, Tweetbot now supports creating polls (but not voting on them, due to API limitations) as well as controlling who can reply to your tweets. There are still several Twitter features that Tweetbot can’t access, but, for my needs, what Tweetbot 6 offers now is enough to not make me miss the official Twitter app anymore. The switch to subscription, however, has allowed Tapbots to continuously iterate on the app over the past few months, which, coupled with Twitter’s v2 API, has resulted in the most integrated, capable version of Tweetbot yet. When Tweetbot 6 came out earlier this year with support for the new Twitter API and a subscription-based business model, I thought the new version was fairly underwhelming because it looked mostly the same as the old one. I had stopped using Tapbots’ app a few years ago when it couldn’t receive new features due to limitations of the old Twitter API, but things are different now with Twitter’s new API, which officially launched for all developers yesterday. The experiment has been successful, but, curiously enough, it also made me appreciate the design and power-user features of Tweetbot all over again. This started off as an experiment to see whether switching to a third-party client with timeline sync would improve my daily use of Twitter, allowing me to miss fewer tweets and catch up on my timeline (I’ve always been a completionist) at my own pace.
Tweetbot 6.6 supports creating polls and limiting replies to your tweets.įor the past two months, I’ve been using Tweetbot as my primary Twitter client again.
0 kommentar(er)
