Fix forward origin #30
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to the Telegram Bot API docs, the cases of the forward origins are as follows:
MessageOriginChannel: The message was originally sent to a channel chat.MessageOriginChat: The message was originally sent on behalf of a chat to a group chat.MessageOriginUser: The message was originally sent by a known user.MessageOriginHiddenUser: The message was originally sent by an unknown user.Testing with the actual bot API, I do get users, not the chat, for messages forwarded from a supergroup.
MessageOriginHiddenUseris determined by the user's settings, which are not exposed to the bot API.