OpenSource/telegram-crawler
OpenSource/telegram-crawler
1
0
Fork 0
mirror of https://github.com/MarshalX/telegram-crawler.git synced 2024-11-29 11:43:05 +01:00
Code Issues Projects Releases Packages Wiki Activity

Update content of files

Browse source
This commit is contained in:
GitHub Action 2023-12-03 15:27:22 +00:00
parent 11778019c2
commit 6d54bd5e89
6 changed files with 38 additions and 69 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
data/web/corefork.telegram.org/api/layers.html
View file

@ -121,8 +121,8 @@
<li>Added <a href="/constructor/updateStoryID">updateStoryID</a> - A story was successfully uploaded.</li>
<li>Added <a href="/constructor/exportedStoryLink">exportedStoryLink</a> - Represents a <a href="/api/stories#story-links">story deep link</a>.</li>
<li>Added <a href="/constructor/inputMediaStory">inputMediaStory</a> - Forwarded story</li>
<li>Added <a href="/constructor/messageMediaStory">messageMediaStory</a> - </li>
<li>Added <a href="/constructor/webPageAttributeStory">webPageAttributeStory</a> - </li>
<li>Added <a href="/constructor/messageMediaStory">messageMediaStory</a> - Represents a forwarded <a href="/api/stories">story</a> or a story mention.</li>
<li>Added <a href="/constructor/webPageAttributeStory">webPageAttributeStory</a> - Webpage preview of a Telegram story</li>
<li>Added <a href="/constructor/storiesStealthMode">storiesStealthMode</a> - Information about the current <a href="/api/stories#stealth-mode">stealth mode</a> session.</li>
<li>Added <a href="/constructor/updateStoriesStealthMode">updateStoriesStealthMode</a> - Indicates that <a href="/api/stories#stealth-mode">stories stealth mode</a> was activated.</li>
<li>Added <a href="/constructor/mediaAreaCoordinates">mediaAreaCoordinates</a> - Coordinates and size of a clicable rectangular area on top of a story.</li>

12
data/web/corefork.telegram.org/api/stories.html
View file

@ -95,6 +95,7 @@ Note that if any of the conditions changes in the period between the call to <a
</ul>
<p>Once a story is successfully uploaded, an <a href="/constructor/updateStoryID">updateStoryID</a> will be returned, indicating the story ID (<code>id</code>) that was attributed to the story (like for messages, <code>random_id</code> indicates the <code>random_id</code> that was passed to <a href="/method/stories.sendStory">stories.sendStory</a>: this way, you can tell which story was assigned a specific <code>id</code> by checking which <a href="/method/stories.sendStory">stories.sendStory</a> call has the returned <code>random_id</code>). </p>
<p>Also, posting a story will emit an <a href="/constructor/updateStory">updateStory</a> both for us, and for our subscribers/contacts (even if they have <a href="#hiding-stories-of-other-users">hidden</a> our stories). </p>
<p>Additionally, a message containing a <a href="/constructor/messageMediaStory">messageMediaStory</a> with the <code>via_mention</code> flag coming from the story poster will also be generated automatically if the poster mentions us in the story's caption. </p>
<p>A story may also be edited using <a href="/method/stories.editStory">stories.editStory</a>. </p>
<h4><a class="anchor" href="#pinned-or-archived-stories" id="pinned-or-archived-stories" name="pinned-or-archived-stories"><i class="anchor-icon"></i></a>Pinned or archived stories</h4>
<pre><code><a href='/constructor/stories.stories'>stories.stories</a>#5dd8c3c8 count:<a href='/type/int'>int</a> stories:<a href='/type/Vector%20t'>Vector</a>&lt;<a href='/type/StoryItem'>StoryItem</a>&gt; chats:<a href='/type/Vector%20t'>Vector</a>&lt;<a href='/type/Chat'>Chat</a>&gt; users:<a href='/type/Vector%20t'>Vector</a>&lt;<a href='/type/User'>User</a>&gt; = <a href='/type/stories.Stories'>stories.Stories</a>;
@ -176,6 +177,17 @@ Use <a href="/method/stories.getAllReadPeerStories">stories.getAllReadPeerStorie
<p>Use <a href="/method/stories.toggleAllStoriesHidden">stories.togglePeerStoriesHidden</a> to hide the active stories of a specific peer, preventing them from being displayed on the action bar on the homescreen.<br>
When the stories of a user are marked as hidden, the <code>stories_hidden</code> flag is set on the related <a href="/constructor/user">user</a> constructor, and they should only be visible on the action bar when opening the <a href="/api/folders#peer-folders">archive folder</a>, by setting the <code>hidden</code> flag when calling <a href="/method/stories.getAllStories">stories.getAllStories</a>, see <a href="#watching-stories">here</a> for more info. </p>
<p>Note that the <a href="/api/folders#peer-folders">archive folder is the peer folder used for archived chats</a>: hidden stories are displayed there purely due to a UI implementation detail, not because they're actually added to the <a href="/api/folders#peer-folders">archive peer folder »</a> or the <a href="#pinned-or-archived-stories">story archive »</a>, which are different things. </p>
<h3><a class="anchor" href="#sharing-stories" id="sharing-stories" name="sharing-stories"><i class="anchor-icon"></i></a>Sharing stories</h3>
<pre><code><a href='/constructor/inputMediaStory'>inputMediaStory</a>#89fdd778 peer:<a href='/type/InputPeer'>InputPeer</a> id:<a href='/type/int'>int</a> = <a href='/type/InputMedia'>InputMedia</a>;
<a href='/constructor/messageMediaStory'>messageMediaStory</a>#68cb6283 flags:<a href='/type/%23'>#</a> via_mention:flags.1?<a href='/constructor/true'>true</a> peer:<a href='/type/Peer'>Peer</a> id:<a href='/type/int'>int</a> story:flags.0?<a href='/type/StoryItem'>StoryItem</a> = <a href='/type/MessageMedia'>MessageMedia</a>;
---functions---
<a href='/method/messages.sendMedia'>messages.sendMedia</a>#72ccc23d flags:<a href='/type/%23'>#</a> silent:flags.5?<a href='/constructor/true'>true</a> background:flags.6?<a href='/constructor/true'>true</a> clear_draft:flags.7?<a href='/constructor/true'>true</a> noforwards:flags.14?<a href='/constructor/true'>true</a> update_stickersets_order:flags.15?<a href='/constructor/true'>true</a> peer:<a href='/type/InputPeer'>InputPeer</a> reply_to:flags.0?<a href='/type/InputReplyTo'>InputReplyTo</a> media:<a href='/type/InputMedia'>InputMedia</a> message:<a href='/type/string'>string</a> random_id:<a href='/type/long'>long</a> reply_markup:flags.2?<a href='/type/ReplyMarkup'>ReplyMarkup</a> entities:flags.3?<a href='/type/Vector%20t'>Vector</a>&lt;<a href='/type/MessageEntity'>MessageEntity</a>&gt; schedule_date:flags.10?<a href='/type/int'>int</a> send_as:flags.13?<a href='/type/InputPeer'>InputPeer</a> = <a href='/type/Updates'>Updates</a>;</code></pre>
<p>Stories can be shared as messages to any chat by simply using <a href="/method/messages.sendMedia">messages.sendMedia</a>, passing an <a href="/constructor/inputMediaStory">inputMediaStory</a> referencing the shared story. </p>
<p>The story will be shared as a <a href="/constructor/messageMediaStory">messageMediaStory</a>, and should be displayed as a message forwarded from the poster of the story (even though <a href="/method/messages.forwardMessages">messages.forwardMessages</a> was not used an the <code>fwd_from</code> field of the <a href="/constructor/message">message</a> <strong>won't</strong> be set). </p>
<p>A message containing a <a href="/constructor/messageMediaStory">messageMediaStory</a> with the <code>via_mention</code> flag coming from the story poster will also be generated automatically if the poster mentions us in the story's caption. </p>
<h3><a class="anchor" href="#fetching-the-viewer-list" id="fetching-the-viewer-list" name="fetching-the-viewer-list"><i class="anchor-icon"></i></a>Fetching the viewer list</h3>
<pre><code><a href='/constructor/storyView'>storyView</a>#b0bdeac5 flags:<a href='/type/%23'>#</a> blocked:flags.0?<a href='/constructor/true'>true</a> blocked_my_stories_from:flags.1?<a href='/constructor/true'>true</a> user_id:<a href='/type/long'>long</a> date:<a href='/type/int'>int</a> reaction:flags.2?<a href='/type/Reaction'>Reaction</a> = <a href='/type/StoryView'>StoryView</a>;
<a href='/constructor/stories.storyViewsList'>stories.storyViewsList</a>#46e9b9ec flags:<a href='/type/%23'>#</a> count:<a href='/type/int'>int</a> reactions_count:<a href='/type/int'>int</a> views:<a href='/type/Vector%20t'>Vector</a>&lt;<a href='/type/StoryView'>StoryView</a>&gt; users:<a href='/type/Vector%20t'>Vector</a>&lt;<a href='/type/User'>User</a>&gt; next_offset:flags.0?<a href='/type/string'>string</a> = <a href='/type/stories.StoryViewsList'>stories.StoryViewsList</a>;

50
data/web/corefork.telegram.org/constructor/messageMediaStory.html
View file

@ -4,38 +4,10 @@
<meta charset="utf-8">
<title>messageMediaStory</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta property="description" content="Parameters
Name
Type
Description
flags
#
Flags, see TL conditional fields
via_mention
flags.1?true
 
peer
Peer
 
id
int…">
<meta property="description" content="Represents a forwarded story or a story mention.">
<meta property="og:title" content="messageMediaStory">
<meta property="og:image" content="">
<meta property="og:description" content="Parameters
Name
Type
Description
flags
#
Flags, see TL conditional fields
via_mention
flags.1?true
 
peer
Peer
 
id
int…">
<meta property="og:description" content="Represents a forwarded story or a story mention.">
<link rel="icon" type="image/svg+xml" href="/img/website_icon.svg?4">
<link rel="apple-touch-icon" sizes="180x180" href="/img/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/img/favicon-32x32.png">
@ -70,7 +42,8 @@ int…">
<div class="dev_page_bread_crumbs"><ul class="breadcrumb clearfix"><li><a href="/api" >API</a></li><i class="icon icon-breadcrumb-divider"></i><li><a href="/schema" >TL-schema</a></li><i class="icon icon-breadcrumb-divider"></i><li><a href="/constructor/messageMediaStory" >messageMediaStory</a></li></ul></div>
<h1 id="dev_page_title">messageMediaStory</h1>
<div id="dev_page_content"><p><div class="clearfix">
<div id="dev_page_content"><p>Represents a forwarded <a href="/api/stories">story</a> or a story mention.</p>
<p><div class="clearfix">
<ul class="dev_layer_select slightly-pull-right nav nav-pills">
<li class="dropdown">
<a class="dropdown-toggle" onclick="return dropdownClick(this, event)" href="#">Layer 164 <b class="caret"></b></a>
@ -101,27 +74,32 @@ int…">
<tr>
<td><strong>via_mention</strong></td>
<td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.1?<a href="/constructor/true">true</a></td>
<td> </td>
<td>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).</td>
</tr>
<tr>
<td><strong>peer</strong></td>
<td style="text-align: center;"><a href="/type/Peer">Peer</a></td>
<td> </td>
<td>Peer that posted the story.</td>
</tr>
<tr>
<td><strong>id</strong></td>
<td style="text-align: center;"><a href="/type/int">int</a></td>
<td> </td>
<td>Story ID</td>
</tr>
<tr>
<td><strong>story</strong></td>
<td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.0?<a href="/type/StoryItem">StoryItem</a></td>
<td> </td>
<td>The story itself, if absent fetch it using <a href="/method/stories.getStoriesByID">stories.getStoriesByID</a> and the <code>peer</code>/<code>id</code> parameters specified above.</td>
</tr>
</tbody>
</table>
<h3><a class="anchor" href="#type" id="type" name="type"><i class="anchor-icon"></i></a>Type</h3>
<p><a href="/type/MessageMedia">MessageMedia</a></p></div>
<p><a href="/type/MessageMedia">MessageMedia</a></p>
<h3><a class="anchor" href="#related-pages" id="related-pages" name="related-pages"><i class="anchor-icon"></i></a>Related pages</h3>
<h4><a class="anchor" href="#storiesgetstoriesbyid" id="storiesgetstoriesbyid" name="storiesgetstoriesbyid"><i class="anchor-icon"></i></a><a href="/method/stories.getStoriesByID">stories.getStoriesByID</a></h4>
<p>Obtain full info about a set of <a href="/api/stories">stories</a> by their IDs.</p>
<h4><a class="anchor" href="#stories" id="stories" name="stories"><i class="anchor-icon"></i></a><a href="/api/stories">Stories</a></h4>
<p>Telegram users and channels can easily post and view stories through the API.</p></div>
</div>

