tweetstorm is a series of tweets, each replying to the previous, often each numbered so the sequence is clear, as a method of expressing a longer series of related thoughts as a single thread on Twitter.
On/about 2019-04-24 Twitter changed their UI (on web) to allow users to edit multiple threaded tweets at the same time and click one button to publish them all simultaneously.
- 1 Why
- 2 IndieWeb Examples
- 3 Other Examples
- 4 Service Examples
- 5 Brainstorming
- 6 Articles with commentary on Tweetstorms
- 7 See Also
Should I post this in the CPLC moodle? I don't even know my dudes. Not gonna lie, I'm 10000% more comfortable writing this stuff on Twitter bc it feels less formal & therefore doesn't have to be "organized" or "actually good" & can just sometimes end up being surprisingly useful?— Jessica Chretien (@infuturereverse) May 19, 2019
Chris Aldrich only very occasionally tweetstorms (using Noter Live, without numbering tweets). Most often it is from conferences, talks, or meetings and then he later assembles them into a post on his own site.
For more "traditional" tweetstorms, I:
- compose them on my site for style and length
- cut and paste them into Noter Live in rapid succession
- I use Noter Live without the username filled in, so the tweets appear to come from me on Twitter without including my @handle; Noter Live also auto-threads the tweetstorm in the Twitter stream, so clicking on any one Tweet provides the entire thread/"story".
- I cut and paste the richer Noter Live data into my original post and publish or update the post
- I tweet one final note to Twitter with a link back to the compilation on my site and include that in my post
- Finally, I manually backfill all of the syndicated links onto the original post for future backfeed.
The process is an odd melange of both POSSE and PESOS, but it's typically geared towards reaching a broader Twitter audience over the traditional audience of my personal site. The benefit is that those who are subscribed to my personal site get a better experience.
Marc Andreessen often posts tweetstorms (on https://twitter.com/pmarca) that seem sufficiently structured that more than one site has sprung up which reposts them as complete blog posts:
He sometimes reposts his own tweetstorms on his own blog:
tweetstorm.io is a site that detects tweetstorms on Twitter user profiles, displays their recent tweet storms, and provides permalinks for each tweetstorm they detect. E.g. recent tweetstorm(s) of a profile:
- http://tweetstorm.io/user/FreedomofPress/ and tweetstorm permalink:
- http://tweetstorm.io/user/paulkrugman and multiple tweetstorm permalinks from that profile:
- http://tweetstorm.io/user/paulkrugman/801120843443175425 (has two tweetstorms)
- http://tweetstorm.io/user/paulkrugman/796362835999727617 (appears to combine two tweetstorms)
- http://tweetstorm.io/user/paulkrugman/796362835999727617 - use of a tweetstorm to put together thoughts that eventually went into a singular blogpost:
Thread Reader will convert a tweetstorm back into a single page post.
How do you cite repost or quote
Amy Guy suggests a single repost, with individual blockquote elements for each tweet of the tweetstorm with different dated permalink for each.
- h-cite markup needs to be updated to include p-content
How do you POSSE to tweetstorm
article to tweetstorm
I think Ben Werdmüller was wondering about this.
See Indieweb example above by Chris Aldrich.
One idea would be to publish a note and then if you publish a reply to that note in your publshing UI you could hit a "storm" or "stream" button. This edite the original note putting in a rel=next. The second post would would get a rel=prev. This pattern would continue until someone hit end "storm" button.
The first note would display all the replies in the storm. The second note would display n-1 (everything but the first).
Or perhaps tweetstorms "work" because of the Twitter UI's constraints.
There appears to be two kinds of tweetstorm syntax:
- List style: numbered (1.) from start to end, e.g. http://tweetstorm.io/user/FreedomofPress/798614923832070144
- Continuation style: numbered (1/) at the end tweets except for last tweet in the tweet storm, e.g. http://tweetstorm.io/user/paulkrugman/801242086834049024
Articles with commentary on Tweetstorms
- Tweetstorms vs Publishing by Jonathan LaCour
- 2017-02-10 Chris Aldrich: Tweetstorms, Journalism and Noter Live: A Modest Proposal by Chris Aldrich (includes other references/footnotes as well)
- 2018-01-29 Jeremy Keith: (calling it a Twitter thread instead) GDPR and Google Analytics
the form of the online equivalent of interpretive dance …a twitter thread (it’s called a thread because it inevitably gets all tangled, and it’s easy to break.)
- Noter Live
- 2017-04-17 @chriseppstein: I was about to tweet storm so I decided to blog and now I'm like 1000 words in and there's so much more I wanted to say and I hate blogging
- 2017-07-04 @NPR tweetstorms the US Declaration of Independence (100+ tweets long reply-chain)
- 2017-09-25 Are typeset blog posts too hard for you to read? Here's a script to turn them into a tweetstorm - https://codepen.io/chriscoyier/pen/RZEVVm/ (js;dr link)
- Thread Reader - unrolls a full Twitter thread on a single page for easier reading
- live tweeting
- Why, see thread, naturally: https://twitter.com/rahaeli/status/1004716924478132224
- "hello people can you PLEASE fucking stop doing endless variations on "this should have been a post instead of a Twitter thread" when someone chooses Twitter as a platform for a longer thread it is annoying AND ableist AND it's not news to anyone that blog posts exist" @rahaeli June 7, 2018
- Example: 75+ tweets spanning 17+ months, estimated ~1hr reading time: https://threadreaderapp.com/thread/943238420037431297.html (tweet start: https://twitter.com/kentbye/status/943238420037431297 )