You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But I don't want to push changes without the ability to test them, and currently no Telegram client supports marking a bot as administrator of a channel.
Now that all the major clients supports adding bots as channel administrators, this can be implemented. The Bot.send method should be fairly easy to fix, but I also want to add an API for the ones who just want to manage the channel.
This is because creating a bot instance just for sending a message to a channel, maybe in an big script, is just a waste of resources. So I designed this API:
The GroupChat object was removed, and a generic Chat object was introduced
instead of the old one. This object is used for private conversations, group
chats and channels, so the Message.chat attribute won't contain anymore the
User or the GroupChat object, but only the Chat one.
Also the API change introduced support for managing channels. Details of the
implementation are tracked on issue #7.
Yesterday Telegram added support for channels in the API, so this should be implemented in botogram.
But I don't want to push changes without the ability to test them, and currently no Telegram client supports marking a bot as administrator of a channel.Now that all the major clients supports adding bots as channel administrators, this can be implemented. The
Bot.send
method should be fairly easy to fix, but I also want to add an API for the ones who just want to manage the channel.This is because creating a bot instance just for sending a message to a channel, maybe in an big script, is just a waste of resources. So I designed this API:
botogram.channel
will return an instance ofbotogram.Chat
, so it won't trigger the initialization of the bot instance.The text was updated successfully, but these errors were encountered: