1) Get PDF archives of all your own threads
2) Publish your threads to blog using Micropub
We are providing these for free to help authors spread their work!
With the idea of Micropub allowing the ability to create updates, why couldn’t one build (or even modify) a Micropub client to create an interface to write relatively short updates with (date and timestamps to appear in the text) that, when published, concatenated that new piece of content into a longer piece of running text to send an updated Micropub request to an article or note on a site to allow that article to become an updating liveblog post?
I’m a bit shocked that no one has done it before now, and I suspect that one of the pre-existing micropub clients out there could probably add the functionality as a one day project at an upcoming IndieWebCamp.
I don’t suspect it was the sort of Micropub functionality that Kevin Marks was thinking about doing this weekend, but Noter Live comes pretty close to having a lot of this sort of UI already. Instead of just doing a single Micropub post at the end of a Twitter thread, why couldn’t it do an initial post at the beginning and then update the site with subsequent updates as it goes along while also acting as a means of syndicating the posts to Twitter and then returning those Twitter permalinks as syndication links on the user’s own site?
There is also an open source project called Silo.pub that provides a micropub endpoint for services like Tumblr, WordPress.com, Blogger, and Twitter (among others). Aaron Parecki has a public version I’m sure he wouldn’t mind if you tried.
Other platforms could quickly allow the functionality and so much more by building their own micropub servers, which would be a major boon to the social media space and the open web.
If you have questions about implementation while building, feel free to pop into the IndieWeb #dev chat (where prior implementers and others) are available for help. (Alternate chat modalities including Slack and IRC are available if you prefer.)
This would be a great way to leverage their existing infrastructure and to allow people to put their own Tweetstorms onto their blog and solve the perennial “Why didn’t you just blog about this” commentary.
At Twitter, we have a history of studying how people use our service and then creating features to make what they’re doing easier. The Retweet, '@reply', and hashtag are examples of this. A few years ago we noticed people creatively stitching Tweets together to share more information or tell a longer story – like this. We saw this approach (which we call “threading”) as an innovative way to present a train of thought, made up of connected but individual elements.
I don’t like Tweetstorms™, or, to turn to a neologism, “manthreading”. They actively annoy me. Stop it. People who do this are almost always blowhards. Blogs are free. Put your ideas on your blog.