Summary of a peer's active stories », embedded in user.stories_max_id and channel.stories_max_id and returned by stories.getPeerMaxIDs.
recentStory#711d692d flags:# live:flags.0?true max_id:flags.1?int = RecentStory;
| Name | Type | Description |
|---|---|---|
| flags | # | Flags, see TL conditional fields |
| live | flags.0?true | Whether the peer is currently broadcasting a live story ». |
| max_id | flags.1?int | If live is set, ID of the peer's active live story »; otherwise, ID of the peer's maximum active story. |
Telegram users and channels can easily post and view stories through the API.
Indicates info about a certain user.
Unless specified otherwise, when updating the local peer database, all fields from the newly received constructor take priority over the old constructor cached locally (including by removing fields that aren't set in the new constructor).
See here » for an implementation of the logic to use when updating the local user peer database.
Channel/supergroup info
When updating the local peer database, all fields from the newly received constructor take priority over the old constructor cached locally (including by removing fields that aren't set in the new constructor).
The only exception to the above rule is when the min flag is set, in which case only the following fields must be applied over any locally stored version:
titlemegagroupcolorphotousernameusernameshas_geonoforwardsemoji_statushas_linkslow_mode_enabledscamfakegigagroupforumlevelrestrictedrestriction_reasonjoin_to_sendjoin_requestis_verifieddefault_banned_rightssignature_profilesautotranslationbroadcast_messages_allowedmonoforumforum_tabslinked_monoforum_idsend_paid_messages_starsbot_verification_iconSee here » for an implementation of the logic to use when updating the local channel peer database.
Get compact active story summaries » for a set of peers.