comment-notifications

From IndieWeb
Jump to: navigation, search

Scenario

  1. aaronpk created a new post [1]
  2. eschnou created a reply post [2] and:
    1. and sent a pingback to aaronpk's server
    2. aaronpk's server pulled in the reply below the original post showing the note
  3. barnabywalters replied to eschnou [3] and:
    1. sent a pingback to eschnou's server
    2. eschnou's server pulled in the reply below the original post

The missing piece is that aaronpk was interested in getting notifications of follow-up posts to eschnou's reply, and now has no idea that barnaby commented on the thread without .

Option 1. Subscribing to comments

aaronpk's site can subscribe to the comment feed on eschnou's post

  • This assumes eschnou publishes follow-up comments as h-entrys

For aaronpk's site to be notified of all conversations in the thread, it would subscribe to the comments feed of any URL that sent a webmention

Option 2. Webmention

When barnaby created his post [4] he could have recognized he was replying to a post that had an "in-reply-to" URL, and sent webmentions to both.

  • This would only work if barnaby also published the in-reply-to URL of eschnou's post so that aaron's site could parse it out.

My guess is this would quickly get out of hand and require much more careful markup to make work properly. Aaronparecki.com 14:54, 29 May 2013 (PDT)

An alternative would be for eschnou to re-ping aaronpk since the reply has been 'updated' (in this case, new comments added). Up to aaronpk to parse it and discover there are replies (marked as comments) and to display them as threaded conversation. --Eschnou.com 00:59, 30 May 2013 (PDT)

Option 3. Conversation Threading

App.net has the concept of "threads", where each post can be part of a conversation thread.

  • If a post is a parent, the thread ID is the same as the post ID [5]
  • If a post is a reply, the thread ID is the top post that started the thread [6]

This concept could be used for IndieWeb comments as well.

In the example above, if both eschnou and barnaby's posts linked to the post on aaronparecki.com as the "parent" or "conversation starter", all future posts in the thread would also use the same URL on aaronparecki.com to be a part of that conversation.

http://eschnou.com/entry/aaronpareckicom-duh-i-actually-never-realized-there-was-hover-text-in-xk-62-24947.html

<p>In reply to <a href="http://aaronparecki.com/notes/2013/05/21/1/xkcd" class="u-in-reply-to u-thread">aaronparecki.com</a></p>

http://waterpigs.co.uk/notes/1469/

<a class="u-url" rel="in-reply-to" href="http://eschnou.com/entry/aaronpareckicom-duh-i-actually-never-realized-there-was-hover-text-in-xk-62-24947.html">
	<time class="dt-published" datetime="2013-05-29T22:01:13+02:00">1 hour ago</time>
</a>

<a href="http://aaronparecki.com/notes/2013/05/21/1/xkcd" class="u-thread">view conversation</a>

In order to handle notifications of updates, anybody that added a post to the conversation would simply send a webmention to aaronparecki.com as before.

Anybody who wanted to get updates on the conversation could subscribe to the URL on aaronparecki.com, and aaron's server would send notifications of updates. This could use a mechanism similiar to PubSubHubbub, but would not require it since polling the URL would work as well (just like with PuSH).


Related

  • The Salmon protocol has a way of sending comments upstream. Might want to take a look at it and see if webmention could support something like it.
  • comment
  • webmention
  • feed