You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some kind of locking is probably required to implement a use case like reactions (thumbs up/down etc., #228 (comment)) correctly. Use cases like implementing comments (with versions) might benefit too.
Optimistic locking seems like a reasonable enough solution.
(Note we don't need this for feeds/entries because they're more or less eventually consistent.)
OTOH, reserved keys are for end-user-facing features...
But, is it reader's responsibility to control how they are shown? Presumably, for a use case like the one described above, the user would not see those tags directly, but see them rendered as 👍, 👎 anyway.
The text was updated successfully, but these errors were encountered:
Some kind of locking is probably required to implement a use case like reactions (thumbs up/down etc., #228 (comment)) correctly. Use cases like implementing comments (with versions) might benefit too.
Optimistic locking seems like a reasonable enough solution.
(Note we don't need this for feeds/entries because they're more or less eventually consistent.)
Relevant resources:
Open questions:
.reader.search
in Entry tags and metadata #228 (comment).The text was updated successfully, but these errors were encountered: