diff --git a/data/web/corefork.telegram.org/api/search.html b/data/web/corefork.telegram.org/api/search.html
index d9fd5001a6..9e3b790c0b 100644
--- a/data/web/corefork.telegram.org/api/search.html
+++ b/data/web/corefork.telegram.org/api/search.html
@@ -133,8 +133,11 @@ For example, when displaying the chat photo gallery, we could display a A special channels.searchPosts method is available to globally search for posts from public channels (including those we aren't a member of), containing a specific hashtag (which should be passed in the ph
+Global hashtag search
----functions---
-channels.searchPosts#d19f987b hashtag:string offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;
hashtag
field without the #
).
Special channels.searchPosts and stories.searchPosts methods are available to globally search for posts from public channels (including those we aren't a member of) and stories from public users, channels and groups (including non-contacts and peers we've never seen before), containing a specific hashtag (which should be passed in the hashtag
field without the #
).
See here » for more info on global search for stories.
diff --git a/data/web/corefork.telegram.org/api/stories.html b/data/web/corefork.telegram.org/api/stories.html index adba100d70..732cb6c60f 100644 --- a/data/web/corefork.telegram.org/api/stories.html +++ b/data/web/corefork.telegram.org/api/stories.html @@ -246,6 +246,18 @@ When the stories of a user are marked as hidden, thestories_hidden
Stories may be reposted by using stories.sendStory, populating the fwd_from_story
field with the original story ID and the fwd_from_id
with the peer that posted the original story.
The user may modify the story (for example by overlaying a round video reaction on top of the media); either way, the modified or the original media must be passed to the media
field as usual, and the fwd_modified
flag must be set if the media was modified.
Reposted stories will have the storyItem set and populated with a storyFwdHeader constructor, containing info about the original story.
+foundStory#e87acbc0 peer:Peer story:StoryItem = FoundStory;
+
+stories.foundStories#e2de7737 flags:# count:int stories:Vector<FoundStory> next_offset:flags.0?string chats:Vector<Chat> users:Vector<User> = stories.FoundStories;
+
+---functions---
+
+stories.searchPosts#6cea116a flags:# hashtag:flags.0?string area:flags.1?MediaArea offset:string limit:int = stories.FoundStories;
+stories.searchPosts may be used to globally search for stories from all users (even non-contacts and other peers we've never seen before) using either a hashtag passed to hashtag
(without the #
) or a location tag passed to area
.
Global search should be automatically triggered when clicking on a hashtag in the description of a story, or when clicking on a location tag.
+Either hashtag
or area
must always be set when invoking the method, offset
must initially be an empty string.
+Paginate the results by re-calling the method, passing to offset
the stories.foundStories.next_offset
field returned by the previous call.
inputReportReasonSpam#58dbcab8 = ReportReason;
inputReportReasonViolence#1e22c78d = ReportReason;
@@ -315,6 +327,7 @@ Note that this should be done transparently in a map UI, not in the usual inline
Clients may only re-use existing mediaAreaVenues when repositioning a pre-existing location tag when editing a story; use inputMediaAreaVenue when posting a new story or adding a new location tag to an existing story.
+Global story search » should be automatically triggered when clicking on a location, passing the mediaAreaGeoPoint/mediaAreaVenue to stories.searchPosts.
Reactions
Schema:
reactionEmoji#1b2286b8 emoticon:string = Reaction;