Thanks, Twitter ... 

On June 19th Twitter will shutter its streaming API, causing issues for third-party app developers. The API, or application programming interface, refreshes timelines and sends push notifications and core features to any Twitter service. Twitter will provide a new Account Activity API to replace it, but little is known about the new API and time is running out for developers to be granted access. Without access, they can’t implement it in their apps fast enough to avoid an interruption in service.

(Read more at Mobile Syrup)

Twitter’s been slowly making stupid decisions, that are most likely designed to drive people to their web interface, but have the impact of killing off their 3rd party ecosystem (or, at least, a lot of the unique apps that have made Twitter useful).

I have to imagine that this isn’t a big deal at Twitter HQ (though I bet a lot of their developers use the very tools that are going to be nerfed) because the way a lot of long-time users of Twitter use Twitter is not how Twitter wants to be used. Or, put another way: the ordered, non-algorithmic timeline with few (or no) ads for people who want to do more than follow and mention celebrities isn’t where Twitter wants to be.

It seems like Twitter could pretty easily make it a requirement to use their APIs that developers include ads, include polls, include whatever Twitter thinks makes Twitter unique.

But, honestly, it is all fine for Twitter to do what they think is right. I think it’s dumb, and short-sighted, and risks the same sort of market correction that Snap took when they messed with their (admittedly obtuse) user interface. But Twitter gon’ Twitter.

It just means I need to spend more time at micro.blog, which is really designed far more to be what Twitter used to be. I should really put that on my todo list, so I can make it a habit. I’m guessing people on micro.blog will enjoy reading my in the moment Celtics thoughts as much as anybody on Twitter.