Read status 2#1405
Closed
staab wants to merge 7 commits into
Closed
Conversation
Closed
Open
Member
Author
|
I had this in production for a while, but it was pretty error prone, and resulted in notification badge whack-a-mole with old events that came in late. I think it could still work, but maybe a simpler timestamp-based solution would be better. Removed from coracle in coracle-social/coracle#504 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Another attempt to solve interoperable read statuses. This one combines the timestamp-based approach with the event-id based approach in #933. It uses e tags, not a tags to allow clients to differentiate versions of replaceable events. It uses replaceable events of a few different kinds to reduce storage requirements. It allows for only private read receipts in order to avoid leaking conversation metadata.