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 24 hours after being added. People use this feature to tell a story about their day.
Stories seem to be more easily shared than posts, because they lack editing – there is less applying filters and clipping out video fragments, more just sharing the 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 yours, there is less pressure to make it perfect.
The video fragments in stories are short, usually not longer than 10 seconds, and skippable per fragment. This lessens the need to edit the message down to an interesting storyline, and moves the editing from the sender to the viewer.
- Aaron Parecki 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.
- Add yourself here… (see this for more details)
- 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.
- 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.
- Brainstorming thread about stories in the IndieWeb involving Vika, Aaron Parecki and Eddie Hinkle. 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)
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)
- 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
- Notable pieces in the JSON: