Info about a message sent to (received from) another user
updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;| Name | Type | Description |
|---|---|---|
| flags | # | Flags, see TL conditional fields |
| out | flags.1?true | Whether the message is outgoing |
| mentioned | flags.4?true | Whether we were mentioned in the message |
| media_unread | flags.5?true | Whether there are some unread mentions in this message |
| silent | flags.13?true | If true, the message is a silent message, no notifications should be triggered |
| id | int | The message ID |
| user_id | long | The ID of the sender (if outgoing will be the ID of the destination) of the message |
| message | string | The message |
| pts | int | PTS |
| pts_count | int | PTS count |
| date | int | date |
| fwd_from | flags.2?MessageFwdHeader | Info about a forwarded message |
| via_bot_id | flags.11?long | Info about the inline bot used to generate this message |
| reply_to | flags.3?MessageReplyHeader | Reply and thread information |
| entities | flags.7?Vector<MessageEntity> | Entities for styled text |
| ttl_period | flags.25?int | Time To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well. |
How to subscribe to updates and handle them properly.
Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.
How to create styled text with message entities