diff --git a/data/web/corefork.telegram.org/api/config.html b/data/web/corefork.telegram.org/api/config.html index f7a0098e6d..8c9716be55 100644 --- a/data/web/corefork.telegram.org/api/config.html +++ b/data/web/corefork.telegram.org/api/config.html @@ -82,8 +82,6 @@ While help.getConfig returns MTProto-specif

Example value of help.appConfig.config: 

{
     "test": 1,
-    "keep_alive_service": true,
-    "background_connection": true,
     "emojies_animated_zoom": 0.625,
     "emojies_send_dice": [
         "\ud83c\udfb2",
@@ -204,6 +202,7 @@ While help.getConfig returns MTProto-specif
         "web.telegram.org",
         "web.t.me",
         "k.t.me",
+        "z.t.me",
         "a.t.me"
     ],
     "round_video_encoding": {
@@ -369,18 +368,28 @@ While help.getConfig returns MTProto-specif
     "intro_description_length_limit": 70,
     "business_chat_links_limit": 100,
     "channel_restrict_sponsored_level_min": 50,
+    "channel_revenue_withdrawal_enabled": true,
     "dismissed_suggestions": [],
     "stories_pinned_to_top_count_max": 3,
-    "can_edit_factcheck": false,
-    "factcheck_length_limit": 1024,
-    "channel_revenue_withdrawal_enabled": true,
-    "stars_purchase_blocked": true,
+    "stars_purchase_blocked": false,
+    "stories_area_url_max": 3,
+    "stars_revenue_withdrawal_min": 1000,
+    "stars_paid_post_amount_max": 2500,
     "web_app_allowed_protocols": [
         "http",
         "https"
-    ]
+    ],
+    "bot_preview_medias_max": 12,
+    "ton_proxy_address": "magic.org",
+    "weather_search_username": "StoryWeatherBot",
+    "story_weather_preload": true,
+    "stars_gifts_enabled": true
 }
-

Typical fields included in the resulting JSON object are:

+

The fields included in the resulting JSON object are:

+

weather_search_username

+

Contains the username of the bot used to query the current weather, to use in weather media areas as specified here ». (string)

+

story_weather_preload

+

If set and true, clients should preload the current weather on startup (as opposed to only when creating a weather media area) by querying the bot specified in weather_search_username. (boolean)

emojies_animated_zoom

Animated emojis and animated dice should be scaled by this factor before being shown to the user (float)

keep_alive_service

@@ -585,6 +594,8 @@ Note that the stickerset can be fetched using stories_entities

Whether styled text entities and links in story text captions can be used by all users (enabled), only [Premium](/api/premium users) (premium), or no one (disabled). (string)

This field is used both when posting stories, to indicate to the user whether they can use entities, and when viewing stories, to hide entities (client-side) on stories posted by users whose Premium subscription has expired (if stories_entities == "premium" and user.premium is not set, or if stories_entities == "disabled").

+

stories_area_url_max

+

Maximum number of URL media areas » that can be added to a posted story. (integer)

giveaway_gifts_purchase_available

Whether giveaways can be started by the current user. (boolean)

giveaway_add_peers_max

diff --git a/data/web/corefork.telegram.org/api/stories.html b/data/web/corefork.telegram.org/api/stories.html index 21a890ab24..e7e278d7c3 100644 --- a/data/web/corefork.telegram.org/api/stories.html +++ b/data/web/corefork.telegram.org/api/stories.html @@ -342,6 +342,22 @@ If the flipped flag is set, the "tail" should be located on the lef The maximum number of story reaction media areas that can be added to a story is specified by the stories_suggested_reactions_limit_* » config keys.
Clicking it should invoke stories.sendReaction as usual.

See here » to get more info on how to fetch the reaction list of a story.

+

URLs

+
mediaAreaUrl#37381085 coordinates:MediaAreaCoordinates url:string = MediaArea;
+

URL media areas offer stickers that when clicked, should offer the user a prompt (implemented as a tooltip on the sticker) to open the specified url.

+

The maximum number of URL media areas that can be added to a story is specified by the stories_area_url_max » config key.

+

Weather

+
mediaAreaWeather#49a6549c coordinates:MediaAreaCoordinates emoji:string temperature_c:double color:int = MediaArea;
+
+---functions---
+
+messages.getInlineBotResults#514e999d flags:# bot:InputUser peer:InputPeer geo_point:flags.0?InputGeoPoint query:string offset:string = messages.BotResults;
+

Users can now share the weather in their stories by adding one weather media area represented by mediaAreaWeather to their stories.

+

The weather media area should be rendered using the background ARGB color specified in color, and should contain the emoji specified in emoji, followed by the temperature specified in temperature_c (Celsius, which should be converted by the client to Fahrenheit if required by the device's settings), followed by °C or °F depending on the unit used.

+

To fetch the current temperature and emoji to use when creating a weather media area when posting a story, clients should internally make an inline query with messages.getInlineBotResults to the bot specified in the weather_search_username client configuration parameter, passing the user's current location in geo_point and inputPeerEmpty in peer.
+This query will return a single botInlineResult: the emoji to use will be contained in the botInlineResult.title and the temperature (always in Celsius) will be contained in botInlineResult.description (it will contain just the value without the unit, so it can be easily casted to a double).

+

The inline query should be made internally by the client when the user creates a new weather media area, not by showing the usual inline query UI, but by treating the inline query as an API call to fetch the weather for the current user's location.

+

If the story_weather_preload client configuration parameter is equal to true, clients should preload the weather using the flow specified above on startup (as opposed to only doing it when creating a weather media area).

Stealth mode

Premium users may enable stealth mode, erasing their views from any stories they opened in the past stories_stealth_past_period seconds », and hiding their views on stories for the next stories_stealth_future_period seconds », as specified by the client configuration ».

Schema: