Katherine, The reply thing from my own site to your tweet is my favorite part of what IndieWeb enables! For me it’s really the whole ball of wax. It shouldn’t matter what platform I’m on and which platform you’re on–we should be able to communicate across domain names and across different CMSes and platforms, right!!? This is what allows us to own all of our data.

The short of it is that I write my reply on my own website and syndicated it (via POSSE) to your tweet on Twitter. I then rely on Brid.gy to provide the backfeed of your comment back to my reply. Now I’m able to write another reply on my site and thread it into the conversation seamlessly. Except that I’m providing the backlinks to my site (for the characters over 280), there are ways I could do this and you wouldn’t even be aware of the duplication of the two separate threads.

If you’re interested in the slightly longer story, I’ve documented it before here: Threaded conversations between WordPress and Twitter.

As I’m thinking of it now, I sort of wonder if, for better UI and accessibility sake, I should be using my URL fragments to have the link for the continuation of the conversation (ie at [more…]) be pointing to the exact point at which the conversation actually continues on the resulting page? (Perhaps I’ll try some experiments to see how it might look/work…)

Syndicated copies: