NIP-52E/52R: private calendar events, busy lists and recurring event support#2351
Open
geralt-debugs wants to merge 2 commits into
Open
NIP-52E/52R: private calendar events, busy lists and recurring event support#2351geralt-debugs wants to merge 2 commits into
geralt-debugs wants to merge 2 commits into
Conversation
Author
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
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.
Introduces two companion extensions to NIP-52:
NIP-52R - Recurring Events
Extends NIP-52 with RRULE-based recurrence using L/l label tags inside event payloads.
NIP-52E - Private Calendar Events
Adds a privacy layer on top of NIP-52 using a view key pattern (NIP-44 self-encryption):
Only the d tag is public; all event content lives in the encrypted content field. Participants receive the
viewKey (nsec) via gift wrap and can decrypt independently of the author.
Full protocol flows are specified for: creating a private event, receiving and accepting an invitation, and
loading calendar events at startup.
Closing #2027 in favour of this