diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/David Blue on Social Media Software.md b/notes/Bear Notes/Tweetbot 6 for iOS Review/David Blue on Social Media Software.md new file mode 100644 index 00000000..55beb9c2 --- /dev/null +++ b/notes/Bear Notes/Tweetbot 6 for iOS Review/David Blue on Social Media Software.md @@ -0,0 +1,8 @@ +# David Blue on Social Media Software +1. [Eugen Rochko, Saint of Federated Social](https://bilge.world/eugen-rochko-interview) | April 17th, 2017 +2. [Twitter Thrives on Incompetence](https://bilge.world/twitter-lists) | May 29th, 2018 +3. [Tweetbot 5 for iOS Review](https://bilge.world/tweetbot-5-ios-review) | November 27th, 2018 +4. [Revelations in Web Starvation](https://bilge.world/bad-connection-insights) | October 14th, 2018 +5. 5. [Mastonaut for MacOS](https://bilge.world/mastonaut-for-macos) | May 30th, 2019 + +#software #tb6 \ No newline at end of file diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/Documentation _ Tweetbot 6 for iOS.md b/notes/Bear Notes/Tweetbot 6 for iOS Review/Documentation _ Tweetbot 6 for iOS.md new file mode 100644 index 00000000..0e66ac8f --- /dev/null +++ b/notes/Bear Notes/Tweetbot 6 for iOS Review/Documentation _ Tweetbot 6 for iOS.md @@ -0,0 +1,10 @@ +# Documentation | Tweetbot 6 for iOS +- [ ] [“Why can’t I see the link/media in some tweets?”](https://tapbots.com/support/tweetbot6/general/cantseelinks.php) | Tweetbot 6 for iOS Support + +- [ ] [Subscriptions Explained](https://tapbots.com/support/tweetbot6/general/sub.php) | Tweetbot 6 for iOS Support + +- [ ] [Introducing a new and improved Twitter API](https://blog.twitter.com/developer/en_us/topics/tools/2020/introducing_new_twitter_api.html) | Twitter Blog +[[Introducing a new and improved Twitter API | Twitter Blog]] +[Twitter API Public Roadmap](https://trello.com/b/myf7rKwV/twitter-developer-platform-roadmap) + +#documentation #ios #tb6 \ No newline at end of file diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/Introducing a new and improved Twitter API _ Twitter Blog.md b/notes/Bear Notes/Tweetbot 6 for iOS Review/Introducing a new and improved Twitter API _ Twitter Blog.md new file mode 100644 index 00000000..107ab198 --- /dev/null +++ b/notes/Bear Notes/Tweetbot 6 for iOS Review/Introducing a new and improved Twitter API _ Twitter Blog.md @@ -0,0 +1,78 @@ +# Introducing a new and improved Twitter API | Twitter Blog +Introducing a new and improved Twitter API.webarchive +![](Introducing%20a%20new%20and%20improved%20Twitter%20API%20%7C%20Twitter%20Blog/developer-blog-share.jpg.twimg.768.jpg) +*We planned to launch the new Twitter API on July 16, 2020. But given the [security incident](https://twitter.com/TwitterSupport/status/1283518038445223936?s=20)we discovered on July 15, 2020, the timing of our launch no longer made sense or felt right.* + +*We updated this post on August 12, 2020 to include additional details below to support the official launch of the new Twitter API.* + +This Tweet is unavailable + +- - - - + +This Tweet is unavailable + +Today, we’re introducing the new Twitter API. Rebuilt from the ground up to deliver new features faster, today’s release includes the first set of new endpoints and features we’re launching so developers can help the world connect to the public conversation happening on Twitter. +If you can’t wait to check it out, [visit the new developer portal](https://developer.twitter.com/en/portal/opt-in). If you can, then read on for more about what we’re building, what’s new about the Twitter API v2, what’s launching first, and what’s coming next. + +This Tweet is unavailable + +This Tweet is unavailable + +Your feedback has been essential in helping us define our vision and roadmap for the new Twitter API. From Tweets to focus groups, you have shared a ton of feedback with us over the past few years about what you need out of the Twitter API and what we can do better. We also [learned a lot](https://blog.twitter.com/developer/en_us/topics/tools/2020/a-year-with-twitter-developer-labs.html) through [Twitter Developer Labs](https://blog.twitter.com/developer/en_us/topics/tools/2019/building-the-next-generation-of-the-twitter-api.html) where you’ve been sharing real-time feedback on the new API features we’ve tested in the open. + +We’ve always known that our developer ecosystem is diverse, but our API has long taken a one-size-fits-all approach. Your feedback helped us see the importance of making the new Twitter API more flexible and scalable to fit your needs. With the new API, we are building new elevated access options and new product tracks, so more developers can find options to meet their needs. More on that below. +We also know it’s important to be able to plan ahead, and we want to do a better job of sharing our plans with you in advance. Going forward, we’ll share more of what’s coming next on our [public roadmap](https://trello.com/b/myf7rKwV/twitter-api-platform-roadmap) (updates coming soon). We're also sharing a [Guide to the future of the Twitter API](http://developer.twitter.com/en/products/twitter-api/early-access/guide) for more about what to expect as we roll out the new API. We have a lot planned, and it will evolve and improve as we continue to hear from you. + +This Tweet is unavailable + +This Tweet is unavailable + +**A new foundation** - The new API is built on a completely new foundation — [rebuilt for the first time since 2012](https://blog.twitter.com/engineering/en_us/topics/infrastructure/2020/rebuild_twitter_public_api_2020.html) — and includes new features so you can get more out of the public conversation. That new foundation allows us to add new functionality faster and better than we’ve done in the past, so expect more new features from Twitter to show up in the API. + +With this new foundation, developers can expect to see: + +* A cleaner API that's easier to use, with new developer features like the ability to specify which fields get returned, or retrieve more Tweets from a conversation within the same response +* Some of the most requested features that were missing from the API, including conversation threading, poll results in Tweets, pinned Tweets on profiles, spam filtering, and a more powerful stream filtering and search query language + +**New access levels** - With the new Twitter API, we’re building multiple [access levels](https://developer.twitter.com/en/products/twitter-api/early-access/guide#newways) to make it easier for developers to get started and to grow what they build. In the past, the Twitter API was separated into three different platforms and experiences: standard (free), premium (self-serve paid), and enterprise (custom paid). As a developer's needs expanded, it required tedious migration to each API. In the future, all developers — from academic researchers to makers to businesses — will have options to get elevated access and grow on the same API. + +This Tweet is unavailable + +![](Introducing%20a%20new%20and%20improved%20Twitter%20API%20%7C%20Twitter%20Blog/develooperblogimage1.png.img.fullhd.medium.png) + +**New product tracks** - We love the incredible diversity of developers who use our API. Our plan is to introduce new, distinct [product tracks](https://developer.twitter.com/en/products/twitter-api/early-access/guide#newways) to better serve different groups of developers and provide them with the right experience and support for their needs, along with a range of relevant access levels, and appropriate pricing (where applicable). To start, these product tracks will include: + +* **Standard**: Available first, this will be the default product track for most developers, including those just getting started, building something for fun, for a good cause, and to learn or teach. We plan to add Elevated access to this track in the future. +* **Academic** **Research**: [Academic researchers](https://developer.twitter.com/en/use-cases/academic-researchers) use the Twitter API to understand what’s happening in the public conversation. In the future, qualified academic researchers will have a way to get Elevated or Custom access to relevant endpoints. We’re also providing [tools and guides](https://developer.twitter.com/en/use-cases/academic-researchers/helpful-tools) to make it easier to conduct academic research with the Twitter API. +* **Business**: Developers build businesses on the Twitter API, including our [Twitter Official Partners](https://partners.twitter.com/en) and [enterprise data customers](https://data.twitter.com/en/customers/enterprise-data). We love that their products help other people and businesses better understand and engage with the conversation on Twitter. In the future, this track will include Elevated or Custom access to relevant endpoints. + +**A new developer portal** - To help you get the most out of the new API, we’ve also designed and built a new developer portal. This is where you can get started with our new onboarding wizard, manage Apps, understand your API usage and limits, access our new support center, find documentation, and more to come in the future. + +### With the new Twitter API, we hope to enable more: + +* Academic research that helps the world better understand our shared perspectives on important topics such as: people’s attitudes about [COVID-19](https://developer.twitter.com/en/case-studies/penn), the social impact of [floods and climate change](https://www.theverge.com/2020/2/10/21128744/twitter-data-floods-noaa-climate-change), or the prevalence of [hateful speech](https://hatelab.net/projects/) and how to address it. +* Tools that help make Twitter better for the people who use it, like: [BlockParty](https://www.blockpartyapp.com/), [TweetDelete](https://tweetdelete.net/), and [Tokimeki Unfollow](https://tokimeki-unfollow.glitch.me/). +* Bots that share information and make conversations more fun like the: [HAM: Drawings bot](https://twitter.com/ham_drawing), [House of Lords Hansard bot](https://twitter.com/HansardLord), and [Emoji Mashup bot](https://twitter.com/EmojiMashupBot). +* Businesses like [Black Swan](https://www.blackswan.com/), [Spiketrap](https://www.spiketrap.io/), and [Social Market Analytics](https://www.socialmarketanalytics.com) who serve innovative use cases such as social prediction of future product trends, AI-powered consumer insights and FinTech market intelligence. +* Twitter Official Partners such as [Brandwatch](https://partners.twitter.com/en/partners/brandwatch), [Sprinklr](https://partners.twitter.com/en/partners/sprinklr) and [Sprout Social](https://partners.twitter.com/en/partners/sprout-social) who help brands better understand and engage with their industry and customers. +* And much more, including new things we haven't thought of yet, but that we know you will... + +One of the most common reasons developers use the Twitter API is to listen to and analyze the conversation happening on Twitter. So, soon we’ll release Early Access to an [initial set of new endpoints](https://twittercommunity.com/t/announcing-early-access-to-the-next-generation-of-the-twitter-api/139612) for developers to: + +All API features we’re releasing first will be available in our new – always free – Basic access level. For most developers, Basic access will provide everything you need to get started and build something awesome. + +Eventually, the new API will fully replace the v1.1 standard, premium, and enterprise APIs. Before that can happen though, we have more to build, which is why we are referring to this phase as [Early Access](https://developer.twitter.com/en/products/twitter-api/early-access/guide#rollingout). It's a chance to get started now and get ahead. + +Unlike Twitter Developer Labs which hosts our experiments, everything in the first release will be fully supported and ready for you to use in production. To see the full list of API functionality and endpoints that are included in today’s release, check out our [developer forum post](https://twittercommunity.com/t/announcing-early-access-to-the-next-generation-of-the-twitter-api/139612). + +You can get started on the new API by creating a new Project and App today in the new developer portal. You can also connect your new Project to existing Apps, if you would like. + +To get started with Early Access to the new Twitter API, [visit the new developer portal](https://developer.twitter.com/en/portal/opt-in). If you don’t yet have a developer account, [apply](https://developer.twitter.com/en/apply-for-access) to get started. + +This is just the beginning. We’re [sharing our public roadmap](https://trello.com/b/myf7rKwV/twitter-api-platform-roadmap) to keep you updated on our vision for the API, along with options to share feedback so that we can continue to learn from you along the way and so you can plan for what’s to come. On deck: full support to hide (and unhide) replies, and free Elevated access for academic researchers. + +Developers like you push us and inspire us every day. Your creativity and work with our API make Twitter better for people & businesses, and make the world a better place. Thanks for your partnership on the journey ahead. + +[Introducing a new and improved Twitter API](https://blog.twitter.com/developer/en_us/topics/tools/2020/introducing_new_twitter_api.html) + +#archive #tb6 \ No newline at end of file diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/Introducing a new and improved Twitter API _ Twitter Blog/Introducing a new and improved Twitter API.webarchive b/notes/Bear Notes/Tweetbot 6 for iOS Review/Introducing a new and improved Twitter API _ Twitter Blog/Introducing a new and improved Twitter API.webarchive new file mode 100644 index 00000000..a78ca78f Binary files /dev/null and b/notes/Bear Notes/Tweetbot 6 for iOS Review/Introducing a new and improved Twitter API _ Twitter Blog/Introducing a new and improved Twitter API.webarchive differ diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/Introducing a new and improved Twitter API _ Twitter Blog/develooperblogimage1.png.img.fullhd.medium.png b/notes/Bear Notes/Tweetbot 6 for iOS Review/Introducing a new and improved Twitter API _ Twitter Blog/develooperblogimage1.png.img.fullhd.medium.png new file mode 100644 index 00000000..e167b957 Binary files /dev/null and b/notes/Bear Notes/Tweetbot 6 for iOS Review/Introducing a new and improved Twitter API _ Twitter Blog/develooperblogimage1.png.img.fullhd.medium.png differ diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/Introducing a new and improved Twitter API _ Twitter Blog/developer-blog-share.jpg.twimg.768.jpg b/notes/Bear Notes/Tweetbot 6 for iOS Review/Introducing a new and improved Twitter API _ Twitter Blog/developer-blog-share.jpg.twimg.768.jpg new file mode 100644 index 00000000..11297f8d Binary files /dev/null and b/notes/Bear Notes/Tweetbot 6 for iOS Review/Introducing a new and improved Twitter API _ Twitter Blog/developer-blog-share.jpg.twimg.768.jpg differ diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/Tech Media on Tweetbot 6.md b/notes/Bear Notes/Tweetbot 6 for iOS Review/Tech Media on Tweetbot 6.md new file mode 100644 index 00000000..407c1b53 --- /dev/null +++ b/notes/Bear Notes/Tweetbot 6 for iOS Review/Tech Media on Tweetbot 6.md @@ -0,0 +1,42 @@ +# Tech Media on Tweetbot 6 +- [ ] [Tweetbot 6 released with support for new Twitter API, now a subscription|based app | 9to5Mac](https://9to5mac.com/2021/01/26/tweetbot|6|new|features|subscription|model/) + +- [ ] [Tweetbot 6 is an update to the popular Twitter app and it brings a subscription model | iMore](https://www.imore.com/tweetbot|6|update|popular|twitter|app|and|it|brings|subscription|model) + +- [ ] [Tweetbot 6 arrives for iPhone and iPad with a subscription model](https://www.engadget.com/tweebot-6-tapbots-twitter-app-subscription-model-launch-110526052.html) | *Engadget* + +- [ ] [Tweetbot 6 Moves to Subscription Pricing](https://www.macstories.net/news/tweetbot|6|moves|to|subscription|pricing/) | *MacStories* + +- [ ] [Tweetbot 6 released with new subscription pricing – TechCrunch](https://techcrunch.com/2021/01/26/tweetbot|6|released|with|new|subscription|pricing/) + +- [x] [Tweetbot 6: essential updates and a monthly subscription to the iPhone’s best Twitter app](https://www.theverge.com/2021/1/26/22250899/tweetbot|6|tapbots|ios|app|update|subscription|service|twitter|api) | *The Verge* + +- [ ] SoldierKnowsBest’s [ancient Tweetbot Video](https://youtube.com/watch?v=DE1YHcoPxMk&feature=share)Embed (Maybe) + +- [x] Strange, possibly controversial threat from Apple regarding taking Tweetbot 5 down. ([Tweet](https://twitter.com/tapbot_paul/status/1354145779494100992?s=20)) + +- [x] [[Tweetbot 5 iOS Review | The Psalms]] +> There has nev­er been — nor will there be, I think — a client for Twit­ter that can replace some use of its own prop­er­ties. + +- [x] [Tapbots keyboard shortcut feedback email thread](https://app.sparkmailapp.com/web-share/iolBCMqOjnPNrnPP7i0RpYLNieB3e9bfdx-M6YEB) (Spark) + +- [x] “[Data Privacy Day, Black History Month, Executive Changes, Tweetbot 6, and Record-Breaking Financial Results](https://macstories-unwind.simplecast.com/episodes/data-privacy-day-black-history-month-executive-changes-tweetbot-6-and-record-breaking-financial-results-eO_2aHGi)” | *MacStories Unwind* +::[Here’s the clipped mp3](https://files.mastodon.social/media_attachments/files/105/697/491/771/381/283/original/fd734e69f18c4b51.mp3):: + +- [ ] [Twitter confirms plans to experiment with new models, like subscriptions, in 2021](https://techcrunch.com/2021/02/08/twitter-confirms-plans-to-experiment-with-new-models-like-subscriptions-in-2021/) | *TechCrunch* + +- [ ] [The 10 best apps for new iPhones](https://www.theverge.com/2018/12/25/18146897/best-iphone-apps-2018-email-photos-maps-weather) | *The Verge* + +- [x] [12 great apps for your new iPhone in 2020](https://www.theverge.com/22187376/best-iphone-apps-2020-apple-ios) | *The Verge* +> Twitter is a vaguely terrible way to spend your time these days, but if you (like me) can’t tear yourself away from the social media service / entryway into hell, you’ll want Tweetbot, which actually makes using Twitter far less painful. Tweetbot shows you the tweets of the people you follow, in the order that they tweeted them. There are no ads or promoted tweets, powerful mute filters to block out unwanted noise, and (thanks to Twitter’s unfriendly API changes) no notifications to constantly ping you to come back to the app. + +- [ ] [Tweetbot 6 Moves to Subscription Pricing - MacStories](https://www.macstories.net/news/tweetbot-6-moves-to-subscription-pricing/) + +- [ ] [Tweetbot 6 Launches With Design Updates and Subscription Pricing - MacRumors](https://www.macrumors.com/2021/01/26/tweetbot-6-subscription-pricing-change/) + +- [ ] [Michael Tsai - Blog - Tweetbot 6 for iOS](https://mjtsai.com/blog/2021/01/26/tweetbot-6-for-ios/) + +- [ ] “Twitter takes forever to do anything” | [Kara Swisher](https://pca.st/episode/483b6064-7255-47cb-9f13-75f89e6fb91e) + + +#tb6 \ No newline at end of file diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/The Subscription Issue _ Tweetbot 6.md b/notes/Bear Notes/Tweetbot 6 for iOS Review/The Subscription Issue _ Tweetbot 6.md new file mode 100644 index 00000000..a44a9f27 --- /dev/null +++ b/notes/Bear Notes/Tweetbot 6 for iOS Review/The Subscription Issue _ Tweetbot 6.md @@ -0,0 +1,12 @@ +# The Subscription Issue | Tweetbot 6 +- [ ] [@tapbot_paul](https://twitter.com/tapbot_paul/status/1354195574459936780) +> The subscription “backlash” hasn’t been anywhere near as bad as I thought it’d be. Pretty sure the last time we did a paid upgrade (you know in 20 freaking 15) it was quite a bit worse. + +- [ ] [@tapbots](https://twitter.com/tapbots/status/1354179910294712320) +> @iAlexLopes if you've purchased ::within the last year:: Tweetbot 6 will be fully functional for up to a year after the time you've purchased. + +- [ ] [r/Apple thread](https://reddit.com/r/apple/comments/l5kqlm/tweetbot_6_moves_to_subscription_pricing/) + +- [ ] [Twitter launches new API as it tries to make amends with third-party developers](https://www.theverge.com/2020/8/12/21364644/twitter-api-v2-new-access-tiers-developer-portal-support-developers) | *The Verge* + +#tb6 \ No newline at end of file diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review.md b/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review.md new file mode 100644 index 00000000..0da69d9e --- /dev/null +++ b/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review.md @@ -0,0 +1,64 @@ +# TweetBot 6 for iOS Review +![](TweetBot%206%20for%20iOS%20Review/Photo%20Feb%209,%202021%20at%20144503.jpg) +![Various - Tweetbot 6](https://i.snap.as/OgxERkXE.png) + +## In the bleak face of Twitter’s centralization, Tapbots refuses to give up on its mobile client. +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. [807 days ago](https://bilge.world/tweetbot-5-ios-review), I told you lots about the history surrounding the development of Tweetbot 5, which I confidently described as “likely the last com­pet­i­tive third-par­ty Twit­ter app for iOS.” After spending the past few months diving deep into iOS in preparation to [review and reflect](https://github.com/extratone/bilge/issues/45) 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. 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**. At this moment, [it is listed on the App Store](https://apps.apple.com/us/app/tweetbot-6-for-twitter/id1527500834) as an “Early Release” version, though its predecessor can still be downloaded by those who’ve already purchased it in the past, like me. `Footnote: Though I was still able to find [a share link](https://apps.apple.com/us/app/tweetbot-5-for-twitter/id1018355599), it appears to be unopenable in a regular web browser, which will simply prompt you to open iTunes.` 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. Notably, Tweetbot developer company Tapbots was [apparently required](https://twitter.com/tapbot_paul/status/1354145779494100992?s=21) to take down Tweetbot 5’s store listing 30 days before releasing Tweetbot 6. `Footnote: I can’t think of any innocuous reason for Apple to do so. A month’s absence of a given software company’s flagship application sounds like a nerve-wracking punishment, nothing more. Discussed at length in this blog post written by someone I don’t have the time to look up, right now: https://mjtsai.com/blog/2021/01/26/tweetbot-6-for-ios/)` + +https://soundcloud.com/compaqclub/macstories-on-tweetbot-6 + +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. 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. As my old fav, *The Verge* noted in [their coverage of 6](https://www.theverge.com/2021/1/26/22250899/tweetbot-6-tapbots-ios-app-update-subscription-service-twitter-api), blame for these omissions rests solely on Twitter, Inc., itself, who’s continued to hold its API development inordinately close-to-chest. I didn’t bother to find out about this, though, because my first assumptions upon poking around the new app - especially after encountering its new subscription requirement in order to use any of its substantive features - was that its developers had ceased any actual time investment into the app long ago, and that 6 was a new version in number and rudimentary visual updates, only, shoved out in hopes of peaking old, loyal users like myself enough to get us to download it, at least. In the disappointment I’d already expected, I closed and immediately deleted the app. + +I’ve paused everything else to write you on this, though, because the story is actually much bigger. Had I investigated any further that first time, I would have discovered an odd amount of buzz coming from even the most mainstream of tech media in a simple search. (Yes, I am ashamed about it.) You’re still reading, but perhaps - as I was, originally - you are doing so from an appropriately-jaded, well-read perspective on software, generally, in 2021. Perhaps you’re looking at the search results, yourself, and wondering if you’re dreaming. *Dedicated coverage of a fucking third-party Twitter client iteration??? At this point in history? What in fuck?* I’m fairly certainly neither of us are, though: fucking Tweetbot made headlines on [Engadget](https://www.engadget.com/tweebot-6-tapbots-twitter-app-subscription-model-launch-110526052.html), [TechCrunch](https://techcrunch.com/2021/01/26/tweetbot-6-released-with-new-subscription-pricing/), [9to5Mac](https://9to5mac.com/2021/01/26/tweetbot-6-new-features-subscription-model/), [MacStories](https://www.macstories.net/news/tweetbot-6-moves-to-subscription-pricing/), [iMore](https://www.imore.com/tweetbot-6-update-popular-twitter-app-and-it-brings-subscription-model), [MacRumors](https://www.macrumors.com/2021/01/26/tweetbot-6-subscription-pricing-change/), and others. No, it’s not 2010 again. In fact, *The Verge*, at least, has never given up on Tweetbot. If my long term memory had been functioning, I would have remembered noticing its spot in “[12 great apps for your new iPhone in 2020](https://www.theverge.com/platform/amp/22187376/best-iphone-apps-2020-apple-ios):” + +> Twitter is a vaguely terrible way to spend your time these days, but if you (like me) can’t tear yourself away from the social media service / entryway into hell, you’ll want Tweetbot, which actually makes using Twitter far less painful. Tweetbot shows you the tweets of the people you follow, in the order that they tweeted them. There are no ads or promoted tweets, powerful mute filters to block out unwanted noise, and (thanks to Twitter’s unfriendly API changes) no notifications to constantly ping you to come back to the app. + +Here’s to Chaim for exposing me to a perspective I never would have otherwise considered: Tweetbot’s lack of push notifications as a *positive*. If you’re wondering, no, this new app does not ~yet~ include any additional notification integration, and it’s not clear whether or not it’s on Tapbots future roadmap for the app, or where. As for the reality of integrating Tweetbot 6 into your current Twitter use, I stand by my argument that deleting the native Twitter app isn’t really an option if you plan to ever view your notifications on your phone. The popular assumption (I assume) if you’re still reading is that you are a “poweruser,” meaning details about my own configuration are probably irrelevant. If by chance you’ve just downloaded Tweetbot for the first time, you should take the time to disable notifications for Tweetbot entirely, but leave them on for the native Twitter app, even if you decide to banish it to your App Library. Before I began any work on this review, I made sure to swap in Tweetbot 6 where the native app had been in my dock for several years, now. I originally pushed the native app all the way to page 6, but immediately found this extreme. Instead, I put it in the bottom-right corner in my second screen, as you can see in the screenshot below (which also serves as proof, if you needed it.) + +![](TweetBot%206%20for%20iOS%20Review/Photo%20Feb%2010,%202021%20at%20150834.jpg) +![Tweetbot vs Native Twitter Proof](https://i.snap.as/WMyY9kLc.png) + +I should also note how much my own engagement on Twitter has diminished in the past 3-5 years. Not to manifest tiny violins - in turn, my engagement on (and investment in) [Mastodon](http://bit.ly/dbmasto) has increased exponentially, and it’s of a *much* higher quality. I bring it up for context’s sake: I can afford to prioritize Tweetbot in my Twitter use because of how few daily notifications I get - a number which is unusual for someone who uses Twitter as much as I do. Inevitably, my own use is once again going to factor heavily in this work, as is the significance of my relationship with Twitter, generally, in my life. If you didn’t already know, I’ve met basically all of my friends since high school through Twitter. As of this moment, my private “Friends” Twitter List includes 149 accounts, and I’ve spent more than 10 years, now, reading almost every single one of their Tweets. I have been as critical of the service as anyone, but - whether or not either of us are willing to acknowledge it, wholly - I believe the intimacy of this arrangement to exceed that of any in-person relationship *I* have ever had. `Footnote: Though I have been trying unsuccessfully to write more on this dynamic for years, I still intend to do so, one day.` Reading the random thoughts of these people seconds or minutes after they’ve popped into their heads for all this time has been an experience unique to the format Twitter pioneered, if not to the service, itself. I have no choice but to acknowledge that I am *deeply* invested in not just Twitter, but Twitter’s less-than-visible Lists feature, emotionally and intellectually. When I hit my [follow limit](https://twitter.com/neoyokel/status/1281646353102147584), several years ago, Lists also became my single means of acquiring new connections on the network. If it were to be removed, I would lose this ability, entirely, as well as any reasonable means of communicating with any of my friends. + +https://www.youtube.com/watch?v=IO-ZSD-vymc + +Perhaps you understand, now, why I have [written](https://bilge.world/twitter-lists) and [Tweeted](https://twitter.com/i/events/996616971880882176) so extensively about Lists. You should also understand just how miraculous the possibility of Tweetbot’s new future now seems, personally, unless you’re new to all of these ideas and don’t feel like reading that big olé Tweetbot 5 review of mine (which is fine.) Before I go into the history of Tweetbot, let me first share the single most telling feature in Tweetbot of Tapbots’ belief in using Lists and share some evidence of *others’* present day belief in Tweetbot. Shamefully, I’ve spent several years - tens, if not hundreds of thousands of hours - using Lists in Tweetbot, oblivious to its upmost Lists integration: “[Use Lists as Timeline](https://tapbots.com/support/tweetbot6/tips/list.php).” Had I actually bothered to look at the support docs at any point, I would have discovered this long ago, which would have almost certainly made my given year. **If you use Tweetbot and Lists, for the love of Gourd, please take a look**. Here’s what those docs currently say, in full: + +> One long time Tweetbot feature is the ability to use any of your lists as your main timeline. To do this, all you have to do is hold down on the “Timeline” label in the navigation bar (in the timeline tab) and a menu populated with your lists will appear. Select one and that will become your current timeline. You can switch to another list or back to your main timeline any time by performing the same action. + +Even after reading this multiple times, it still was not obvious to me what it was talking about, and I was unable to find precisely *zero* visuals on The World Wide Web of this action taking place, so I recorded and uploaded [the video embedded above](https://youtu.be/IO-ZSD-vymc). Good God, how I wish I’d been a more detail-oriented young man! I’ll be privatizing my self-punishment from here on out, though, so bear with me. + +![](TweetBot%206%20for%20iOS%20Review/Photo%20Feb%2011,%202021%20at%20141603.jpg) +![Lists Integration | Tweetbot 6](https://i.snap.as/oZ5u34QP.png) + +The discourse surrounding Tapbots’ recent announcement has already reached a higher decibel count than I would have ever expected, so it’s obvious there are plenty of *users* who still [love Tweetbot](https://twitter.com/neoyokel/status/1064579914538602496), and you already know from the beforelinked stories that *The Verge* has also stood firmly by it as the preferred Twitter experience. It takes a wee bit of digging, though, to discover the subtle bets on both Tweetbots and Lists from no less than Apple, Inc., itself. In the official Apple Shortcuts Gallery, a curated list entitled “Twitter Better” includes “[Open Twitter Lists](https://www.icloud.com/shortcuts/161bb19df7ee47fa8b31a0c0fb43307b)” at number 1. In 5th position is “[Open in Tweetbot](https://www.icloud.com/shortcuts/c148d4f0dfbc45d6bf8bad6bb67d519c),” and “[Open in Twitter App](https://www.icloud.com/shortcuts/c45206139b9e47eb8de780e686350022)” (3rd,) is configured *by default* to first ask you to choose between Tweetbot and Twitter’s native app, despite its title. + +![](TweetBot%206%20for%20iOS%20Review/Photo%20Feb%2011,%202021%20at%20143957.jpg) +![Tweetbot Bets in Shortcuts](https://i.snap.as/sZXfdk8L.png) + +As for App Store rankings, the fact that Tweetbot 5 was forcibly removed from public listings makes it impossible to meaningfully judge recent popularity of Tweetbot on iPhone/iPad. Its MacOS-based sibling, though (called Tweetbot 3,) was the *second most popular* paid app [on the Mac App Store](https://apps.apple.com/us/app/tweetbot-3-for-twitter/id1384080005) as of [February 6th, 2020](https://i.snap.as/Uq8bRMF8.png). That’s the day I borrowed my Mom’s MacBook Pro for a short while to check up on MacOS Big Sur, when I downloaded the current version (3.5.2, if you wanted to know) of Tapbots’ desktop Twitter client and [messed around with it](https://www.youtube.com/watch?t=219&v=vHDNdMux16g) enough to tell you that it’s as wonderful as ever. (Had I not switched back to Windows as my primary desktop OS a decade ago, I would use it every single day.) + +![](TweetBot%206%20for%20iOS%20Review/Photo%20Feb%2011,%202021%20at%20150738.jpg) +![Tweetbot 3 for MacOS Version 3.5.2](https://i.snap.as/1bbw5iFH.png) + +I suspect most active Twitter users in 2021 would be even more surprised to discover Tweetbot’s remaining, discreet hold on today’s Twitter experience than I was, assuming most of them joined more recently than myself and those I regularly interact with. For the sake of this Post, I reached out to Tapbots with an interview request about “Tweetbot’s roadmap, Apple’s requirement that [they] remove 5 from the App Store 30 days beforehand, and why [they’ve] decided to take this (risky, imo) bet on making our lives better,” though I don’t expect a reply, which is fine. They *did* respond to my support request regarding hardware keyboard shortcut support very quickly, saying they’ll look into it. (Without being verbose, I’ll just tell you that if a near future update to the app fixes the F and ⌘ + R +shortcuts, I *will* shit out my whole ass.) + +![](TweetBot%206%20for%20iOS%20Review/Photo%20Feb%2011,%202021%20at%20191851.jpg) +![Poll Support in Tweetbot 6](https://i.snap.as/kCCCZzh5.png) + +## Present +Before I dig into the controversy and hypotheticals surrounding what Tweetbot 6 might become, let’s take a moment to qualify it vs all of one’s options to interact with Twitter on iOS *currently* (as in, Feb 11, 2021 at 19:24.) It’s almost certainly premature to do so, but skeptical readers would note, I’m sure, that its listing on the App Store is “early release” in name only, that I have just spent money on this specific version, which should therefore render inert the normal exceptions a review would make for beta or pre-release software. + + + +![](TweetBot%206%20for%20iOS%20Review/Photo%20Feb%2011,%202021%20at%20181459.jpg) +![All Tweetbot Themes](https://i.snap.as/W884QXpS.png) + +## The Subscription Issue +Notice that almost every single one of the stories linked above contains mention of Tweetbot’s move to recurring subscriptions in its header. + +Now that you’re familiar with my personal investment in Twitter and Tweetbot, perhaps you’re better equipped to understand + + +#ios #tb6 \ No newline at end of file diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 10, 2021 at 150834.jpg b/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 10, 2021 at 150834.jpg new file mode 100644 index 00000000..15d92152 Binary files /dev/null and b/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 10, 2021 at 150834.jpg differ diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 11, 2021 at 141603.jpg b/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 11, 2021 at 141603.jpg new file mode 100644 index 00000000..fae7da7a Binary files /dev/null and b/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 11, 2021 at 141603.jpg differ diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 11, 2021 at 143957.jpg b/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 11, 2021 at 143957.jpg new file mode 100644 index 00000000..fe5b723c Binary files /dev/null and b/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 11, 2021 at 143957.jpg differ diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 11, 2021 at 150738.jpg b/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 11, 2021 at 150738.jpg new file mode 100644 index 00000000..891f51e3 Binary files /dev/null and b/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 11, 2021 at 150738.jpg differ diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 11, 2021 at 181459.jpg b/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 11, 2021 at 181459.jpg new file mode 100644 index 00000000..f995c506 Binary files /dev/null and b/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 11, 2021 at 181459.jpg differ diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 11, 2021 at 191851.jpg b/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 11, 2021 at 191851.jpg new file mode 100644 index 00000000..9b581c52 Binary files /dev/null and b/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 11, 2021 at 191851.jpg differ diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 9, 2021 at 144503.jpg b/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 9, 2021 at 144503.jpg new file mode 100644 index 00000000..cd905ffa Binary files /dev/null and b/notes/Bear Notes/Tweetbot 6 for iOS Review/TweetBot 6 for iOS Review/Photo Feb 9, 2021 at 144503.jpg differ diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 5 iOS Review _ The Psalms.md b/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 5 iOS Review _ The Psalms.md new file mode 100644 index 00000000..adbd8df1 --- /dev/null +++ b/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 5 iOS Review _ The Psalms.md @@ -0,0 +1,32 @@ +# Tweetbot 5 iOS Review | The Psalms +![](Tweetbot%205%20iOS%20Review%20%7C%20The%20Psalms/g5G5uUb.jpeg) +On Win­dows XP bal­lot day, I spent *my* beat­nik-ass time mar­veling at the (seem­ing­ly) abrupt avail­abil­i­ty of some gen­uine­ly inno­v­a­tive social apps on the Apple App Store for the first time since iOS 7(?) Of course, I am aware that rea­son­able peo­ple would regard a “sneak peek,” NDA-vio­lat­ing, per­fect­ly Adobe Pre­miered app review to be pret­ty fuck­ing lame, and I won’t dis­pute any accu­sa­tions to the tune of “just an insane white guy with a Word­Press site,” but I still believe it’s impor­tant to talk about soft­ware *espe­cial­ly* because vir­tu­al­ly every­one uses it (as opposed to qui­et­ing down just when these apps and the peo­ple who make them attain the most advan­ta­geous pos­si­ble posi­tion to fuck the whole world.) +That said, I’m going to keep this as brief and unre­vi­sion­ist as I can: Tweetbot’s [lat­est iter­a­tion](https://9to5mac.com/2018/10/18/tweetbot-true-dark-mode-gifs/) may actu­al­ly jus­ti­fy the [ded­i­cat­ed sub­red­dit](https://www.reddit.com/r/Tweetbot/) I’ve just dis­cov­ered! (Reddit’s the last place any­one wants to talk about apps, I guess.) I’ve com­plained at length about Twitter’s increas­ing­ly hos­tile (but [jus­ti­fied, sortof](https://www.theverge.com/2018/4/25/17274828/twitter-earning-q1-2018-profit-user-growth) ) treat­ment of its once [aston­ish­ing­ly diverse land­scape of third-par­ty clients and tools](https://mashable.com/2009/05/02/twitter-iphone-apps/#S_O.z..2mqqJ), yet I’d hon­est­ly grown sig­nif­i­cant­ly in accept­ing that the dynam­ic would nev­er again see the pow­er of the world’s most cash-stuffed com­pa­nies deliv­ered into the sweaty hands of small, kooky one and two-man teams, and it *nev­er* would’ve occurred to me that Tweet­bot was still around — much less get­ting ready to update its trusty old app with a release that would sud­den­ly make it clear­ly more sta­ble *and* bet­ter-look­ing than its last com­peti­tor: [the Native Fuck, itself](https://itunes.apple.com/us/app/twitter/id333903271?mt=8), which has also under­gone [sig­nif­i­cant cos­met­ic surgery](https://www.searchenginejournal.com/twitter-redesigns-ios-app-for-one-handed-scrolling/276541/), recent­ly. Name­ly, they moved the *one fuck­ing but­ton* that’s giv­en the app a usabil­i­ty pre­mi­um over its mobile web-based low-rent clone. +“The com­pose but­ton has been moved to the bot­tom right-hand cor­ner and “floats” as users scroll down their time­line. That means the but­ton is always avail­able to quick­ly send a tweet when the mood strikes.” +Yeah okay, *Matt*. +> We’ve got a shiny, new com­pose but­ton to unveil on Twit­ter for iOS! Eas­i­er than ever to use, the float­ing icon is promi­nent­ly dis­played and per­fect for one-hand­ed scrolling and Tweet com­pos­ing. Pro tip: Press and hold the icon to access your drafts, pho­tos, and the GIF gallery. - [@Twit­terSup­port](https://twitter.com/TwitterSupport/status/1057726896765423616) +Twit­ter Sup­port is no [@Cher](http://twitter.com/cher), yeah, but it seems strange that less than a thou­sand of Twitter’s [more than 300 mil­lion month­ly users](http://bilge.world/media/birdearn.pdf) would both­er to engage with the announce­ment of a sig­nif­i­cant fun­da­men­tal change to its infra­struc­ture. Imag­ine if the fed­er­al gov­ern­ment announced via White House press con­fer­ence that every stop­light in the Unit­ed States was going to have its yel­low light removed to “stream­line work­flow” with­out any fur­ther expla­na­tion, yet only 1000 *total* Amer­i­cans even both­ered to tune in to the tele­vi­sion cov­er­age across all the news net­works. It’d be strange, yeah? Well, y’all are using Twit­ter more than you’re dri­ving, I’ll bet. Next time, **get out and** [vote on my Twit­ter poll](https://twitter.com/NeoYokel/status/1062859883211620352) **, you fas­cist!** +In my Twit­ter glo­ry days — that is, when I used to spend the entire­ty of every one of my com­mu­ni­ty col­lege class­es Tweet­ing from my phone — there was a healthy offer­ing of third-par­ty clients on both mobile and desk­top that filled the eng­lish of the era’s soft­ware media with an absolute­ly bar­bar­ic brand-beat­en pile of lin­guis­tic Twit­trash. After Twin­kle — one of the [ear­li­est and ugli­est](https://www.macrumors.com/2008/07/17/twinkle-another-twitter-client-in-app-store/) ways to use Twit­ter ever — you’d have to choose between Twit­pic, Tweet­deck, Twit­ter­counter, Twit­ter­feed, Twhirl, Twit­turly, Twt­poll, Retweet­ist, Tweepler, Hel­lotxt, Twit­dom, Tweetscan, Tweet­burn­er, Tweet­vi­sor, Twit­ter­vi­sion, Twibs, Twistori, and Twit­bin. These are just a few I picked up from a [10-year-old](https://techcrunch.com/2009/02/19/the-top-20-twitter-applications/) [TechCrunch](https://techcrunch.com/2009/02/19/the-top-20-twitter-applications/) [report](https://techcrunch.com/2009/02/19/the-top-20-twitter-applications/) list­ing the top 21 Twit­ter appli­ca­tions by traf­fic. ***Twibs*** **.** +Now, I have to stop myself from dig­ging too deep here and attempt­ing some­thing absurd like *The His­to­ry of Twit­ter Clients*, but the fuck­ing mate­r­i­al is there! I could spend an entire after­noon going through YouTube search­es and gad­get blogs because it brings me back to that time when I lived every day assum­ing these things were going to con­tin­ue to aston­ish for my entire adult­hood. So many incred­i­ble ideas! *How­ev­er,* I’m going to save them for lat­er and focus on the cream of the crop, so to speak: **Twit­terif­ic** and **Tweet­bot**, which has been a long­time favorite of mine. As I said, it was in com­mu­ni­ty col­lege that I first ponied up mon­ey for Tweet­bot 3 on my iPhone 4S sim­ply because the hype over it among app and gad­get nerds was *so bonkers* that it man­aged to spill over into my life, despite the fact that iOS7 and I were hav­ing seri­ous issues in our mar­riage. +If you trust Mark Wat­son with your life as I do, you’d bet­ter believe that Tweet­bot has been “ [a scream­er](https://youtu.be/DE1YHcoPxMk) ” since its very begin­ning, when it pio­neered the *Pre­mi­um Poweruser* seg­ment, for which a demo­graph­ic appar­ent­ly still exists. It was *fast*, yet always notice­ably smoother than the native app, just as the newest release is today. I must point out, though, that the blog­gers and YouTu­bers who’ve insist­ed that Tweet­bot or Twit­ter­rif­ic or any oth­er pre­mi­um app could replace the native Twit­ter app entire­ly on iPhone even before they were stripped of a most live/push func­tion­al­i­ty (which I’ll come back around to in just a moment,) are undoubt­ed­ly lying to them­selves — as good as they got, they nev­er over­took Twitter’s own app in imme­di­a­cy terms, which is almost inevitably going to present fun­da­men­tal deter­rence on the part of the active Twit­ter user who intends to rid them­selves of the default pedes­tri­an avenue of admin­is­tra­tion. Tweet­bot solved a lot of things, it real­ly is *daft* when it comes to noti­fi­ca­tions. It wouldn’t be the end of the world if they came a few hun­dred sec­onds late — it’s that they’re nev­er pre­dictably or con­sis­tent­ly so, which sev­ers entire­ly the human per­cep­tion of engaged *plugged-in-ness*, if you will. It’s the same phe­nom­e­na Chuck Kloster­man explores best in the con­text of DVRing live sports to watch lat­er. +> It’s dif­fi­cult to project fic­tion­al sce­nar­ios that are more oblique and unex­pect­ed than the cra­zi­est moments from real­i­ty. We all under­stand this. And that under­stand­ing is at the core of the human attrac­tion to live­ness. We don’t crave live sport­ing events because we need imme­di­a­cy; we crave them because they rep­re­sent those (increas­ing­ly rare) cir­cum­stances in which the entire spec­trum of pos­si­bil­i­ty is in play. +> -“ [Space, Time, and DVR Mechan­ics](http://grantland.com/features/space-time-dvr-mechanics) ” by Chuck Kloster­man. +Tweet­bot is unques­tion­ably a more thor­ough envi­ron­ment in which to explore Twit­ter than any oth­er third par­ty client, but it can’t do the live thing. Please do com­plain to Twit­ter, Inc. about the API sit­u­a­tion if you’re so inclined, but the sit­u­a­tion we’re going to find our­selves in +All I’m try­ing to say is, **there is no fuck­ing rea­son you’d delete the Twit­ter app** — hide it away in a fold­er and nev­er ever open it again if it dis­gusts you so, but leave its noti­fi­ca­tions set­tings on so that it can keep itself busy in there. Now *that* is a smart work­flow! In fact, it was mine! And it did work for such a long time that you’d prob­a­bly for­get about the arrange­ment in no time were there not the occa­sion­al obvi­ous dis­crep­an­cies between Tweetbot’s Mention’s tab and the native app’s instant noti­fi­ca­tions. There has nev­er been — nor will there be, I think — a client for Twit­ter that can replace *some* use of its own prop­er­ties. +I think Tweet­bot 3 *made* me into my own ridicu­lous equiv­a­lent of a “Poweruser.” Things are a lit­tle hazy now, but I know that I depart­ed my main Twit­ter account just before the app’s release, and I didn’t come back until 2015. I was going to school in the same old mall build­ing that housed the tool store in which I was also work­ing in full-time, which is sure­ly the only expla­na­tion for the shame­less­ness I demon­strat­ed in bring­ing a wire­less Apple Blue­tooth key­board to my class­es and plac­ing it behind the phone on what­ev­er sur­face was in front of me so that I could lean for­ward and type into iOS with my nose damned near touch­ing the screen. Strange­ly, I was not able to ver­i­fy when Blue­tooth key­board sup­port was added to iOS, but we’re going to [con­clude for the sake of con­ve­nience](https://www.reddit.com/r/iphone/comments/9y1bjd/when_was_support_for_bluetooth_keyboards/) that it was first includ­ed in the imme­di­ate pre­de­ces­sor to the iPhone 4S I was using then. +> The cognoscen­ti have been on Twit­ter for years now. Stephen Fry, the web service’s patron saint — in Britain at least, joined in 2008. How­ev­er, it wasn’t until ear­ly 2009, xsome­where around the time that Fry tweet­ed while stuck in a lift, that the ser­vice went tru­ly main­stream. Men­tions of Twit­ter, usu­al­ly involv­ing celebri­ties, could be found in news­pa­pers and on break­fast tele­vi­sion. +“ [Top 10 tech­nol­o­gy high­lights of 2009](https://www.telegraph.co.uk/technology/6817359/Top-10-technology-highlights-of-2009.html) ” | **The Telegraph** +If you’ve made it this far, you’ve already seen the demos and skimmed reviews at least. You should know by now whether or not Tweet­bot 5 is worth it to you in pure­ly func­tion­al terms, but I think we should all acknowl­edge that **this release of Tweet­bot is like­ly the last com­pet­i­tive third-par­ty Twit­ter app for iOS**. The mess that is Twit­ter, Inc. has [made clear this year](https://blog.twitter.com/official/en_us/topics/product/2018/investing-in-the-best-twitter-experience-for-you.html) that it intends to pri­or­i­tize its own clients over main­tain­ing the APIs nec­es­sary for oth­ers to receive push noti­fi­ca­tions. And when I say “its own,” I’m also refer­ring to our dear­est [Tweet­Deck](https://youtu.be/EHDOQVAQzec), which they in fact *absorbed*. From a busi­ness per­spec­tive, it makes sense: only “six mil­lion App Store and Google Play users installed the top five third-par­ty Twit­ter clients between Jan­u­ary 2014 and July 2018,” [accord­ing to TechCrunch](https://techcrunch.com/2018/08/17/6-million-users-had-installed-third-party-twitter-clients/). I nev­er expect­ed to see Tweet­bot on the App Store charts again, nor would I have con­sid­ered that [Echophon](https://itunes.apple.com/us/app/echofon-for-twitter/id286756410?mt=8), [Tweet­Cast­er](https://itunes.apple.com/us/app/tweetcaster-for-twitter/id420792544) or Twit­ter­rif­ic would have been left avail­able. They’re on the App Store, at least, and I can con­firm that they all tech­ni­cal­ly *still work*, but it’s safe to say they’re show­ing their fuck­ing age. Tweet­bot and Twit­ter­rif­ic, though, are not just satel­lite prod­ucts of the plat­form — they *[lit­er­al­ly built it](https://furbo.org/2011/03/11/twitterrific-firsts/)*. These two are the poles that have spent Twitter’s life­time thus far demon­strat­ing for the com­pa­ny and its user­base their own respec­tive inter­pre­ta­tions of a mobile social appli­ca­tion. Today, they are unit­ed — along with [Talon](http://klinkerapps.com/talon-overview/) and [Tweet­ings](https://www.tweetings.net/apps/) — in a [plea for con­tin­ued access](http://apps-of-a-feather.com/) to the plat­form they helped estab­lish on behalf of Twit­ter users and devel­op­ers around the world. + +Both Tweet­bot and Twit­ter­rif­ic are in their 5th ver­sions, and nei­ther has actu­al­ly changed much since iOS 7. (Twit­ter­rif­ic appears to still be in the same ver­sion num­ber.) Fac­ing the grow­ing walls around the ser­vice, one strug­gles to imag­ine them sur­viv­ing more than one or two iOS releas­es, but [I’ve been wrong before](https://twitter.com/NeoYokel/status/712292559058444288). (In fact, I dis­cov­ered yes­ter­day that Look­book is [still around some­how](https://lookbook.nu/mom).) By the time iOS 7 came around, the new native Twit­ter app still [looked fuck­ing ter­ri­ble](https://www.cultofmac.com/246067/twitter-for-ios-7-released-with-new-design-icon-on-iphone-and-ipad/). When Tap­bots [released Tweet­bot 3](https://mashable.com/2013/10/24/tweetbot-3-for-iphone-review/#SDbMxlCvFPqx), every­thing about its visu­al expe­ri­ence was beyond any­thing we’d seen on the iPhone before and its effec­tive­ness as a Twit­ter tool was imme­di­ate­ly rec­og­niz­able in con­trast with even Jack’s brand-new app and mobile web expe­ri­ence. The ani­ma­tions were taste­ful and smooth and the “pro user” label on Tapbot’s demo­graph­ic allowed them to ful­ly explore the func­tion­al­i­ty of iPhone’s ges­tures sep­a­rate any bond with the hypo­thet­i­cal­ly least-capa­ble user. + +This is a dynam­ic which I am appar­ent­ly unable to avoid across just about all of my sub­jects — includ­ing [dig­i­tal media](http://extratone.com/freq) — so you may take it as gen­er­al­ly unrea­son­able or extreme, but I’m near­ly as tired of being treat­ed as an idiot *user* as I am an idiot *read­er*. *Read­abil­i­ty* is to *Usabil­i­ty*, etc. It’s espe­cial­ly aggra­vat­ing when I *could* do so much more if devel­op­ers would just assume I’m capa­ble of any knowl­edge acqui­si­tion or intel­lec­tu­al growth what­so­ev­er. Except for a few left­over key­board short­cuts, the native Twit­ter app’s only func­tion are the most obvi­ous to engage with, as per the high­est pos­si­ble stan­dards of use, which would make per­fect sense if it was paired with com­pe­tent invest­ments in *Acces­si­bil­i­ty*, but Twit­ter always appears to [detest the sub­ject](https://theoutline.com/post/2458/there-are-still-some-people-on-twitter-who-don-t-have-280-characters?amp=&zd=1&zi=zbzf6tkp), even while qui­et­ly putting in some of the work. Thanks to Mastodon’s explic­it and vis­i­ble acknowl­edge­ment of acces­si­bil­i­ty by way of just one young Ger­man man and a vol­un­teer team, we cer­tain­ly know it’s *not* because it’s an expen­sive one at all. (The “if Mastodon can do it than Twit­ter can *def­i­nite­ly* fuck­ing do it” argu­ment can be expand­ed almost with­out lim­it.) + +> Some­where out there is a social media man­ag­er using a screen read­er whose pro­fes­sion­al­ism has been under­mined by the belief that the update is avail­able to every­one. We deserve equal access to the tools our peers take for grant­ed, and the secu­ri­ty to know that we will be able to do our jobs tomor­row regard­less of updates. -Kit Englard for [The Out­line](https://theoutline.com/post/2458/there-are-still-some-people-on-twitter-who-don-t-have-280-characters) + +I would like to com­mend myself now for mak­ing it this far with­out men­tion­ing **Lists** — a sub­ject which I’ve already [Tweet­ed](https://twitter.com/i/moments/996616971880882176) and [writ­ten](http://www.extratone.com/tech/lists/) about exten­sive­ly — but this time, I have the won­drous bless­ing of two pre­miere mobile soft­ware com­pa­nies who rec­og­nized the poten­tial pow­er in list func­tion­al­i­ty to dis­pel or avoid most of the inher­ent risks assigned to the usage of a social net­work like Twit­ter and bet heav­i­ly on it. Nei­ther can be uti­lized to the fullest with­out lists and *wouldn’t it be such a shame* to not get your money’s worth? Tap­bots expand­ed their cura­tive abil­i­ty tremen­dous­ly by adding cus­tomiz­able fil­ters to any time­line in Tweet­bot, allow­ing the user to infi­nite­ly manip­u­late incom­ing posts with any com­bi­na­tion of every vari­able sup­port­ed by the core Twit­ter code itself. With­in a mat­ter of sec­onds, you could cre­ate a fil­ter that will exclude all Tweets except for those from unver­i­fied accounts that men­tion “blimps” and include a media attach­ment and apply this fil­ter to any of the app’s time­line views — includ­ing Home, Men­tions, Pro­file (your own Tweets,) your Favorites, and your Search­es — every­thing but your Direct Mes­sages can be sort­ed this way. + +“ [Tweet­bot for iOS Tips](https://tapbots.com/tweetbot/tips/),” Tap­bots Tweet­Bot and I accom­plished a lot of sort­ing togeth­er, and it wouldn’t have occurred to me had it not crept to #1 Paid Social App again a few weeks ago that per­haps [my bias towards Twit­ter lists](http://www.extratone.com/tech/lists/) could be entire­ly attrib­uted to my ear­ly use of Tweet­Bot and Twit­ter­rif­ic, which allowed me to amass a [Fol­low­ing count](https://twitter.com/neoyokel/following) of over 5000 with­out phys­i­cal­ly per­ish­ing or men­tal­ly dis­in­te­grat­ing to the point of unde­ni­able insan­i­ty. How­ev­er, by the time [Tweet­Bot 4 was released](https://www.theverge.com/2015/10/1/9432291/tweetbot-4-ipad-iphone-available) in 2015, it had long since swapped places with the native app with­in my iPhone’s home­screens and was only used when I felt par­tic­u­lar­ly like Tweet­storm­ing from a sta­tion­ary sit­u­a­tion. From my wire­less Apple Key­board, this meant Cmd (⌘)-N to com­pose a Tweet and ⌘-Enter to send it. +Today — [in Tweet­bot 5](https://www.macstories.net/reviews/tweetbot-5-for-ios-brings-a-redesign-dedicated-giphy-support-and-a-new-dark-mode/) — this con­tin­ues to be a tried-and-true method of Tweet­ing Tweets on Twit­ter, smooth­ly and effi­cient­ly, as always. Return­ing to Ye Olde Alter­na­tive in 2018 yields both famil­iar *and* new­ly-imple­ment­ed goods: ani­ma­tion and audio noti­fi­ca­tions are car­ried over and/or updat­ed as need­ed to main­tain a flu­id and fresh expe­ri­ence. The abil­i­ty to switch between its intel­li­gent­ly-cho­sen col­or themes with a two-fin­gered ver­ti­cal swipe, alone will be jus­ti­fi­ca­tion enough for many users like myself to hand over anoth­er $4.99 to the Tap­bots devel­op­ers who’ve man­aged against all odds to one-up Twitter’s own mobile app devel­op­ment one last time. Over any oth­er alter­na­tive app, Tweet­bot 5 retains the robust qual­i­ties nec­es­sary to achieve #1 Paid Social App sta­tus on the App Store despite its new API shack­les. +[Tweetbot 5 iOS Review — The Psalms](http://bilge.world/tweetbot-5-ios-review) +#archive #tb6 \ No newline at end of file diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 5 iOS Review _ The Psalms/g5G5uUb.jpeg b/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 5 iOS Review _ The Psalms/g5G5uUb.jpeg new file mode 100644 index 00000000..dd30cfe1 Binary files /dev/null and b/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 5 iOS Review _ The Psalms/g5G5uUb.jpeg differ diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 6 Support Reply.md b/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 6 Support Reply.md new file mode 100644 index 00000000..e160ab9d --- /dev/null +++ b/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 6 Support Reply.md @@ -0,0 +1,16 @@ +# Tweetbot 6 Support Reply +Thanks for responding so promptly! Sorry I didn’t do the same. +## Shortcuts That Are *Not* Working +- **F Key** (To favorite.) +- **⌘ + R** (To reply to the selected Tweet.) + +## Shortcuts That *Are* Working +- **Shift + ⌘ + L** (Open links.) +- **Shift + ⌘ + U** (View user profile.) +- **Shift + ⌘ + R** (Refresh.) +- **⌘ + ⬆︎** and **⌘ + ⬇︎** (Scroll up and down) +- **Shift + ⌘ + [** and **Shift + ⌘ + ]** (Cycle through accounts.) +(And more but unfortunately I’m out of time lol.) + +I hope that helps. I also wanna say that I really appreciate you all continuing to work on TweetBot despite how bleak the Twitter client landscape must seem... And that I hope you’ll try your hand at a client for Mastodon one day. ;) +#correspondence #documentation #tb6 \ No newline at end of file diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 6 for iOS Review (Bear Notes).md b/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 6 for iOS Review (Bear Notes).md new file mode 100644 index 00000000..60bdc388 --- /dev/null +++ b/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 6 for iOS Review (Bear Notes).md @@ -0,0 +1,47 @@ +# Tweetbot 6 for iOS Review (Bear Notes) +`tweetbot-6-review-ios` + +- [x] [Tweetbot 6 on the App Store](https://apps.apple.com/us/app/tweetbot-6-for-twitter/id1527500834) +## Social +- [x] “[Which third-party Twitter app was your favorite?](https://twitter.com/NeoYokel/status/1064579914538602496)” | Twitter Poll + +- [ ] A potential Easter theme! +*Tweetbot is Risen.* +*A third-party Twitter client is Risen, indeed!* + +## Written +[[David Blue on Social Media Software]] +- [ ] In terms of reliability/bugs, I can say with 100% honesty that Tweetbot 6 has been more reliable than the native Twitter app in the past week or so. + +### From Hand Notes +- [ ] 1st version release date (both on MacOS and iOS) +- [ ] Reviews of older versions +- [ ] More extensive search for Lists discourse +- [ ] App footprint size vs. the native app. -> 10.9MB vs. 115.8MB +- [ ] A bullet list summary of the API changes Twitter Blog post compared in a graphic(?) with any/all public statements/hints from Tapbots regarding specific feature additions relating to API changes. + +#### Possible Interview Questions +- [ ] Reasoning behind such investment in lists - 2021 vs. first year of development +- [ ] Notable events/correspondence from Twitter - both public and otherwise +- [ ] Stuff you feel Twitter may have been “inspired” by Tweetbot to include in the native app (like keyboard shortcuts.) +- [ ] Most unusual feature requests from users. +- - - - + +![](Tweetbot%206%20for%20iOS%20Review%20(Bear%20Notes)/Photo%20Feb%209,%202021%20at%20154202.jpg)![Account Settings | Tweetbot 5 vs Tweetbot 6](https://i.snap.as/7aSwOoGn.png) + +- [ ] Swiping to change the theme feature! God I can’t believe I forgot about that. +https://imgur.com/gallery/A1zbhLq + +- [x] Use Lists as Timeline +[My video](https://youtu.be/IO-ZSD-vymc) +[Lists Tips Support Page](https://tapbots.com/support/tweetbot6/tips/list.php) + +- [ ] ![All Tweetbot Themes (Horizontal)](https://i.snap.as/FzUKdQPX.png) +![](Tweetbot%206%20for%20iOS%20Review%20(Bear%20Notes)/Photo%20Feb%2010,%202021%20at%20151052.jpg) + +## Competition +![](Tweetbot%206%20for%20iOS%20Review%20(Bear%20Notes)/Photo%20Feb%2011,%202021%20at%20182421.jpg) +![Twitter Client Poll - Testflight Releases on Telegram](https://i.snap.as/RFFnqYLS.jpeg) ([March 4th, 2020](https://t.me/TFReleases/3049)) + + +#ios #tb6 \ No newline at end of file diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 6 for iOS Review (Bear Notes)/Photo Feb 10, 2021 at 151052.jpg b/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 6 for iOS Review (Bear Notes)/Photo Feb 10, 2021 at 151052.jpg new file mode 100644 index 00000000..8616a067 Binary files /dev/null and b/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 6 for iOS Review (Bear Notes)/Photo Feb 10, 2021 at 151052.jpg differ diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 6 for iOS Review (Bear Notes)/Photo Feb 11, 2021 at 182421.jpg b/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 6 for iOS Review (Bear Notes)/Photo Feb 11, 2021 at 182421.jpg new file mode 100644 index 00000000..5865ddb7 Binary files /dev/null and b/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 6 for iOS Review (Bear Notes)/Photo Feb 11, 2021 at 182421.jpg differ diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 6 for iOS Review (Bear Notes)/Photo Feb 9, 2021 at 154202.jpg b/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 6 for iOS Review (Bear Notes)/Photo Feb 9, 2021 at 154202.jpg new file mode 100644 index 00000000..1c9f6326 Binary files /dev/null and b/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot 6 for iOS Review (Bear Notes)/Photo Feb 9, 2021 at 154202.jpg differ diff --git a/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot History.md b/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot History.md new file mode 100644 index 00000000..b8228915 --- /dev/null +++ b/notes/Bear Notes/Tweetbot 6 for iOS Review/Tweetbot History.md @@ -0,0 +1,8 @@ +# Tweetbot History +- [ ] [Tweetbot for iPhone Review - MacStories](https://www.macstories.net/news/tweetbot-for-iphone-review/) +* Tweetie - which would eventually be bought by Twitter and rebranded its official iOS client - [receiving an Apple Design Award](https://www.flickr.com/photos/apoltix/3614598843/) on June 9th, 2009. (Flickr) + +- [ ] [Tapbots and the State of Our Apps in iOS7 — Tapbots Blog](https://web.archive.org/web/20131017184722/http://tapbots.com/blog/business/tapbots-and-the-state-of-our-apps-in-ios7) + +- [ ] [Twitter To Developers: Enough With The Twitter Clients - MacStories](https://www.macstories.net/stories/twitter-to-developers-enough-with-the-twitter-clients/) +#tb6 \ No newline at end of file