Once a story is successfully uploaded, an updateStoryID will be returned, indicating the story ID (id) that was attributed to the story (like for messages, random_id indicates the random_id that was passed to stories.sendStory: this way, you can tell which story was assigned a specific id by checking which stories.sendStory call has the returned random_id).
Also, posting a story will emit an updateStory both for us, and for our subscribers/contacts (even if they have hidden our stories).
+Additionally, a message containing a messageMediaStory with the via_mention flag coming from the story poster will also be generated automatically if the poster mentions us in the story's caption.
A story may also be edited using stories.editStory.
stories.stories#5dd8c3c8 count:int stories:Vector<StoryItem> chats:Vector<Chat> users:Vector<User> = stories.Stories;
@@ -176,6 +177,17 @@ Use stories.getAllReadPeerStorie
Use stories.togglePeerStoriesHidden to hide the active stories of a specific peer, preventing them from being displayed on the action bar on the homescreen.
When the stories of a user are marked as hidden, the stories_hidden flag is set on the related user constructor, and they should only be visible on the action bar when opening the archive folder, by setting the hidden flag when calling stories.getAllStories, see here for more info.
Note that the archive folder is the peer folder used for archived chats: hidden stories are displayed there purely due to a UI implementation detail, not because they're actually added to the archive peer folder » or the story archive », which are different things.
+Sharing stories
+inputMediaStory#89fdd778 peer:InputPeer id:int = InputMedia;
+
+messageMediaStory#68cb6283 flags:# via_mention:flags.1?true peer:Peer id:int story:flags.0?StoryItem = MessageMedia;
+
+---functions---
+
+messages.sendMedia#72ccc23d flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true noforwards:flags.14?true update_stickersets_order:flags.15?true peer:InputPeer reply_to:flags.0?InputReplyTo media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int send_as:flags.13?InputPeer = Updates;
+Stories can be shared as messages to any chat by simply using messages.sendMedia, passing an inputMediaStory referencing the shared story.
+The story will be shared as a messageMediaStory, and should be displayed as a message forwarded from the poster of the story (even though messages.forwardMessages was not used an the fwd_from field of the message won't be set).
+A message containing a messageMediaStory with the via_mention flag coming from the story poster will also be generated automatically if the poster mentions us in the story's caption.
Fetching the viewer list
storyView#b0bdeac5 flags:# blocked:flags.0?true blocked_my_stories_from:flags.1?true user_id:long date:int reaction:flags.2?Reaction = StoryView;
stories.storyViewsList#46e9b9ec flags:# count:int reactions_count:int views:Vector<StoryView> users:Vector<User> next_offset:flags.0?string = stories.StoryViewsList;
diff --git a/data/web/corefork.telegram.org/constructor/messageMediaStory.html b/data/web/corefork.telegram.org/constructor/messageMediaStory.html
index 5eed964eee..80af847e56 100644
--- a/data/web/corefork.telegram.org/constructor/messageMediaStory.html
+++ b/data/web/corefork.telegram.org/constructor/messageMediaStory.html
@@ -4,38 +4,10 @@
messageMediaStory
-
+
-
+
@@ -70,7 +42,8 @@ int…">
messageMediaStory
-
+ Represents a forwarded story or a story mention.
+
-
Layer 164
@@ -101,27 +74,32 @@ int…">
via_mention
flags.1?true
-
+If set, indicates that this someone has mentioned us in this story (i.e. by tagging us in the description) or vice versa, we have mentioned the other peer (if the message is outgoing).
peer
Peer
-
+Peer that posted the story.
id
int
-
+Story ID
story
flags.0?StoryItem
-
+The story itself, if absent fetch it using stories.getStoriesByID and the peer/id parameters specified above.
Type
-
+
+Related pages
+stories.getStoriesByID
+Obtain full info about a set of stories by their IDs.
+Stories
+Telegram users and channels can easily post and view stories through the API.
diff --git a/data/web/corefork.telegram.org/constructor/webPageAttributeStory.html b/data/web/corefork.telegram.org/constructor/webPageAttributeStory.html
index 890ea664dc..bd7225d698 100644
--- a/data/web/corefork.telegram.org/constructor/webPageAttributeStory.html
+++ b/data/web/corefork.telegram.org/constructor/webPageAttributeStory.html
@@ -4,34 +4,10 @@
webPageAttributeStory
-
+
-
+
@@ -66,7 +42,8 @@ Story…">
webPageAttributeStory
-
+ Webpage preview of a Telegram story
+
-
Layer 164
@@ -107,7 +84,7 @@ Story…">
story
flags.0?StoryItem
-
+May contain the story, if not the story should be fetched when and if needed using stories.getStoriesByID with the above id and peer.
@@ -115,7 +92,9 @@ Story…">
Related pages
Stories
-Telegram users and channels can easily post and view stories through the API.
+Telegram users and channels can easily post and view stories through the API.
+stories.getStoriesByID
+Obtain full info about a set of stories by their IDs.
diff --git a/data/web/corefork.telegram.org/type/MessageMedia.html b/data/web/corefork.telegram.org/type/MessageMedia.html
index a7d4ad3ec6..d33e31d947 100644
--- a/data/web/corefork.telegram.org/type/MessageMedia.html
+++ b/data/web/corefork.telegram.org/type/MessageMedia.html
@@ -138,7 +138,7 @@
messageMediaStory
-
+Represents a forwarded story or a story mention.
diff --git a/data/web/corefork.telegram.org/type/WebPageAttribute.html b/data/web/corefork.telegram.org/type/WebPageAttribute.html
index 2186a64221..e62e367468 100644
--- a/data/web/corefork.telegram.org/type/WebPageAttribute.html
+++ b/data/web/corefork.telegram.org/type/WebPageAttribute.html
@@ -72,7 +72,7 @@
webPageAttributeStory
-
+Webpage preview of a Telegram story