diff --git a/data/web/corefork.telegram.org/api/stories.html b/data/web/corefork.telegram.org/api/stories.html index 2a7b3971fe..86015b0741 100644 --- a/data/web/corefork.telegram.org/api/stories.html +++ b/data/web/corefork.telegram.org/api/stories.html @@ -150,18 +150,18 @@ Note that if any of the conditions changes in the period between the call to stories.getPeerMaxIDs#535983c3 id:Vector<InputPeer> = Vector<int>;
Active stories of contacts and subscribed channels should be shown in the action bar of the homescreen.
Use stories.getAllStories to fetch the full list of active stories.
Optionally, the hidden
flag can be set to fetch the hidden stories to be shown in the archived tab.
Optionally, the hidden
flag can be set to fetch the hidden stories to be shown in the archived tab, instead of the main story list.
Pagination using this method is a bit different from usual: a state
string is used to maintain the pagination state.
next
or state
flags should be set: upon completion, a new state
string is returned and should be stored locally, associated either to the main or hidden story list (depending on the value of hidden
we passed); pass the locally stored state
to all future calls of the method. has_more
flag will be set: in this case, the client should re-call the method with the newly returned state
and the next
flag set to fetch a new state
and the remaining stories from the chosen story list; the process should be repeated until no more stories are available (no_more
will not be set). next
or state
flags should be set: upon completion of the RPC call, a new state
string is returned and should be stored locally, associated either to the main or hidden story list (depending on the value of hidden
we passed); pass the locally stored state
to all future calls of the method. has_more
flag will be set: in this case, the client should re-call the method with the newly returned state
and the next
flag set to fetch a new state
and the remaining stories from the chosen story list; the process should be repeated until no more stories are available (has_more
will not be set). Once the full story list is fetched, stories.allStories can be called with the stored state
without setting the next
flag to check for updates in an active story list: if no changes have occurred since our last call, stories.allStoriesNotModified is returned, otherwise stories.allStories is returned (possibly requiring further pagination as described above).
Changes to the active stories list are contained in the stories.allStories.peer_stories
field: this field contains a vector of peerStories constructors, one for each peer, containing the peer ID, the ID of the maximum read story (if any), and a list of StoryItem constructors of type:
state
set and next
not set)user#abb5f120 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true bot_attach_menu:flags.27?true premium:flags.28?true attach_menu_enabled:flags.29?true flags2:# bot_can_edit:flags2.1?true close_friend:flags2.2?true stories_hidden:flags2.3?true stories_unavailable:flags2.4?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string emoji_status:flags.30?EmojiStatus usernames:flags2.0?Vector<Username> stories_max_id:flags2.5?int = User;