Specific to your tooling in that Twitter will be the host of users’ media, and wouldn’t want to water that down by providing public API access to users’ media?
I’m pretty excited about the prospects of Twitter Studio, and others are as well. Part of my excitement is associated with being able to build some handy scripts based on the media hosting you all will provide. For example, I might grab a URL out of my studio programatically. I don’t know that I fully understand the motivations to keep an endpoint like this closed off, as from my perspective, it would encourage users to embrace Twitter Studio further.
I’m very interested in your in-the-loop perspective, and am not sure that I fully understand it. I really appreciate the straightforward, honest opinion as well!