External 3rd parties are unknown in some cases, and may try to leverage you in others.

So you have a stable 3rd party api for some very large features, and we have a internal highly fluid api for our stuff. 3rd parties can totally use that api you use, and do. But why make any representations or tie your velocity to all those 3rd parties for your main app.

You want these companies to inovate and improve while also tying them to often unmonitized ecosystems of 3rd parties you can't communicate with or priroitize well.

It's generally unsurprising to me that the api support breaks down this way. I actually think it's pretty disiungenuine to make a sold 3rd party api without it being monetized. That encourages people to build ecosystems on other peoples good will which. We've seen how that works time and again. Even worse when 3rd parties try and compete partly with the bread and butter of the api they're using.

The point is that saying there's no API is wrong. There is an API. Elon has chosen not to let developers outside of Twitter use it. It's clearly a political choice rather than a technical competence problem.