Add membership state consistency section to 43.md#2267
Open
mostafa-khaldi wants to merge 4 commits intonostr-protocol:masterfrom
Open
Add membership state consistency section to 43.md#2267mostafa-khaldi wants to merge 4 commits intonostr-protocol:masterfrom
mostafa-khaldi wants to merge 4 commits intonostr-protocol:masterfrom
Conversation
Clarify membership state consistency requirements for relays regarding user membership events.
Member
|
Why not just keep the kind:8000 and delete it when a member is removed? @staab |
Member
|
I think tbis should be left up to relays. Ideally, all events would be available, creating a complete history of membership at any time in the past, but that could be abridged as an optimization. This PR can just be solved by doing |
This NIP introduces a new event kind (10164) for payment gateways, allowing content creators to define payment methods, pricing models, and subscription rules for paid content. It enhances usability with labels for methods and plans while supporting multiple payment providers.
Add NIP-63a: Minimal Payment Gateway Descriptor
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
3 participants
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.
This change clarifies that relays should remove the opposing membership event when publishing a new one (
8000for add,8001for remove).The goal is to keep the membership state simple and unambiguous. If both events exist for the same pubkey, clients have to scan through all returned events to determine the latest state, especially in cases where a user joins and leaves multiple times. By ensuring only one state event exists at a time, clients can immediately know whether a user is currently a member or not.
It also helps reduce the number of stored events on relays by preventing redundant membership state history from accumulating.