diff --git a/data/web/corefork.telegram.org/api/emoji-status.html b/data/web/corefork.telegram.org/api/emoji-status.html index 903ecd3c32..24a1fcb160 100644 --- a/data/web/corefork.telegram.org/api/emoji-status.html +++ b/data/web/corefork.telegram.org/api/emoji-status.html @@ -88,12 +88,13 @@ account.emojiStatuses#90c467d1 hash:long statuses:Vector<EmojiStatus> = account.EmojiStatuses; inputStickerSetEmojiDefaultStatuses#29d0f5ee = InputStickerSet; +inputStickerSetEmojiChannelDefaultStatuses#49748553 = InputStickerSet; ---functions--- account.getDefaultEmojiStatuses#d6753386 hash:long = account.EmojiStatuses; account.getChannelDefaultEmojiStatuses#7727a7d5 hash:long = account.EmojiStatuses; -

A set of standard statuses can be fetched by passing inputStickerSetEmojiDefaultStatuses to messages.getStickerSet, as specified in the stickerset documentation ».

+

A set of standard statuses for users/channels can be fetched by passing inputStickerSetEmojiDefaultStatuses/inputStickerSetEmojiChannelDefaultStatuses to messages.getStickerSet, as specified in the stickerset documentation ».

account.getDefaultEmojiStatuses can also be used to get a list of featured emoji statuses, from multiple featured custom emoji stickersets.
account.getChannelDefaultEmojiStatuses is the equivalent method for channel emoji statuses.

diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html index b53eb5d8cc..9485182e54 100644 --- a/data/web/corefork.telegram.org/api/layers.html +++ b/data/web/corefork.telegram.org/api/layers.html @@ -143,13 +143,13 @@
  • Added stories.storyReactionsList - List of peers that reacted to or intercated with a specific story
  • Added storyViewPublicForward -
  • Added storyViewPublicRepost -
  • -
  • Added channelAdminLogEventActionChangePeerColor -
  • -
  • Added channelAdminLogEventActionChangeProfilePeerColor -
  • -
  • Added channelAdminLogEventActionChangeWallpaper -
  • -
  • Added channelAdminLogEventActionChangeEmojiStatus -
  • -
  • Added inputStickerSetEmojiChannelDefaultStatuses -
  • +
  • Added channelAdminLogEventActionChangePeerColor - The message accent color was changed
  • +
  • Added channelAdminLogEventActionChangeProfilePeerColor - The profile accent color was changed
  • +
  • Added channelAdminLogEventActionChangeWallpaper - The wallpaper was changed
  • +
  • Added channelAdminLogEventActionChangeEmojiStatus - The emoji status was changed
  • +
  • Added inputStickerSetEmojiChannelDefaultStatuses - Default custom emoji status stickerset for channel statuses
  • Added mediaAreaChannelPost -
  • -
  • Added inputMediaAreaChannelPost -
  • +
  • Added inputMediaAreaChannelPost - Represents a channel post
  • Added updateBotMessageReaction -
  • Added updateBotMessageReactions -
  • diff --git a/data/web/corefork.telegram.org/api/stories.html b/data/web/corefork.telegram.org/api/stories.html index 99048f1bb6..51fbd91918 100644 --- a/data/web/corefork.telegram.org/api/stories.html +++ b/data/web/corefork.telegram.org/api/stories.html @@ -189,10 +189,19 @@ When the stories of a user are marked as hidden, the stories_hidden

    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

    +

    Fetching the interaction 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;
    +storyViewPublicForward#9083670b flags:# blocked:flags.0?true blocked_my_stories_from:flags.1?true message:Message = StoryView;
    +storyViewPublicRepost#bd74cf49 flags:# blocked:flags.0?true blocked_my_stories_from:flags.1?true peer_id:Peer story:StoryItem = StoryView;
    +
     stories.storyViewsList#59d78fc5 flags:# count:int views_count:int forwards_count:int reactions_count:int views:Vector<StoryView> chats:Vector<Chat> users:Vector<User> next_offset:flags.0?string = stories.StoryViewsList;
     
    +storyReaction#6090d6d5 peer_id:Peer date:int reaction:Reaction = StoryReaction;
    +storyReactionPublicForward#bbab2643 message:Message = StoryReaction;
    +storyReactionPublicRepost#cfcd0f13 peer_id:Peer story:StoryItem = StoryReaction;
    +
    +stories.storyReactionsList#aa5f789c flags:# count:int reactions:Vector<StoryReaction> chats:Vector<Chat> users:Vector<User> next_offset:flags.0?string = stories.StoryReactionsList;
    +
     storyViews#8d595cd6 flags:# has_viewers:flags.1?true views_count:int forwards_count:flags.2?int reactions:flags.3?Vector<ReactionCount> reactions_count:flags.4?int recent_viewers:flags.0?Vector<long> = StoryViews;
     stories.storyViews#de9eed1d views:Vector<StoryViews> users:Vector<User> = stories.StoryViews;
     
    @@ -200,9 +209,22 @@ When the stories of a user are marked as hidden, the stories_hidden
     
     stories.getStoryViewsList#7ed23c57 flags:# just_contacts:flags.0?true reactions_first:flags.2?true forwards_first:flags.3?true peer:InputPeer q:flags.1?string id:int offset:string limit:int = stories.StoryViewsList;
     
    +stories.getStoryReactionsList#b9b2881f flags:# forwards_first:flags.2?true peer:InputPeer id:int reaction:flags.0?Reaction offset:flags.1?string limit:int = stories.StoryReactionsList;
    +
     stories.getStoriesViews#28e16cc8 peer:InputPeer id:Vector<int> = stories.StoryViews;
    -

    Use stories.getStoryViewsList to obtain the full list of users that have viewed a specific story we posted, returned as a list of storyView constructors; pass the returned next_offset (if present) to offset to paginate through the results; the full list is available at all times only to Premium users, and will be deleted on stories posted by non-Premium users story_viewers_expire_period » seconds after the story expires; if it's still viewable, the has_viewers flag will be set.

    -

    Use stories.getStoriesViews to obtain info about the view count, forward count, reactions and recent viewers list of one or more stories, using a single, unpaginated method call, obviously potentially returning less info than stories.getStoryViewsList.

    +

    Use stories.getStoryViewsList to obtain the full list of users that have interacted with a specific story we posted as a user, returned as a list of StoryView constructors; pass the returned next_offset (if present) to offset to paginate through the results; the full list is available at all times only to Premium users, and will be deleted on stories posted by non-Premium users story_viewers_expire_period » seconds after the story expires; if it's still viewable, the has_viewers flag will be set.

    +

    The above method can only be used for stories posted by users, to fetch almost the exact same information for stories posted by channels, use stories.getStoryReactionsList: the data returned by both methods is actually almost exactly the same, the only difference is that:

    + +

    For the rest, both methods return information about:

    + +

    Additionally, stories.getStoriesViews can be used to obtain info about the view count, forward count, reactions and recent viewers list of one or more stories, using a single, unpaginated method call, obviously potentially returning less info than stories.getStoryViewsList.

    Replying to stories

    inputReplyToStory#15b0f283 user_id:InputUser story_id:int = InputReplyTo;
     
    @@ -264,6 +286,12 @@ When the stories of a user are marked as hidden, the stories_hidden
     

    Stories can have so-called "media areas": clickable rectangular areas with animated overlays on top of the story offering functionality like location tags or reactions.

    The coordinates and size of each media area is specified in a mediaAreaCoordinates constructor attached to each MediaArea, see the constructor page » for more info.

    After construction, the vector of MediaArea constructors can be passed to stories.sendStory or stories.editStory.

    +

    Channel posts

    +
    inputMediaAreaChannelPost#2271f2bf coordinates:MediaAreaCoordinates channel:InputChannel msg_id:int = MediaArea;
    +
    +mediaAreaChannelPost#770416af coordinates:MediaAreaCoordinates channel_id:long msg_id:int = MediaArea;
    +

    Messages from channels can be reposted to stories using inputMediaAreaChannelPost/mediaAreaChannelPost.

    +

    Clients should fetch and display a copy of the channel post on top of the story according to the media area coordinates: clicking on the media area should open the linked post.

    Location tags

    Schema:

    geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;
    @@ -297,27 +325,16 @@ Note that this should be done transparently in a map UI, not in the usual inline
     
     updateSentStoryReaction#7d627683 peer:Peer story_id:int reaction:Reaction = Update;
     
    -storyReaction#6090d6d5 peer_id:Peer date:int reaction:Reaction = StoryReaction;
    -
    -stories.storyViewsList#59d78fc5 flags:# count:int views_count:int forwards_count:int reactions_count:int views:Vector<StoryView> chats:Vector<Chat> users:Vector<User> next_offset:flags.0?string = stories.StoryViewsList;
    -
    -stories.storyReactionsList#aa5f789c flags:# count:int reactions:Vector<StoryReaction> chats:Vector<Chat> users:Vector<User> next_offset:flags.0?string = stories.StoryReactionsList;
    -
     ---functions---
     
    -stories.sendReaction#7fd736b2 flags:# add_to_recent:flags.0?true peer:InputPeer story_id:int reaction:Reaction = Updates;
    -
    -stories.getStoryViewsList#7ed23c57 flags:# just_contacts:flags.0?true reactions_first:flags.2?true forwards_first:flags.3?true peer:InputPeer q:flags.1?string id:int offset:string limit:int = stories.StoryViewsList;
    -
    -stories.getStoryReactionsList#b9b2881f flags:# forwards_first:flags.2?true peer:InputPeer id:int reaction:flags.0?Reaction offset:flags.1?string limit:int = stories.StoryReactionsList;
    +stories.sendReaction#7fd736b2 flags:# add_to_recent:flags.0?true peer:InputPeer story_id:int reaction:Reaction = Updates;

    Story reactions are implemented using a simple in-UI button that allows the user to send any reaction using stories.sendReaction.

    Sending this method will return an updateSentStoryReaction update to all logged-in sessions.

    However, the poster of a story may also use mediaAreaSuggestedReaction media areas » to suggest some specific reactions as simple clickable buttons: they're rendered as a round comic-style thought bubble with its "tail" on the right, white background and the reaction » from the reaction field located in its center.
    If the dark flag is set, the background should be black.
    If the flipped flag is set, the "tail" should be located on the left.

    Clicking it should invoke stories.sendReaction as usual.

    -

    To get the reaction list of a story posted as a user, use stories.getStoryViewsList, see here » for more info on how to use the method.
    -To get the reaction list of a story posted as a channel, use stories.getStoryReactionsList, see here » for more info on how to use the method (the parameters and behavior is pretty much the same as for stories.getStoryViewsList, the only difference is that the viewer list cannot be fetched with it).

    +

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

    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:

    diff --git a/data/web/corefork.telegram.org/constructor/channel.html b/data/web/corefork.telegram.org/constructor/channel.html index 6b350476a5..cc318008c2 100644 --- a/data/web/corefork.telegram.org/constructor/channel.html +++ b/data/web/corefork.telegram.org/constructor/channel.html @@ -264,17 +264,17 @@ profile_color flags2.8?PeerColor -  +The channel's profile color. emoji_status flags2.9?EmojiStatus -  +Emoji status level flags2.10?int -  +Boost level @@ -302,7 +302,11 @@

    Admin, banned, default rights

    How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

    Accent colors

    -

    Telegram users and channels can change the accent color and background pattern of their profile page and their messages!

    +

    Telegram users and channels can change the accent color and background pattern of their profile page and their messages!

    +

    Emoji status

    +

    Telegram allows users to set an emoticon or a custom emoji as status, to show next to their name in chats and profiles.

    +

    Channel boosts

    +

    Telegram Premium users can grant their favorite channels additional features like the ability to post stories by giving them boosts.

    diff --git a/data/web/corefork.telegram.org/constructor/channelAdminLogEventActionChangeEmojiStatus.html b/data/web/corefork.telegram.org/constructor/channelAdminLogEventActionChangeEmojiStatus.html index d0f1ee2c08..6deffdbf81 100644 --- a/data/web/corefork.telegram.org/constructor/channelAdminLogEventActionChangeEmojiStatus.html +++ b/data/web/corefork.telegram.org/constructor/channelAdminLogEventActionChangeEmojiStatus.html @@ -4,32 +4,10 @@ channelAdminLogEventActionChangeEmojiStatus - + - + @@ -64,7 +42,8 @@ ChannelAdminLogEventAction">

    channelAdminLogEventActionChangeEmojiStatus

    -

    +

    The emoji status was changed

    +

    +

    ChannelAdminLogEventAction

    +

    Related pages

    +

    Emoji status

    +

    Telegram allows users to set an emoticon or a custom emoji as status, to show next to their name in chats and profiles.

    diff --git a/data/web/corefork.telegram.org/constructor/channelAdminLogEventActionChangePeerColor.html b/data/web/corefork.telegram.org/constructor/channelAdminLogEventActionChangePeerColor.html index fd652cb3a5..080310179f 100644 --- a/data/web/corefork.telegram.org/constructor/channelAdminLogEventActionChangePeerColor.html +++ b/data/web/corefork.telegram.org/constructor/channelAdminLogEventActionChangePeerColor.html @@ -4,32 +4,10 @@ channelAdminLogEventActionChangePeerColor - + - + @@ -64,7 +42,8 @@ ChannelAdminLogEventAction">

    channelAdminLogEventActionChangePeerColor

    -

    +

    The message accent color was changed

    +

    +

    ChannelAdminLogEventAction

    +

    Related pages

    +

    Accent colors

    +

    Telegram users and channels can change the accent color and background pattern of their profile page and their messages!

    diff --git a/data/web/corefork.telegram.org/constructor/channelAdminLogEventActionChangeProfilePeerColor.html b/data/web/corefork.telegram.org/constructor/channelAdminLogEventActionChangeProfilePeerColor.html index f69898464a..d6e3240411 100644 --- a/data/web/corefork.telegram.org/constructor/channelAdminLogEventActionChangeProfilePeerColor.html +++ b/data/web/corefork.telegram.org/constructor/channelAdminLogEventActionChangeProfilePeerColor.html @@ -4,32 +4,10 @@ channelAdminLogEventActionChangeProfilePeerColor - + - + @@ -64,7 +42,8 @@ ChannelAdminLogEventAction">

    channelAdminLogEventActionChangeProfilePeerColor

    -

    +

    The profile accent color was changed

    +

    +

    ChannelAdminLogEventAction

    +

    Related pages

    +

    Accent colors

    +

    Telegram users and channels can change the accent color and background pattern of their profile page and their messages!

    diff --git a/data/web/corefork.telegram.org/constructor/channelAdminLogEventActionChangeWallpaper.html b/data/web/corefork.telegram.org/constructor/channelAdminLogEventActionChangeWallpaper.html index e4613c30f3..4fc83426ec 100644 --- a/data/web/corefork.telegram.org/constructor/channelAdminLogEventActionChangeWallpaper.html +++ b/data/web/corefork.telegram.org/constructor/channelAdminLogEventActionChangeWallpaper.html @@ -4,32 +4,10 @@ channelAdminLogEventActionChangeWallpaper - + - + @@ -64,7 +42,8 @@ ChannelAdminLogEventAction">

    channelAdminLogEventActionChangeWallpaper

    -

    +

    The wallpaper was changed

    +

    +

    ChannelAdminLogEventAction

    +

    Related pages

    +

    Wallpapers

    +

    Telegram apps support generating, sharing and synchronizing chat backgrounds.

    diff --git a/data/web/corefork.telegram.org/constructor/channelFull.html b/data/web/corefork.telegram.org/constructor/channelFull.html index d99718e06e..156327481a 100644 --- a/data/web/corefork.telegram.org/constructor/channelFull.html +++ b/data/web/corefork.telegram.org/constructor/channelFull.html @@ -329,7 +329,7 @@ wallpaper flags2.7?WallPaper -  +Wallpaper @@ -370,7 +370,9 @@

    Invites

    Chats and channels may have a public username or a private invite link: private invite links may be further enhanced with per-user join requests.

    Message reactions

    -

    Telegram allows users to react on any message using specific emojis, triggering cute lottie animations.

    +

    Telegram allows users to react on any message using specific emojis, triggering cute lottie animations.

    +

    Wallpapers

    +

    Telegram apps support generating, sharing and synchronizing chat backgrounds.

    diff --git a/data/web/corefork.telegram.org/constructor/help.peerColorOption.html b/data/web/corefork.telegram.org/constructor/help.peerColorOption.html index d768baf51e..4d45f30fa6 100644 --- a/data/web/corefork.telegram.org/constructor/help.peerColorOption.html +++ b/data/web/corefork.telegram.org/constructor/help.peerColorOption.html @@ -94,13 +94,15 @@ channel_min_level flags.3?int -  +Channels can use this palette only after reaching at least the boost level specified in this field.

    Type

    help.PeerColorOption

    Related pages

    +

    Channel boosts

    +

    Telegram Premium users can grant their favorite channels additional features like the ability to post stories by giving them boosts.

    Accent colors

    Telegram users and channels can change the accent color and background pattern of their profile page and their messages!

    diff --git a/data/web/corefork.telegram.org/constructor/inputMediaAreaChannelPost.html b/data/web/corefork.telegram.org/constructor/inputMediaAreaChannelPost.html index c4906af9f6..3c6a41d0f5 100644 --- a/data/web/corefork.telegram.org/constructor/inputMediaAreaChannelPost.html +++ b/data/web/corefork.telegram.org/constructor/inputMediaAreaChannelPost.html @@ -4,38 +4,10 @@ inputMediaAreaChannelPost - + - + @@ -70,7 +42,8 @@ MediaArea">

    inputMediaAreaChannelPost

    -

    +

    Represents a channel post

    +

    diff --git a/data/web/corefork.telegram.org/type/MediaArea.html b/data/web/corefork.telegram.org/type/MediaArea.html index 04d52b5922..3d97a59bd4 100644 --- a/data/web/corefork.telegram.org/type/MediaArea.html +++ b/data/web/corefork.telegram.org/type/MediaArea.html @@ -92,7 +92,7 @@ inputMediaAreaChannelPost -  +Represents a channel post