[flagged]
[deleted]
Tweetbot. April 2011 – January 2023
11–20 of 427 posts
Re: Tweetbot. April 2011 – January 2023
#12Re: Tweetbot. April 2011 – January 2023
#13Tweetbot was the only way I interacted with Twitter for years. I refuse to use the website and I refuse to download Twitter's app. When it was finally revealed that this move was intentional I deleted my Twitter account. I was mocked in high school for having a Twitter account (2008) and not a Facebook account. I remember "tweeting" from my flip/dumb-phone. I still don't have Facebook.
I don't regret being on Twitter but I am learning to live without it these days. There's something freeing about a cold turkey detox from that increasingly hostile social network.
Anyway, I'm just rambling at this point. RIP Tweetbot. Thank you for making Twitter usable. Eagerly awaiting Ivory.
Re: Tweetbot. April 2011 – January 2023
#14I have an old friend who is blind. The official Twitter client is a LOT less accessible than the one she was using. This change impacts her ability to use Twitter considerably.
And before you start with the "well, she's probably better off" -- she lives in a small rural town. Twitter and Facebook and the like are one of her few connections to a larger world.
Re: Tweetbot. April 2011 – January 2023
#15And so ends my daily use of Twitter. I still haven't been able to get into Mastodon in the same way, but if Ivory is as good as Tweetbot was it might bring me around.
It is as good as Tweetbot. Using Ivory makes most of the "UX issues" of Mastodon go away ... almost.
Re: Tweetbot. April 2011 – January 2023
#16The question I have with this move is why didn't Twitter just force advertising as part of their API for third party clients? Just change the TOS for using the API so if they didn't show advertising they would be cut off. What am I missing?
The list of unforced errors is insane. Remember when pg was banned from Twitter for mentioning that he had a link to Mastodon on his website? https://finance.yahoo.com/news/twitter-suspends-account-paul...
Re: Tweetbot. April 2011 – January 2023
#17Note this kind of thing happens all the time. VRChat instituted EAC to prevent client modifications late last year. Hundreds of developers and tens of thousands of users all had their mods stop working overnight. Projects that dozens of devs had poured countless hours into became instantly and utterly worthless. It’s insane that this is what the internet has become.
Re: Tweetbot. April 2011 – January 2023
#18The question I have with this move is why didn't Twitter just force advertising as part of their API for third party clients? Just change the TOS for using the API so if they didn't show advertising they would be cut off. What am I missing?
This was probably easier and the decision was probably made on a whim - no time plan and execute a transition like you're suggesting. I think this theory is supported by the fact that API access was cut with no notice, the ToS was only changed after-the-fact, and some smaller apps - like Twitterific for MacOS - were initially missed.
Re: Tweetbot. April 2011 – January 2023
#19The question I have with this move is why didn't Twitter just force advertising as part of their API for third party clients? Just change the TOS for using the API so if they didn't show advertising they would be cut off. What am I missing?
“Starting Feb 1st using a third part client will require Twitter Blue.”
That’s all it would have taken. Probably would have made a huge increase in subscribers too.
This is 100% a control move. He wants full control over how everyone experiences Twitter (not sure why). So this was pulled.
Of course you can NEVER go back from this move.
Re: Tweetbot. April 2011 – January 2023
#20A great opportunity Mastodon wouldn't otherwise get.
Thanks Elon.