@Ron I don’t know the best way of referring to a single item—unless it is an initial post, the item (comment/reply) is probably going to require some context to make any sense, and it’s probably not a good idea in today’s toxic socio-intellectual climate to encourage looking at things devoid of context ;-)
So to show a single item from a Conversation, Manton would have to engineer a whole new “page type” to show just the one item plus somehow indicate its context. For now, on the web, you can take the item ID (the number at the end of the URL, e.g.
2870858 for this comment of yours
micro.blog/Ron/2870858 I am replying to) and append it to the URL with an HTML anchor, like this
#post_div_2870858 (full URL is then
micro.blog/Ron/2870858#post_div_2870858) to make browsers jump to the actual post when you want to reference it elsewhere, e.g. see Ron’s comment here. That’s…better, but it requires a bit of extra work on the part of the person wanting to link to it, too—witness I forgot to do it in the GitHub issue last night—and doesn’t really get you the single item.
(I believe in the past it was not possible to see the entire Conversation via the intial post—you could only see the Conversation via an existing reply, or see the initial post on its own—which led to fractured conversations before Manton “merged” the two. As far as I can recall, the timestamp on intial posts has always* pointed to post on its source blog, and the timestamp on replies has always* pointed to the Conversation view, with the appropriate reply being highlighted with a grey background since sometime last year.)
* Since December 2017, at least.