IndieWeb idea for the extension of ThreadReaderApp

I’d love it if ThreadReaderApp had the ability to authenticate into my personal website and publish a copy of my own tweetstorms into my blog using Micropub

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. 

Published by

Chris Aldrich

I'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, IndieWeb, theoretical mathematics, and big history. I'm also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.

37 thoughts on “IndieWeb idea for the extension of ThreadReaderApp”

  1. I’d love it if ThreadReaderApp had the ability to authenticate into my personal website and publish a copy of my own tweetstorms into my blog using Micropub
    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. 

    Syndicated copies:

  2. We have been receiving requests to allow embedding of unrolled threads automatically to blogs and other publications, including @ChrisAldrich‘s proposal below. Curious, how many folks are interested in this? And if so, what blogging platforms (eg WordPress?) should be supported?

  3. I really like this idea Chris, although with the introduction of threads, I wish there was a means of embedding a Twitter thread out of Twitter itself. I assume that when you include multiple tweets in a reply via your site that you are manually embedding each one individually.

    1. Yes, typically I’m embedding mine manually, though I don’t do it very often as they don’t make it easy at all. I might say it’s even gotten harder as of about 6 months ago when they made some changes. The problem with threads often is the branching nature of the conversation and presenting that in a useful way.

  4. OMG! I can’t imagine what readers would do if my blog was suddenly flooded with 280 character messages.

    1. I love the snark!

      (But also just in case I’m missing your meaning or you’re not understanding the intent, this isn’t meant to push lots of Twitter content to your site. It’s meant to allow people to use Twitter to create tweetstorms, and then when they’re done, have ThreadReaderApp to bundle that tweetstorm into a blog post and post just that to their site. NoterLive.com is the only thing I’m aware of that comes close, but there you have to do the cut/paste to your site at the end–though perhaps Kevin will implement the Micropub portion at IWC London coming up?)

  5. I’m happy to see the response so far. I hope it rises above the threshold for wanting to build it into ThreadReaderApp as a feature.
    I’ll note, hopefully for ease of implementation, that a Micropub solution will already allow you to post to WordPress, Drupal, WithKnown, Craft, Jekyll, Kirby, Hugo, Blot, Micro.blog and others.
    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.)
     

Leave a Reply

Your email address will not be published. Required fields are marked *