Perhaps it’s because the app didn’t appear to have any new features – in fact, it’s technically got less than 5, though those that have been removed – user-specified URL shortening, image hosting, and video hosting services – haven’t worked in a good while anyway. I can’t remember exactly why – though I suspect I was just fucking around on my phone before bed, bleary-eyed – but the implications of this next numeral passed me by the first time I saw and downloaded Tweetbot 6, two weeks ago. Notably, Tweetbot developer company Tapbots was apparently required to take down Tweetbot 5’s store listing 30 days before releasing Tweetbot 6. This is an unusual practice – usually, pre-release versions of iOS apps can only be distributed through Apple’s developer beta testing infrastructure, though Testflight. At this moment, it is listed on the App Store as an “Early Release” version, though its predecessor can still be downloaded by those who’ve already purchased it in the past, like me. In the name of progress, I’ve done my best to make a point of looking back, too, yet something astonishingly personally relevant managed to slip past me until just last week: there is a sixth version of the Tweetbot app.
825 days ago, I told you lots about the history surrounding the development of Tweetbot 5, which I confidently described as “likely the last competitive third-party Twitter app for iOS.” After spending the past few months diving deep into iOS in preparation to review and reflect upon Apple’s current flagship handset, my eyes have been opened to the exponentially-increasing pace of the whole environment’s metamorphosis during the course of my lapsed attention. Were it just I who came to you with only my voice on this cold night, proclaiming the imminent release of a whole numerical version of a third-party mobile Twitter client in 2021, you really would have no choice but to send for the laws, for you’d be left no consideration other than my comprehensive descent into absolute insanity. Listen to this article read by Siri below.
With this new v2 version we can get all that data in a single step.In the bleak face of Twitter’s centralization, Tapbots refuses to give up on its mobile client. “We currently use the v1.1 home timeline API to get a list of Tweets and then v2 APIs to fill in any v2 specific data (polls, cards, metrics, etc). “We’ll simply be able to refresh the timeline more often and allow users to scroll much further back in their timeline.” From a development standpoint, he says, it makes things much simpler. In an email to The Verge, Haddad explained that the change will make Tweetbot more responsive to users. One of Tweetbot’s developers, Paul Haddad, quoted in a Twitter announcement that the old way to get a user’s timeline is “one of our most commonly used API calls.” The older version of the API was introduced in 2012, where developers who used it were facing limits when trying to get a user’s timeline. This feature is a very welcome one for third-party clients like Tweetbot.
0 kommentar(er)
