visperi / glasnostbot Goto Github PK

If the config files get new fields, it can be burdensome to migrate existing files to new structure. Add some kind of tool for merging existing configuration files with new ones without touching modified variables.

One way to achieve this is to make a custom class handling the configuration files. This could possibly also give nice ways for more granular configuration file handling.

The markdown algorithm does not work correctly and starting position is incorrect in nested markdown text.

For example, this is supposed to be bolded and underlined text:

Add native support for fetching and forwarding messages from regular channels. Currently this needs to be done manually by modifying method on_update in telegram_cog where only channel posts are parsed by default.

Possibly add boolean switches for accepting messages from different kind of channels in the configuration?

Not probably a very big issue though. Boundaries for nested styles could probably be checked and then applied, or the markdown algorithm coul be approached in more granular OOP style.

Add rate limiting threshold and implementation for Discord messages to prevent rate limit errors. This can become a problem if the amoount of Discord channels grows big enough. The messages should then be rather delivered in batches.

Update the showcase images in the main Readme file.

Discord has character limit of 2000 characters for plain text messages, which is shorter than in Telegram (even more shorter if one has Telegram premium). Add support for longer messages by e.g. using embeds instead, or perhaps splitting the messages into multiple ones.

Telegram messages are sometimes quietly ignored instead of forwarded to Discord. No log messages or anything.

Hyperlinks don't work and are sent instead as a bare text. Add a way to extract the link and text, and then format them in a suitable way.

Title. Following example is simple one but works in the same principle for longer messages too:

Maybe something to do with how the emojis are encoded while parsing through the messages in python, since they show correctly in both Telegram and Discord?

Edit: Confirmed to be an issue with Telegram calculating MessageEntity offsets using UTF-16 code units instead of Python default UTF-8 code points. The code point encoding must be taken into account when applying markdowns and offsets to messages received from Telegram API.

Telegram messages can have attachments and so do Discord messages. Add support for different kind of attachments. At least following attachment types should be sufficient:

• video
• audio
• images

Add also possibility of removal of attachments if possible.