lukaswagner / moderatelyusefulbot Goto Github PK

add a basic readme

the commands shouldn't be spammable. these cooldowns should be chat-specific.

print the logs to file and to screen. in order to do this, a logging helper should be used (see this)

remove all user data (telegram ids, playlist etc) from the config file. thus, no private information is shared when adding new functionality.

add text-to-speech capability, maybe as an inline function (requiring #33 to be implemented)

calcualte some stats for the chat, like who's msot active and most active times

just grab a random image from google images related to the user's input

store a dict<string, string> per command, which can be accessed by the action for command customization

normal bots shouldn't be able to stop the whole application, since this may affect other bots. add a management bot which provides options to start/exit/restart/edit other bots and their commands.

some commands shouldn't be run in all chats. thus, a whitelist should be defined per bot, with commands having an optional requireWhitelist property.

These are chosen randomly currently. Since this project isn't meant to be used as lib at the moment, everything should be made internal.

Grab a random collection of a chat's images from the last month and create a beautiful collage or even a short video from it.

currently, multiple names for a command require adding the command multiple times.

idea: add command state containing bot, message, settings etc, everything that could be used by delegate

instead of having config and credentials in one file, use two different files - thus, the config files may be added to the repo

• exit
• restart?
• log
• set adminOnly

split up huge schema tree into smaller, named type definitions

print all commands available to user in current chat

creating a new token by hand every hour isn't very usable. the token should be refreshed automatically.

Show more Spotify stats when invoked with argument "more" or "full"

Ideas: total stats, time by user, mainstream / popularity score

support inline functions

add support for timed commands which send a message periodically to a given channel

Don't fetch the complete playlist, only the number of songs (or is there a better metric? Last updated time?). The track list and the calculated results should be stored for faster replies. A "refresh" arguments should be available.

allow request of single data blocks with arguments "count", "duration", "popularity". argument "full" should still return all blocks.

see https://msdn.microsoft.com/de-de/library/ms162371(v=vs.110).aspx

include time, author id and name

Check if multiple telegram accounts can be used with the lib.

the cached spotify playlist shouldn't be stored as a static var. to solve this, a data member could be added to the bot class.

If the bot is set to receive all messages (not just commands), all these messages are logged, even if they are ignored by the bot. This creates a lot of bloat in the log file. Additionally, this doesn't feel right privacy-wise.

For better management of functions and their commands, a simple command class should be implemented.