Why make it difficult when you can make it simple ?<div><br></div><div>We could create a new XEP by looking how the IMAP protocol works. Each subscribed user of a node can send a little "read" stanza to the server. Then the next time eh will request the items of the the node, the server can add a little tag to show him that this content has already been read.</div><div><br></div><div>We can also add specific stanza like :</div><div>- Mark all read</div><div>- Mark read until this specific date</div><div><br></div><div>But this should be resolved server side and I personnaly dont like the idea to track these data with an another node, we will have serious consistancy issues (like we already have with the Bookmark XEP).</div><div><br></div><div>edhelas<br><br>On lun., juil. 28, 2014 at 7:18 , Ashley Ward <firstname.lastname@example.org> wrote:<br>
<blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;">On 28 Jul 2014, at 18:14, Simon Tennant <email@example.com> wrote:
<blockquote> IMHO this is something that should be solved in that node rather than running parallel nodes or adding a PEP dependency.
Almost like returning a different metadata key-value pair to each requesting JID.
Now you mention it, it feels like it’s actually metadata on the subscription (rather than the node), so perhaps storing it in the subscription configuration might be more appropriate?