Hey Dekkonot, Thanks again for posting this, and also some of your recent responses on Account Session Protection. We discussed this internally and wanted to give you a combined response on both for some more transparency.
To start, I want to reassure you that we will not seek to break existing workflows of Rojo such as the one you point out without an alternative endpoint, deprecation plan, and ample heads-up time to ensure no interruption to tooling developers or their users. That means we’ll be careful on which endpoints we turn on the “Account Session Protection” side-effects such that it will not impede workflows of tooling such as Rojo.
We also acknowledge your request here to put this on Open Cloud so that you can use a scoped token rather than a full session token. We will provide an alternative solution on Open Cloud at some point in the future, though we are still figuring out exactly what this solution will look like, so unfortunately I can’t give you a timeline here yet.
We’ll keep this thread open for comments. Thanks again!