BYOD4LChat Number 1

I created this page as a proof of concept using CoDog’s link extraction tool on the story that was curated by Sheila McNeil.

Observations, long tweetchats like this should be edited in the Text view in WordPress. Rendering the tweets in the Visual HTML editor view is not something that the WordPress can cope with, but is probably necessary if you want to add commentary to a chat rather than a straight record.

The page will take a long time to load as each tweet has fetched as HTML, embedded in the post and rendered by the browser! (I assume Storify caches the embedded tweets somehow to avoid overloading the Twitter APIs.)

There’s a danger that you might crash your WordPress server!

Conclusion, a story which can be archived as a static website (See Archiving Tweetchats) may actually be preferable!

Here is the Archived Chat

Archiving Tweetchats – Experiment 1

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.)

status_url

How to archive your Storify stories on GitHub pages

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!