This is very cool, although every additional use case for Matrix makes me wish there were ways to grant access to a subset of my account.
Worst case scenario logging into a Mastodon client is that it wrecks my microblogging data. Worst case scenario logging into a Matrix microblogging app is that it wrecks my microblogging data and drops my admin privileges on all of my Matrix chatrooms.
We've had this idea for a really long time e.g https://github.com/matrix-org/matrix-doc/issues/531 and is something I would like to tinker with in Dendrite for sure. Typed rooms helps categorise but doesn't allow control over a subset of your account.
>Typed rooms helps categorise but doesn't allow control over a subset of your account.
Sure, but they could in the future, right? Couldn't a homeserver in theory generate a more restricted credential for which it would reject e.g. "PUT /rooms/<roomid>/send/..." requests after checking the room type?
None of the machinery around that exists now, but it feels like it could be done.
(FWIW, I did write MSC1840 with this use case in mind.)
Worst case scenario logging into a Mastodon client is that it wrecks my microblogging data. Worst case scenario logging into a Matrix microblogging app is that it wrecks my microblogging data and drops my admin privileges on all of my Matrix chatrooms.
OAuth scope by room type, maybe? https://github.com/matrix-org/matrix-doc/pull/1840