Check out the OIDC section of https://matrix.org/blog/2022/08/15/the-matrix-summer-special... for more details
- This requires that any time you want to be able to selectively grant a subset of your account's authority, it requires standardizing new scopes to do so if there aren't already some that are suitable
- If I'm not mistaken, only the application is able to define which OIDC scopes are requested, and if the application requests more access than you'd like to give it, your options are limited
- If I'm not mistaken, OIDC scopes can only be requested at authentication-time, so there's no way to grant additional access later on at runtime
To be clear, none of this is specific to Matrix; most webapps seem to work this way! I just happen to be of the opinion that most webapps have way more access than they need. :)
I've grown increasingly disillusioned with ACL-based permissions systems for distributed social applications like this. Matrix is very strongly oriented towards ACLs/user identity, and the result is that applications like this which could operate without access to much of my existing account data nevertheless run effectively as me and can thus do everything I can. That's super dangerous when I'm the admin of a few rooms, because e.g. granting another user admin privileges in a room is irrevocable.
There have been plenty of cases when I've wanted to try out a Matrix-based app, but every time I do that I'm handing over the keys to my account to the app, which may or may not be trustworthy. And the consequences of mistakenly trusting a malicious app are severe.