On a reply post, it is common practice (possibly established by Twitter on tweet permalinks) to display the context of what the post is in reply to, including linking to that original post with rel-in-reply-to.
Why show reply contexts?
How should reply contexts be marked up?
<div class="h-entry"> <div class="p-in-reply-to h-cite"> <p class="p-author h-card">Emily Smith</p> <p class="p-content">Blah blah blah blah</p> <a class="u-url" href="permalink"><time class="dt-published">YYYY-MM-DD</time></a> <p>Accessed on: <time class="dt-accessed">YYYY-MM-DD</time></p> </div> <p class="p-author h-card">James Bloggs</p> <p class="e-content">Ha ha ha too right emily</p> </div>
Why use h-cite instead of h-entry for reply contexts?
Why not use h-entry in addition?
There is a broad spectrum of reply-context presentation that can be roughly ordered in terms of fidelity and difficulty, from simplest/easiest to richest (silo-parity) and most challenging.
Since a reply has to be in-reply-to to something (a URL), the simplest reply context is to simply show the URL (hyperlinked of course) of the original with perhaps a text label like:
In reply to: hyperlinked-URL-of-original
IndieWeb Examples of URL-only :
The next easiest thing to add is the icon (or avatar) of the author of the original post.
For example, replies to tweets can retrieve the icon purely by inspecting the URL for the first path segment for the Twitter username, and then embedding a dynamic image redirect URL, e.g. https://twitter.com/benwerd/profile_image: See Twitter: Profile Image URLs for details.
Replies to indieweb posts can retrieve the icon from a nicknames-cache.
IndieWeb Examples of icon plus URL:
The original's published date is the next interesting (and slightly harder) thing to retrieve and display in a reply-context. With this step, an implementation must retrieve the original post and determine its "dt-published" (e.g. from parsing its h-entry).
The date and time of the original should be displayed and hyperlinked to the original's URL.
IndieWeb Examples of icon URL and dt-published:
Determining the author's name and their icon (more broadly/reliably than above), requires implementing the authorship algorithm on the original post, which requires more work than just parsing it for its h-entry as above.
IndieWeb Examples of icon URL dt-published and author name:
Lastly, the content of an original post is the hardest thing to display well in a singular reply-context, due to numerous additional variables. Some challenges:
IndieWeb Examples of icon URL dt-published author name and original content:
Main article: reply-thread
Popular silos (e.g. Twitter) display an entire thread of reply-contexts of originals/replies from the tweet that you're replying to, and if it was a reply itself, what it replies to etc. on up through the original tweet at the start of the thread.
IndieWeb Examples of icon URL dt-published author name original content for the entire reply chain up through the original post that started the thread:
Main article: reply-context-examples
In order of deployment:
of silo posts
Reply contexts where the original is on a silo may sometimes need or deserve special treatment.
If you reply to a silo post where the silo does not mark up their HTML pages with h-entry, (e.g. post a comment on your own site, and the POSSE it to an Instagram post), you will need to do further processing in order to display the reply context as high fidelity as other indieweb posts.
You may find the following tools useful:
Though one advantage of storing and showing a reply-context is freezing the original context of what you're replying to, it may make sense to accept some updates.
Main article: reply-context-examples#Silo_Examples