The index page has more information how how it was done.
— Chris Jobling (@cpjobling) December 21, 2017
If you take a TAGS file (I used this one: BYOD4L 2016-2017 (@cpjobling)) and sort it in time order, you can then copy column Q (status_url) and paste the data into the HTML view of a WordPress page or Post to get a similar archive to that which @Storify produces.
Unfortunately, there seems to be a limit (on hosted WordPress at least) and only the first N tweets are shown (where N is to be determined). If there are more than N, only the links are shown. Also, retweets will need to be romoved from the data because they are not shown correctly.
(There is a bug in TAGS, the HTTPS protocol has to be used for WordPress to embed a tweet, but Martin records HTTP in the status URLs … A simple fix.)
Yesterday, Storify announced the retirement of its Storify service. This leaves a lot of users, including myself, with Storify stories linked into their blog sites and nowhere to host them when the service closes. Storify has provided an export feature, which can output a whole Storify store as a static HTML5 webpage, and GitHub provides a way to host static websites via its free GitHub pages feature. I, therefore, yesterday tweeted about a proof of concept trial:
Today, I’ve created a simple video to show how it was done.
I’ll be archiving my own collection of stories over the next few days and updating the links on this blog. To see my collection, visit cpjobling.github.io/stories.
This solves the problem for historical tweetchats. We, as a community, now need to find a new way to curate our future chats!
Today is Ada Lovelace Day – an annual celebration of women in STEM.
To mark the occasion I used Storify to make a personal curation of the tweets and blog posts that I liked on #AdaLovelaceDay 2017 (#ALD17)