spec idea: bot comands listing

[AngeloFrangione]

Suggestion

Today (most of the) bots use ! to read commands from messages. It would be easier for people to do / (or even keep !) and get a list of available commands for the bots inside their clients.

Bots would have to register the commands to the client and server in some way.

The other problem this could solve is related to #1109 : messages that are targeted for bots are always public. If commands are registered only the targeted bot could get them (if not a passive command) But at least it could give the user the choice to not let it's bot read everything.

A real spec around bots would help a lot. I couldn't find any spec proposal including this suggestion.

[KitsuneRal]

I wouldn't conflate commands for clients (processed locally) with commands for bots (processed by the bot, usually deployed somewhere else). But I agree that making Matrix a better place for bot integration would be valuable. Registering commands with the client may help with autocompletion (somewhat similar to, but much simpler than, the language server protocol works in IDEs) and probably have other benefits. I don't think there's much use in registering commands on the server though - for one, the server is not even aware of message content in encrypted rooms.

All in all, good idea; MSCs are welcome.