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!
While using that method for publishing is still my preference for owning the content first and syndicating it to Twitter, there’s another method that many educators might find simpler. ThreadReaderApp now has beta support for the Micropub Spec so you can publish Twitter threads directly to your blog.
This means that participants can write their threads directly on Twitter and reverse syndicate them to their websites if they support the Micropub spec.
For PressEdConf participants who have WordPress.org based sites (or .com sites with a subscription that supports plugins), this should be relatively easy since there’s a Micropub plugin for WordPress.
Download the plugin, activate it, write your Twitter thread, and have Thread Reader unroll it. Then authentic Thread Reader to your website at https://threadreaderapp.com/account/micropub and click the publish button on the thread you want to copy to your site.
This functionality in Thread Reader will also work for any other blogging platform or CMS that has either native or plugin support for Micropub. This includes platforms like Drupal, Grav, WithKnown, and many others including several static site generators.
Once things are set up, it’s pretty straightforward. You can read about my first experience (linked above) for more details.
If you have prior unrolled Twitter threads in your Thread Reader account you can use them as test cases before the next PressEdConf.
I wish @ThreadReaderApp had the ability to authenticate into my personal website & publish a copy of my tweetstorms into my blog using Micropub. This would be a great way to leverage existing infrastructure and to allow people to put their [more…]https://t.co/maWditNLNB
— Chris Aldrich (@ChrisAldrich) March 6, 2020
I would often see people post tweetstorms, long threads of related tweets, to tell an extended story.
Invariably people see these threads and say “Why don’t/didn’t you just post that on your website as a blog post instead?”
(In fact, why don’t you try it on this very tweet?)
I’ve personally been using the #IndieWeb concept of P.O.S.S.E. (Post on your Own Site and Syndicate Elsewhere) for a while now. I’ll post my content on my personal website first and only then syndicate a copy to Twitter.
But today, for the first time in a very LONG time, I’m posting this particular thread to Twitter first…
Then when I’m done, I’ll roll it all up conveniently using the awesome @ThreadReaderApp which will put a nice readable version on their site.
Sadly, I don’t own that copy…
It really needs to be on my blog for that to work, right?!
“But wait. There’s more.” as they say in advertising.
Yes, you guessed it! It’s that wondrous “Publish to Blog” button!!
With a quick click, @ThreadReaderApp will authenticate and I can authorize it to publish to my WordPress site on my behalf.
I can now publish the entire thread to my own website!!
Now this thread that I’ve published to Twitter will live forever archived on my own website as its own stand-alone blogpost.
I’m not sure how often I’m prone to do this in the future, but I hope we won’t hear that “Why didn’t you just post that on your own website as a blogpost?” as frequently.
With just a button push, I’ll be able to quickly and simply cross-post my Twitter threads on Twitter directly to my website!
I’ll mention for the masses that this publishing functionality is only possible courtesy of a W3C recommendation (aka web standard) known as Micropub.
Because it’s a web standard, @ThreadReaderApp can build the functionality once & it should work on dozens of platforms including @WordPress @Drupal @WithKnown @CraftCMS @Jekyllrb @GetKirby @GoHugoIO @MicroDotBlog among a growing set of others.
Some of these may have built-in or core support for the standard while others may require a simple plugin or module to support this functionality.
Don’t see your platform supported yet? Ask your CMS or platform provider to provide direct support.
There’s lots of open source implementations already out there in various languages and there’s a fantastic test suite available for developers.
I’ll also give a quick shout out to @iAWriter which also just added Micropub support to let people use their editor to post to their websites.
And of course once you’ve realized that your platform supports Micropub to publish to your website, why not try out one of the dozens of other Micropub clients out there?
They support a variety of post or content types from full articles to photos and geolocation to bookmarks. The sky’s the limit.
Some of my favorites are Quill, OwnYourSwarm, Omnibear, and Teacup. And let’s not forget social feed readers like Monocle and Indigenous that let you read and respond to content directly in your feed reader! (I no longer miss Google Reader, now I just feel sorry for them.)
Congratulations again to @ThreadReaderApp for helping to lead the way in the corporate social space for support of the awesomeness that Micropub allows.
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.