🤫 LEAK: STORIES in Telegram

🥸 A source close to Telegram has shown and told @EBInfo editors details about a new upcoming feature in Telegram that has been the subject of rumors for the past few days - STORIES!

❓ Briefly:
• Up to 100 stories per day
• Privacy settings will be available
• Chat attachment for comments on stories
• Stories and chat comments will be deleted after 24 hours
• The list of recent stories will be displayed above the message list, similar to Facebook Messenger
• Scheduled stories

👀 The editor interface will be similar to Signal's. Users will be able to add music from any chat (similar to accessing the "Music" tab in the current global search, aggregating music from all chats and channels you are in). Video messages can be recorded and placed anywhere on top of the story. Additionally, similar to BeReal, there is a button that allows simultaneous snapshots from the main and selfie cameras. Interactive elements such as links are not implemented yet.

🤘 Masks are not being created due to an unsuccessful contest, but animators are currently working on new animated effects for stories. We can speculate that in the future, a simple video editor will be available where effects can be added at specific timestamps.

💬 A chat can be linked for comments, and a non-disableable 24-hour self-destruction timer is set for the chat (which can be turned off again if the group is detached). However, most messages are still deleted faster than 24 hours because replies to a story are deleted along with the story. Reactions can also be enabled for stories, functioning similarly to a regular channel.

🫦 Similar to avatars, stories can be made accessible to everyone, only contacts, or selected individuals.

🔔 Stories can be delayed and published at a designated time, similar to channel messages. Stories can be reported, and as well as shared as a link.

👉 READ MORE: IN-DEPTH TELEGRAM STORIES 👈

@ebinfo

🤫 LEAK: UNDER THE HOOD OF TELEGRAM STORIES

👉 READ MORE ABOUT TELEGRAM STORIES 👈

How will Telegram stories work?

A source has revealed the underlying implementation of stories in Telegram. Similar to forums, Telegram has taken an existing format and wrapped it in a beautiful interface.

In Layer 160, when publishing the first story, a special channel is created using the channels.createChannel method, with the stories flag [flags.6?true]. It's not possible to create more than one such channel simultaneously, but the channel can be deleted and recreated using the API. The channel now has the stories property in the channel constructor [flags.31?true]. This channel has no invitation links or username, and they cannot be assigned to it. The channel is not counted against any of the limits on the number of chats and channels. This channel has a non-disableable 24-hour timer.

The publishing system, reporting, delayed messages, and comments are inherited from channels. Publication is done through messages.sendMedia, where the video is uploaded like a regular message, but the inputMediaUploadedDocument attribute has the story flag set. The video must be in MPEG4 format, with one side being at least 800px and the width not exceeding the height. Video cropping to fit the screen size happens on the client side.

A chat can be attached to this channel, just like a regular channel (messages.setDiscussionGroup). If no chat is attached to the channel, the apps will send comments as private messages to the author.

The channel is returned as a channel constructor in the user constructor.

In the messages.getDialogs method, folder_id=2 has been added for the list of contacts' stories.

The app retrieves the list of user stories using the messages.searchSentMedia method with the inputMessagesFilterVideo filter. This implies a limitation of showing the last 100 visible stories. Stories will support deep links, and the story ID will be the post ID in the channel.

Currently, any type of post, even text posts, can be published directly to such a channel via MTProto. It's likely that this will be fixed before the release, but these posts do not affect the functionality of stories.

@ebinfo