MSC4049: Sending events as a server or room

[turt2live]

Rendered

Dependencies:

• MSC4047: Send Keys
  • Depends on MSC4046

[turt2live]

seemingly I forgot to mention m.room.create: it needs to be sent by a user ID, not a server (or room, not that it can...) because it implies that servers create rooms when it's actually users who do. I don't think anything overly breaks if we were to allow it, but the semantic reasons justify banning (imo).

[andrewzhurov]

Sending as a "Room" sounds confusing to me. "Room" is a rather unfortunate name for a Matrix Event Graph to begin with.

What the described use-case wants, it seems, is to publish events from some sort of role identifier (e.g., Acme corp) that may be collectively hold. E.g., top-level officers are authorized to publish announcements on behalf of Acme corp id.

A way to manage such id in Self-Sovereign Identifier space is to e.g. use a MultiSig Autonomous Identifier (AID) of KERI.
Basically, it states keys that need to sign in order for event to be deemed authentic.
Given we can have Profile Rooms #1769, such room is naturally a MultiSig AID, that could be used to manage authorized keys and add authenticity to actions on behalf of this ID. E.g., create an announcement event with one of the authorized keys and link to it from Profile Room to add authenticity. Or simply have a dedicated Announcements Room (with MultiSig requirement on it's events), a kind of Announcer ID of Acme corp.