After a bit of experimentation and tinkering tonight, it appears that one can use their website to create threaded conversations on (and likely other portions of the ) using the IndieWeb syndication strategy of POSSE with backfeed of comments using and Brid.gy. I’d outlined the process using Twitter in the past, and the same principles seem to work well for Mastodon.
Replied to a post by Kathleen FitzpatrickKathleen Fitzpatrick (hcommons.social)

@chrisaldrich Another #IndieWeb question for you! I'm syndicating blog posts from kfitz.info to Mastodon, where they appear from @kfitz@kfitz.info, and then I boost from this account. Replies to @kfitz@kfitz.info appear as comments to the blog post, as desired. But if I reply to the comment on the blog, that reply doesn't syndicate here, so the commenter doesn't know. And if I reply to the comment here, the reply comes from this account (and I'm not yet sure whether it appears as a reply on the blog or not). How do you manage this?

@kfitz I’m not sure that the straightforward functionality you’re looking for exists within the ActivityPub plugin (yet), but it’s certainly something you could potentially file as a feature request.

Since you have other Fediverse accounts you’re using, you might be able to follow the same general pattern I’d documented with Twitter for threading comments between my site and Twitter: https://boffosocko.com/2018/07/02/threaded-conversations-between-wordpress-and-twitter/

Generally, you’d post on your site where it’s seen in the Fediverse via the ActivityPub plugin and/or optionally boosted by your native Mastodon account. Replies to your post (on Mastodon) show up on your site as comments and you reply to them there in your site’s comments section. Then you manually copy/paste the text of your reply from your website into your native Mastodon account and include the comment/reply permalink in that reply. If you’ve got Webmention set up with Brid.gy for Mastodon, replies to your replies on Mastodon should then make their way back to the proper threaded spot in your website’s comments section.

An example of this at work can be seen on my earlier mistake:

Related, I’ve been playing around with mirroring my WP site as an instance with the ActivityPub plugin and have boosted posts with my more broadly followed mastodon.social account the same way you mentioned that you were doing with yours. Somehow I’m anecdotally finding that I get more responses/reactions with native posts that with these boosts. I’m curious what your experience has been with this strategy so far? I’m still just starting my experimentation here, but I do like the fact that I’m able to include richer presentation of wrapped links in my WordPress native posts which are seen in the Fediverse while Mastodon seems to strip them out or not allow them (see an example of this in the post above this reply).

Replied to a thread by John-Mark Gurney, Dan McDonald, and Seth Wright (Twitter)
I’m pretty sure that many within the IndieWeb space have got this working with a variety of software, particularly using Bridgy for the responses. Here’s an outline of how I do it with WordPress https://boffosocko.com/2018/07/02/threaded-conversations-between-wordpress-and-twitter/

I’m always curious to see other implementations.

Replied to Jetpack 9.0 to Introduce New Feature for Publishing WordPress Posts to Twitter as Threads by Sarah Gooding (WordPress Tavern)
Jetpack 9.0, coming on October 6, will debut a new feature that allows users to share blog posts as Twitter threads in multiples tweets. A recent version of Jetpack introduced the ability to import and unroll tweetstorms for publishing inside a post. The 9.0 release will run it back the other way so the content originates in WordPress, yet still reaps all the same benefits of circulation on Twitter as a thread.
It’s awesome to see this feature added and that it expands the ability to do do this sort of workflow directly from one’s website instead of relying on posting to Twitter and relying on ThreadReaderApp to unroll a thread and post it to a WordPress site using the flexible Micropub specification. I’d love to see more POSSE (Post to your Own Site, Syndicate Elsewhere) syndication set ups within WordPress.

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

Replied to a thread by Nicholas Rempel and Adam Greenough (Twitter)
I need to go back and revise it a bit, but I built a bit of UI for doing just this with Webmention: https://boffosocko.com/2017/12/24/adding-simple-twitter-response-buttons-to-wordpress-posts/

The other piece requires being able to thread conversations. Details for that here: https://boffosocko.com/2018/07/02/threaded-conversations-between-wordpress-and-twitter/

Read OMG! Twitter release an OFFICIAL conversations API! by Terence Eden (shkspr.mobi)
One of the most requested Twitter API features is now available – the ability to get replies to a Tweet as a thread.
Long time readers know that I’ve long been a fan of Visualising Twitter Conversations in 2D Space. But up until now you had to use horrible hacks to get the data. As trailed in th...

A Micropub client idea: Liveblogging!

I’ve been thinking about Twitter threads, tweetstorms and liveblogging for the better part of the week, and last night I had an idea that has stuck with me.

With the idea of Micropub allowing the ability to create updates, why couldn’t one build (or even modify) a Micropub client to create an interface to write relatively short updates with (date and timestamps to appear in the text) that, when published, concatenated that new piece of content into a longer piece of running text to send an updated Micropub request to an article or note on a site to allow that article to become an updating liveblog post?

I’m a bit shocked that no one has done it before now, and I suspect that one of the pre-existing micropub clients out there could probably add the functionality as a one day project at an upcoming IndieWebCamp.

I don’t suspect it was the sort of Micropub functionality that Kevin Marks was thinking about doing this weekend, but Noter Live comes pretty close to having a lot of this sort of UI already. Instead of just doing a single Micropub post at the end of a Twitter thread, why couldn’t it do an initial post at the beginning and then update the site with subsequent updates as it goes along while also acting as a means of syndicating the posts to Twitter and then returning those Twitter permalinks as syndication links on the user’s own site?

👓 Kara Swisher interview with Jack Dorsey: Highlights | Recode

Read Kara Swisher interview with Jack Dorsey: Highlights by Kurt Wagner (Recode)
How hard is it to have a conversation on Twitter? So hard even the CEO can’t do it. Kara Swisher’s live-tweeted interview with Jack Dorsey highlighted some of Twitter’s product issues.

Threaded conversations between WordPress and Twitter

I’ve written about threading comments from one WordPress website to another before. I’ve long suspected this type of thing could be done with Twitter, but never really bothered with it or necessarily needed to do it, though I’ve often seen cases where others might have wanted to do this.

For a post today, I wrote on my own site and syndicated it to Twitter and got a reply back via webmention through Brid.gy. This process happens for me almost every day, and this all by itself feels magical.  The real magic however, and I don’t think I’ve done this before or seen it done, was that I replied to the backfed comment on my site inline and manually syndicated to Twitter using a permalink of the form http://www.example.com/standard-permalink-structure/?replytocom=57527#respond, where 57527 is the particular comment ID for my inline comment. (This comment ID can typically be found by hovering over the “Reply” or “Comment” button on one’s WordPress website in most browsers.)

Where to find the comment ID to provide the proper permalink to get properly nested comments backfed to your site.

When a reply to my second syndicated Twitter post came in, Brid.gy properly sent it as a comment to my comment AND nested it properly!

I’ve now got a nested copy of the conversation on my site that is identical to the one on Twitter.

I suspect that by carefully choosing the URL structure you syndicate to Twitter, you’ll allow yourself more control over how backfed comments from Brid.gy nest (or don’t) in your response section on your site.

Perhaps even more powerfully, non-WordPress-based websites could also use these permalinks structures for composing their replies to WordPress sites to have their replies nest properly too. I think I’ve seen Aaron Parecki do this in the wild.

Since the WordPress Webmention plugin now includes functionality for sending webmentions directly from the comments section, I’ll have to double check that the microformats on my comments are properly marked up to  see if I can start leveraging Brid.gy publish functionality to send threaded replies to Twitter automatically. Or perhaps work on something that will allow automatic replies via Twitter API. Hmmm…

Despite the fact that this could all be a bit more automated, the fact that one can easily do threaded replies between WordPress and Twitter makes me quite happy.

Thread onward!

For more on my IndieWeb explorations with Twitter, see my IndieWeb Research page.

Read Nice Threads (blog.twitter.com)
At Twitter, we have a history of studying how people use our service and then creating features to make what they’re doing easier. The Retweet, '@reply', and hashtag are examples of this. A few years ago we noticed people creatively stitching Tweets together to share more information or tell a longer story – like this. We saw this approach (which we call “threading”) as an innovative way to present a train of thought, made up of connected but individual elements.