From bd248bab2053002a8b3d27fd01be8783fd6f7d93 Mon Sep 17 00:00:00 2001 From: fiatjaf Date: Wed, 10 Jan 2024 07:31:22 -0300 Subject: [PATCH] cleanup NIP-52. --- 52.md | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-) diff --git a/52.md b/52.md index 4ec68369..daaf3ad6 100644 --- a/52.md +++ b/52.md @@ -35,9 +35,6 @@ The list of tags are as follows: * `t` (optional, repeated) hashtag to categorize calendar event * `r` (optional, repeated) references / links to web pages, documents, video calls, recorded videos, etc. -The following tags are deprecated: -* `name` name of the calendar event. Use only if `title` is not available. - ```json { "id": <32-bytes lowercase hex-encoded SHA-256 of the the serialized event data>, @@ -96,9 +93,6 @@ The list of tags are as follows: * `t` (optional, repeated) hashtag to categorize calendar event * `r` (optional, repeated) references / links to web pages, documents, video calls, recorded videos, etc. -The following tags are deprecated: -* `name` name of the calendar event. Use only if `title` is not available. - ```json { "id": <32-bytes lowercase hex-encoded SHA-256 of the the serialized event data>, @@ -210,13 +204,7 @@ The list of tags are as follows: } ``` -## Unsolved Limitations - -* No private events - -## Intentionally Unsupported Scenarios - -### Recurring Calendar Events +## Recurring Calendar Events Recurring calendar events come with a lot of complexity, making it difficult for software and humans to deal with. This complexity includes time zone differences between invitees, daylight savings, leap years, multiple calendar systems, one-off changes in schedule or other metadata, etc.