It would be ideal if we can configure via config.ini the commands the bot responds to.
Specifically, in normal primary channel communications certain keywords trigger lots of bot traffic. For example, if someone uses the word "messages" in any message, the bot responds with the most recent history of messages seen on the channel. This can be disruptive and unexpected, especially if the bot is configured to respond to the channel and not via DM.
Suggestion would be to make each command configurable via commenting out lines or giving a 'true' or 'false' option for the commands. Data Commands
It would be ideal if we can configure via config.ini the commands the bot responds to.
Specifically, in normal primary channel communications certain keywords trigger lots of bot traffic. For example, if someone uses the word "`messages`" in _any message_, the bot responds with the most recent history of messages seen on the channel. This can be disruptive and unexpected, especially if the bot is configured to respond to the channel and not via DM.
Suggestion would be to make each command configurable via commenting out lines or giving a 'true' or 'false' option for the commands. [Data Commands](https://github.com/SpudGunMan/meshing-around?tab=readme-ov-file#data-lookup)
<!-- github-sync-id:2851251473 -->
I was considering changing that command to history not messages but didn't want to make a hard change for everyone
you can disable store_forward_enabled and it removes the command?
I was considering changing that command to history not messages but didn't want to make a hard change for everyone
you can disable store_forward_enabled and it removes the command?
<!-- github-comment-id:2658089071 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
It would be ideal if we can configure via config.ini the commands the bot responds to.
Specifically, in normal primary channel communications certain keywords trigger lots of bot traffic. For example, if someone uses the word "
messages" in any message, the bot responds with the most recent history of messages seen on the channel. This can be disruptive and unexpected, especially if the bot is configured to respond to the channel and not via DM.Suggestion would be to make each command configurable via commenting out lines or giving a 'true' or 'false' option for the commands. Data Commands
I was considering changing that command to history not messages but didn't want to make a hard change for everyone
you can disable store_forward_enabled and it removes the command?
Yeah that's a good workaround.