Message drafts in Telegram allow syncing the text typed into message fields between devices.
-Drafts are represented by the DraftMessage constructors. -The parameters of the peer-specific draft should be used as defaults when composing a message to be sent to a certain peer (in the case of media, the same draft should still be used as base, the message will become the caption). -If the user exits the app before sending the message, the message should be saved as a draft:
-Drafts can be saved using the messages.saveDraft method.
-New drafts are automatically sent to all devices via updateDraftMessage updates.
-Dialog objects fetched via the API also contain the draft associated with the dialog.
-Drafts can be cleared by setting the clear_draft flag when sending messages or media using messages.sendMessage, messages.sendMedia, messages.sendMultiMedia, messages.sendInlineBotResult and similar or manually by passing empty values to messages.saveDraft.
Whether messages forwarded from this user will be anonymous
-inputPrivacyKeyForwards#a4dd4c08 = InputPrivacyKey;This constructor does not require any parameters.
-Info on successfully sent message and on changes links.
-Constructor schema is available as of layer 24. Switch ยป| Name | -Type | -Description | -
|---|---|---|
| id | -int | -Message ID | -
| date | -int | -Date of sending | -
| pts | -int | -New value of pts parameter of a current state | -
| seq | -int | -New value of seq parameter of a current state | -
| links | -Vector<contacts.Link> | -List of changes links | -
Channel participant
-channelParticipant#c00c07c0 user_id:long date:int = ChannelParticipant;
-channelParticipantSelf#35a8bfa7 flags:# via_request:flags.0?true user_id:long inviter_id:long date:int = ChannelParticipant;
-channelParticipantCreator#2fe601d3 flags:# user_id:long admin_rights:ChatAdminRights rank:flags.0?string = ChannelParticipant;
-channelParticipantAdmin#34c3bb53 flags:# can_edit:flags.0?true self:flags.1?true user_id:long inviter_id:flags.1?long promoted_by:long date:int admin_rights:ChatAdminRights rank:flags.2?string = ChannelParticipant;
-channelParticipantBanned#6df8014e flags:# left:flags.0?true peer:Peer kicked_by:long date:int banned_rights:ChatBannedRights = ChannelParticipant;
-channelParticipantLeft#1b03f006 peer:Peer = ChannelParticipant;| Constructor | -Description | -
|---|---|
| channelParticipant | -Channel/supergroup participant | -
| channelParticipantSelf | -Myself | -
| channelParticipantCreator | -Channel/supergroup creator | -
| channelParticipantAdmin | -Admin | -
| channelParticipantBanned | -Banned/kicked user | -
| channelParticipantLeft | -A participant that left the channel/supergroup | -
The banned rights of a user were changed
-channelAdminLogEventActionParticipantToggleBan#e6d83d7e prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;| Name | -Type | -Description | -
|---|---|---|
| prev_participant | -ChannelParticipant | -Old banned rights of user | -
| new_participant | -ChannelParticipant | -New banned rights of user | -
How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.