Twitter Cripples Third-Party Clients…Again

Twitter Cripples Third-Party Clients…Again:

A bird flying in a graveyard.

Photo by malsawn on Pixabay
Twitter has spent years fighting the third-party clients the company once encouraged. Despite protests from developers and users (see “Twitter App Developers Band Together to Fight API Changes,” 21 May 2018), Twitter has gone ahead with its latest restrictions on third-party clients. Clients can no longer live-stream tweets or send push notifications. If you want those features, you now must turn to Twitter’s official apps. But while it’s cutting out outside developers, Twitter has a bad record of maintaining its own clients, having killed off its own Mac app months ago (see “Three Alternatives to Twitter’s Now-Defunct Mac App,” 2 March 2018). Twitter’s Rob Johnson shared an internal email on Twitter, along with other comments intended to placate users, but based on Michael Tsai’s sampling of responses, Johnson’s explanations fell flat.

Read original article

(Via TidBITS)

Twitter has its reasons. We don’t know what they are. Their business plan should account for the bad press, damage to their reputation for some recent decisions, and “influencers” who will abandon the platform.

I look forward to reading the almost certainly in process analyses of Twitter’s decisions.

Also on:

i forget how much i like Sloop John B by the Beach Boys until i hear it
Also on:

True Fear

Similarly, when the First Anglo-Dutch War ended in 1654, the Dutch Republic forgot to include the Isles of Scilly in the Treaty of Westminster, so the Dutch and the Scillonians remained pointlessly but arguably at war for 332 years, until they signed a symbolic peace in 1986.
The Dutch ambassador said, “It must have been awful to know we could have attacked at any moment.”

Futility Closet

Also on: