MSC4391: Simplified in-room bot commands

[Gnuxie]

Rendered

Signed-off-by: Gnuxie [email protected]

---

This MSC incorporates work from MSC4332

[tulir]

Implementation requirements:

• Client
• Bot

[tulir]

gomuks/gomuks#675 is mostly complete implementation of client and technically also bot, converted from MSC4332. It doesn't have full support for room/event IDs or unions yet, but mostly it should be there

It assumes most of my suggestions in other comments are applied. Specifically:

• command string instead of designator array
• "optional": true instead of "required": false
• primitive schemas nested in an object with "schema_type": "primitive"
• arrays only at top level and unions only at top level or in arrays)
• optionally: list of aliases, default_value for default values

[Gnuxie]

(all of these suggestions were up-streamed into the MSC)

[tulir]

Proper bot implementation: maunium/meowlnir#50

Both meowlnir and parts of gomuks use logic from mautrix/go#446 (gomuks web has its own typescript implementation, gomuks terminal uses mautrix-go)

[tulir]

As an alternative/extension to optional parameters, a default value might be useful. The /raw command in gomuks has {} as the default value for event JSON for example

Also, "optional": true might be nicer than "required": false to allow treating undefined as false

[Gnuxie]

I didn't include defaults at this stage because they can also be provided by partial commands and interactive prompts ie the way suggestions work in draupnir. I guess it might be ok if it's treated like a literal default.

[Gnuxie]

I'm a little bit hesitant to do so right now and am thinking of making a JSON RPC style response follow up MSC that can explore the prompts and partial commands before settling on how to do defaults.