37
data/web/corefork.telegram.org/constructor/webPageAttributeStory.html
View file

@ -4,34 +4,10 @@
<meta charset="utf-8">
<title>webPageAttributeStory</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta property="description" content="Parameters
Name
Type
Description
flags
#
Flags, see TL conditional fields
peer
Peer
Peer that posted the story
id
int
Story…">
<meta property="description" content="Webpage preview of a Telegram story">
<meta property="og:title" content="webPageAttributeStory">
<meta property="og:image" content="">
<meta property="og:description" content="Parameters
Name
Type
Description
flags
#
Flags, see TL conditional fields
peer
Peer
Peer that posted the story
id
int
Story…">
<meta property="og:description" content="Webpage preview of a Telegram story">
<link rel="icon" type="image/svg+xml" href="/img/website_icon.svg?4">
<link rel="apple-touch-icon" sizes="180x180" href="/img/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/img/favicon-32x32.png">
@ -66,7 +42,8 @@ Story…">
<div class="dev_page_bread_crumbs"><ul class="breadcrumb clearfix"><li><a href="/api" >API</a></li><i class="icon icon-breadcrumb-divider"></i><li><a href="/schema" >TL-schema</a></li><i class="icon icon-breadcrumb-divider"></i><li><a href="/constructor/webPageAttributeStory" >webPageAttributeStory</a></li></ul></div>
<h1 id="dev_page_title">webPageAttributeStory</h1>
<div id="dev_page_content"><p><div class="clearfix">
<div id="dev_page_content"><p>Webpage preview of a Telegram story</p>
<p><div class="clearfix">
<ul class="dev_layer_select slightly-pull-right nav nav-pills">
<li class="dropdown">
<a class="dropdown-toggle" onclick="return dropdownClick(this, event)" href="#">Layer 164 <b class="caret"></b></a>
@ -107,7 +84,7 @@ Story…">
<tr>
<td><strong>story</strong></td>
<td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.0?<a href="/type/StoryItem">StoryItem</a></td>
<td> </td>
<td>May contain the story, if not the story should be fetched when and if needed using <a href="/method/stories.getStoriesByID">stories.getStoriesByID</a> with the above <code>id</code> and <code>peer</code>.</td>
</tr>
</tbody>
</table>
@ -115,7 +92,9 @@ Story…">
<p><a href="/type/WebPageAttribute">WebPageAttribute</a></p>
<h3><a class="anchor" href="#related-pages" id="related-pages" name="related-pages"><i class="anchor-icon"></i></a>Related pages</h3>
<h4><a class="anchor" href="#stories" id="stories" name="stories"><i class="anchor-icon"></i></a><a href="/api/stories">Stories</a></h4>
<p>Telegram users and channels can easily post and view stories through the API.</p></div>
<p>Telegram users and channels can easily post and view stories through the API.</p>
<h4><a class="anchor" href="#storiesgetstoriesbyid" id="storiesgetstoriesbyid" name="storiesgetstoriesbyid"><i class="anchor-icon"></i></a><a href="/method/stories.getStoriesByID">stories.getStoriesByID</a></h4>
<p>Obtain full info about a set of <a href="/api/stories">stories</a> by their IDs.</p></div>
</div>

2
data/web/corefork.telegram.org/type/MessageMedia.html
View file

@ -138,7 +138,7 @@
</tr>
<tr>
<td><a href="/constructor/messageMediaStory">messageMediaStory</a></td>
<td> </td>
<td>Represents a forwarded <a href="/api/stories">story</a> or a story mention.</td>
</tr>
</tbody>
</table>

2
data/web/corefork.telegram.org/type/WebPageAttribute.html
View file

@ -72,7 +72,7 @@
</tr>
<tr>
<td><a href="/constructor/webPageAttributeStory">webPageAttributeStory</a></td>
<td> </td>
<td>Webpage preview of a Telegram story</td>
</tr>
</tbody>
</table></div>