already-read flag is needed to follow delayed comments and mentions.

ZeroHello just displays users' activity events on the right pane in the order of posted timestamp of each activity, so that the delayed comments or mentions which were uploaded a few hours ago locally but updated now are displayed at the bottom of the event list.

So, the user loses his chance to notice the events.

We could add 'read check' field which might contain all the user list just like upvote field does.
And then, ZeroHello could filter the events (posts, comments, mentions) where the user didn't check the 'read check' field. Of course, this has to be reversible by not filtering and unchecking it.

Moreover, filtering feature will just mark some of all the events, or will hide the filtered one in the display.

http://127.0.0.1:43110/Me.ZeroNetwork.bit/?Profile/1SunAWK2VUT9GQK32MpwRfFPVgcBSJN9a/16dEowtNbV89NxPcDrAKkmnuXtiJVoVcDm/leftside@zeroid.bit

sos4sos@riseup.net 2018-03-07 17-10-36

The issue identifies ZeroHello's right-pane activity event list as the entry point. First clarify whether read checks should hide or mark events and how users reverse that choice; then inspect the existing posts, comments, and mentions display. Done means delayed events remain discoverable and read filtering is reversible.

Written by the indexing model from the issue text.