-
Notifications
You must be signed in to change notification settings - Fork 311
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Channel_post #37
Comments
And a second example ("/bottest test test")
|
just use @channel_name as chat_id. |
This works only for sending emails to channel that are public. But in this case you still don't get any messages back, because getUpdates searches for messages only in the section results/messages and not in the section results/channel_post. |
Hey @littleyoda thanks for raising the issue. Adding the example response here is very helpful so thanks for that too! Yeah this is something we could handle for sure, at the moment bot only cares about messages but this needs to be extended handle other types from getUpdates such as this one. I've never seen the entities object before, I'll have to take a bigger look into it If created a new branch over the next few days supporting this could download it and try it out? |
If you want to reproduce this kind of messages:
Of course, I will be happy to test every new source code. |
I did some work towards this there. It requires a good bit of code clean up but is working for me I added a "type" that you can check to see is it a channel post so you can handle it differently if required. I also added "chat_title" if that is useful. Example usage below
|
Just tested and it works fine. Perfect. Thanks |
Available in the V1.1.0 RC branch https://github.com/witnessmenow/Universal-Arduino-Telegram-Bot/tree/V1.1.0 |
Support for Channel_post would be great.
see https://core.telegram.org/bots/api-changelog#november-21-2016
An Example of the result-String:
The text was updated successfully, but these errors were encountered: