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

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.
Very cool!
In that case, maybe this?
@ThreadReaderApp has support for the Micropub Spec so you can publish Twitter threads directly to your blog. (Or perhaps do both methods?)
(boffosocko.com/2022/06/21/558…)
boffosocko.com/2020/05/28/thr…
@kfitz Oops, my version had the wrong initial link, it should be https://boffosocko.com/2016/12/05/how-to-own-display-your-twitter-archive-on-your-website-in-under-10-minutes/. But perhaps it will go to your “other” question, whose answer is coming shortly, and perhaps with a small experiment that’s demonstrated here.https://boffosocko.com/2022/12/17/55812895/?replytocom=400346#respond
How to Own & Display Your Twitter Archive on Your Website in Under 10 Minutes
@liztai while there aren’t a lot of guides for WP.com, part of the reason is that by the time you’ve paid for an account capable of having plugins/extensions you can probably pay someone to do the work.