So it can be standard across all clients

Reply to this note

Please Login to reply.

Discussion

standards for bot commands? why would there be a need for multiple bots if they all do the same thing?

Not multiple bits, but so damus, amethyst, snort, can all know how to display the commands interface

seems like a good way for clients to differentiate themselves. not everything needs to be a nip

How would the bot communicate to the client what the commands are? There should be a standard

give the bot a help command. GitHub docs. unless you mean autocomplete sort of functionality. then maybe. really I just think we need some other mechanism besides nips

How would the user know there's a help command?

make it easily explorable. much like many rest apis or decent cli tools. rest has a standard like hateoas. however that's a standard on top of rest which is on top of http. to me, nips should be lower level and we have something else for specific application use cases. I guess like bolts vs blips.