alvarogzp / telegram-bot-framework Goto Github PK

In a private repo or something similar, as it contain sensitive information.

Example: bot.api.telegram.TelegramBotApiException: Message is too long

It is being sent to admin, and the command does nothing to the user. Maybe is more appropriate to send also to the chat, to make them know an error has happened.

Take care to only send this kind of messages in response to commands or actions that the user expect a response from the bot, to avoid the bot spamming errors when it should be quiet.

To refresh bot_info

For example, in /poles ranking show /poles_recent.

That is, to use /messages message_id syntax instead of /messages show message_id, or to add buttons to view a message.

To avoid having to modify it for every new param that is used

Either by showing them separately, or by mixing with poles creating a scoring system where poles count more than subpoles, etc.

With a command maybe? 😄

Every "from" User info should be persisted so that later user_ids can be mapped to username and/or first_name last_name.

For example, hashtags store user_ids.

By mentioning them

So that some people can do more things than others

For example, when there are more than 2000 messages, remove the 1000 older.
If possible, do it in batches to avoid writing too much to the disk.

Move folder when a group is migrated to a supergroup, to maintain stats and data

That is, to broadcast poles as messages to chats, controlled by a feature flag.

Using the Config class

Instead, recover and request again

That is, the last_message_timestamp, to avoid thinking at entering again that it is a pole.
Maybe at entering also, to avoid not being notified on leave?

To ease making the bot work

To avoid sending too long messages, or api errors.

Proposal: 100 items max

example: <a href="telegram.me/username">username</a>

Yo, can you write a bot multilanguage? Some people have a bad habit. Some people want to read things in their language... xD

If a user deletes its pole message and then requests to show it by using /poles last, bot will throw an exception because the message replied to no longer exists.

One option is to disable completely replying to pole messages, and user messages in general (except for bot commands).

Currently, on DST change it will start failing

• Uptime
• Version

UserFormatter by default mentions the user if (s)he has a username.
This can be annoying for some users.

Not being recognized as such when they are after the first message

As it is not the same to send a message a minute later (while the bot reboots) or a day later (after a big problem).

Maybe, if the time is short, pending actions could be threated like normal actions.

Example: @user_name

It is being parse as markdown, so the mention does not work

From code comment:

            # FIXME this does not work as expected
            # FIXME it only resets the current chat status,
            # FIXME and only if this action is executed (eg. it is is a normal message)