I would like to add one thing and fix one already mentioned point.

In point eight, the author says:

“Fix Tweetdeck. Fix Twitter for Android. Fix Twitter for OSX. Twitter for OSX still has a hard limit on how many blocks it can apply because they didn’t bother updating the API call when they switched to paged requests. It also crashes a lot if you’re receiving a lot of notifications. Tweetdeck doesn’t use server side mutes. The ability to mute users originated from Tweetdeck prior to Twitter buying it. They then added this functionality to Twitter itself, but never updated the client to store these mutes server side. It also doesn’t process incoming block events, so if you block on a different client, an existing running Tweetdeck application won’t see it and remove the tweets from your timeline or notifications. This is actually a problem that exists with most clients, but I like picking on Tweetdeck because the project manager is too busy adding bullshit like Twitter Teams to bother with basic bug fixes.”

I don’t disagree with this is the least. Twitter’s first party apps are not good. Their third party clients are, in general, far better. If Twitter is going to insist on handicapping third party clients, then they should have killer first part apps.

Specifically, recently their iOS clients have gone to shit. On iPad, instead of properly implementing size classes, Twitter made an app that scales poorly and displays more white space than app. On Android that might be tolerated, but this is iOS. The iPhone app is okay, but since it’s a universal app, it needs to be better.

Relating to the idea that Twitter should fix their first party apps is that Twitter needs to implement timeline syncing across their apps. This is arguably the number one feature of third party clients, allowing me to start reading Twitter on my Mac, pick up on my iPhone, and finish on my iPad, all without having to search for where I left off.

I use iCloud to sync my position in Tweetbot, which only works if you use Tweetbot everywhere and only on Apple platforms, but syncing engines like Tweetmarker have existed for years. Twitter could just as easily implement Tweetmarker or their own first party syncing solution. I think this would actually increase Twitter interaction, because users wouldn’t have to fear missing tweets, making Twitter more manageable.