story

A  story  is a singular (one per profile) time stream collection post, that consists of ephemeral photo and video posts that are shown in sequence one at a time and disappear from the collection some time after being added, usually 24 hours.

Stories seem to be more easily shared than posts. Most stories are less edited, except when the story contains overlays like text or stickers. Their creation UI encourages spontaneity and sharing material right away. They also don't receive public likes and replies (one can reply privately on Snapchat and Instagram), and because they disappear after 24 hours, there is less pressure to make them perfect.

The video fragments in stories are short, usually not longer than 10 seconds. This lessens the need to edit the message down to an interesting storyline, and moves the editing from the sender to the viewer who can skip to the next fragment with a tap.

Some stories have built-in features for collecting simple responses such as a poll or "yes/no" toggle, and the author of the story can see the aggregate and individual responses, however the people responding can only see the aggregate responses.

In the case of Instagram and Facebook, There is usually no way to comment or otherwise react publicly to stories, other than the option of posting a copy of the story post to your own story.

IndieWeb Examples

 * supports stories on his home page since 2017-11-04. If there is any content posted to the "stories" section, the circle around his profile photo will be a gradient outline if you haven't seen the content yet or a grey outline if you have.
 * supports showing stories on his home page since May 2023. To post a story, James needs to manually update a list of images on his home page. Stories may not be ephermal on a 24 hour basis; rather, James can choose for how long an image is featured as a story. When a story is available, a blue border is displayed around James' profile image.





Instagram

 * since 2016-08-02

WhatsApp

 * since 2017-02-20 under the name “Status”. See the official announcement.

Facebook

 * since 2017-03-28

YouTube

 * since 2018-11-29 (for channels with over 10k subscribers). See also official documentation on creating and watching.

Stories on YouTube are visible for 7 days. Like videos, stories may be shown to people who are not subscribed to a channel as well.

Viewers can comment on stories, however the author can't reply to comments and is instead to "Reply in Story".

YouTube reports stats on the number of people who have subscribed after watching a story.

Twitter

 * 2020-11-17 through 2021-08-03(also Twitter blog) under the name “Fleets”.

Like most Story UIs, there is a horizontal scrolling list of avatars across the top of the Twitter app. On the far left, there is an add button to add your own story. At the time of this edit, this feature is only available if you're using the mobile Twitter app.



Something that does stand out about Twitter's implementation is that ability to add Text as a Story rather than just images/video. You can see adding a "fleeting thought" and being able to align it and do some basic styling to it.



Causes FOMO

 * Vika posted an article that explains how ephemeral stories lead to fear that she will miss content if she isn’t opening the app related to the content frequently. See also FOMO

Brainstorming
This will allow people to treat stories like ephemeral posts. Conforming Microsub readers would expunge (or mark as obsolete and old) data about expired posts (but probably should allow to archive them - we need to do better than silos and offer a save button). Fireburn.ru (talk) 12:47, 8 September 2019 (PDT)
 * Brainstorming thread about stories in the IndieWeb involving Vika, and . Thread starts here.
 * Vika’s criticism above lists the fear of missing out on Stories due to their ephemeral nature. This is a common tactic by Silos to keep people addicted to the apps. How can we in the IndieWeb create stories that don’t create that dependency? Allow each person to view each story item once only? Give a longer time window? 2 days? 7 days?
 * The following brainstorming occurred in result.
 * I suggest making a story another MF2 piece of content with following properties:
 * u-photo, u-video and/or e-content (Instagram stories allow text-only stories, rendered as text on a colorful backdrop)
 * An experimental property dt-expires - signifies the time when the content becomes obsolete and should be expunged (but can remain in archives if someone wants it to)
 * Zuck.js has a specific JSON format for their stories that could be helpful for brainstorming purposes.
 * Notable pieces in the JSON:
 * type - photo or video (this is also used in aaronpk's stories JSON)
 * length - the length of the video or the length that the photo should be displayed
 * src - the url of the photo or video file (aaronpk's stories JSON calls this filename)
 * link - a url that the user is taken to if the button is clicked
 * linkText - the text in the button that the user can take to open up the link url
 * time - unix timestamp of when the photo/video was published, zuck.js then converts that to "time ago" format for display to the user