Refactor !commands to use the Telegram command API

[hluaces]

Refactor !commands to use the Telegram command API

[hluaces]

pinging @oscarmlage

[oscarmlage]

Yep, I've thought about that at the beginning: just parse every msg vs telegram commands. One of the purposes of the bot (at the very beginning) was to be able to read all the messages (that's why they're being saved) and offer a kind of periodic "channel summary". I mean something like:

• Top of people talking
• Tagcloud
• Hot topics
• Commonly said words...

But you know, after all this time I had no time to summarize and people is most likely more happy with quotes feature than the other stuff so in the end we can discuss and get rid about the other features in order to have a more structured code (and, of course, privacy reasons, they are always worrying me).

[hluaces]

We can have both worlds if we want to:

1. Telegram commands so that we can benefit from the API, parsing and all the related goodies.
2. Channel data saving to create topics and clouds (which properly executed might be useful).

I think we can keep both. Later on, if needed, the "channel reading" can easily be turned off we we have the commands using the respective API.

[hluaces]

If that's OK with you I can prepare a PR so that the commands are moved to the API and the rest is kept in the same way (that is: saving messages as they are being saved now). I'd also add some deprecation notices on the ! commands so that users are asked to move to the / command form.

[oscarmlage]

If that's OK with you I can prepare a PR so that the commands are moved to the API and the rest is kept in the same way (that is: saving messages as they are being saved now). I'd also add some deprecation notices on the ! commands so that users are asked to move to the / command form.

Sure! it's perfectly fine. And if it's ok with you I'll wait for this PR to make a new release.