ekcom / rbot Goto Github PK

Server time cannot be used to schedule reminder times because the server may be in a different time zone. Currently, all reminder times are converted to Central time (frankly, because that is my time zone). Different timezone options should be implemented.

The command could be Hey RBot, change timezone to X and it would check if the timezone is valid and then store in database.
We then need to pull that info and use it in setCronAlarm.js

Allow a group member to be moderator and be the only one who can configure the Reminder Bot. This could reduce spam from other users. The command could be Rbot, take control and Rbot, release control

Currently, all messages are taken toLowerCase() and returned as query in recieveMessage. When setting the reminder message, though, capitalization should remain intact.
We must make sure that if we do not make query lowercase beforehand, we do that before passing to other functions (like setTimeOrDay).

To reduce the setup process, a step-by-step /setup route could be created to input BOT_ID and GROUP_ID. This route could also be available after setup as a configuration GUI (in case a user doesn't want to chat with the bot directly in GroupMe).

Sufficient security measures would need to be taken to ensure not everyone can get to the /setup route, and to ensure that the BOT_ID and GROUP_ID tokens are safe. (Tokens could be encrypted into database.)

Enabling the user to input solely their access token would allow the app to configure the bot name, bot id, and bot avatar for them. This would also allow adding the bot to multiple groups and removing the bot from the group via messages.
The option to use BOT_ID and GROUP_ID instead could still be used.