Another interesting option is @KevinMarks’s noterlive.com which will compile your threaded tweets for cutting/pasting HTML to your site. Perhaps one day he’ll add Micropub functionality as well?
I’m hoping that future versions of this provide the Twitter permalinks for the syndicated copies there to be returned to my WordPress site for storage. In my case, I’m using the simple Syndication Links plugin which has storage and/or finds the storage location in WordPress to allow for the display of those permalinks in my post to indicate where I’ve syndicated the copies. This does two things: it’s a reminder of where my content lives elsewhere on the web (especially if I later want to go back and delete them, or to delete them if I’m deleting or making the original post private/unpublished) and it allows services like Brid.gy to find my original post and backfeed replies to the Twitter versions back into the comments section of my post using the Webmention spec (via the Webmention plugin and the Semantic Linkbacks plugin).
One of my favorite is Kevin Marks’ Noter Live (open source) which is great for live tweeting and creating long threads quickly, especially at conferences. When you’re done, it’s kept a record of everything which you can quickly cut/paste as HTML into your website for an instant archive post.
Another option if your website supports the Micropub spec (perhaps with a plugin?) ThreadReaderApp recently added support to let you unroll the thread and you can go to your account and authenticate to your website and post the thread with one click.
I’ll also note that WordPress’ Gutenberg just added the ability to unroll threads to websites built with it as well.
In addition to general public use, these could actually be the backbone of an interesting journalistic live notebook for reporters in the field who could quickly compile/archive their threads for expanded articles later on.
Turn your recent Twitter thread into your next blog post.
I'm working on a tool that will convert a twitter thread to a post for my blog. I got the idea from @ChrisAldrich's tweet . // @vrypan→
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 ...
I ran across a Chrome extension for highlights, annotations, and tagging tonight. It’s called Learning Paths. It works roughly as advertised for creating and saving highlights and annotations online. With a social silo log in process (I didn’t see an email login option), you’ve quickly got an account on the service.
You can then use the extension to highlight, tag, and annotate web pages. One can export their data as a .csv file which is nice. They’ve also got an online dashboard which displays all your data and has the ability to see public data from other users as well.
One of the interesting pieces they support is allowing users to tweet a thread from all their highlights of a piece online. Upon seeing this I thought it might make a useful feature for getting data into one’s personal wiki, website, or digital garden, particularly now that ThreadReaderApp supports posting unrolled Twitter threads to one’s Micropub enabled website.
So the workflow goes something like this (with links to examples of my having tried it along the way):
While this works relatively well, there are a few drawbacks:
While the idea works roughly in practice, it isn’t as optimal as the workflow or data fidelity I’ve found in using more robust tooling like that found in Hypothes.is for which I’ve also built a better UI on my website.
Still others, might appreciate the idea, so have at it! I’d love to see others’ ideas about owning their highlights, annotations, and related data in a place they control.
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.)