From ac80fdb755480544d62e499e7c91d777997bc9d6 Mon Sep 17 00:00:00 2001 From: Gary R Krause Date: Tue, 14 Feb 2023 19:03:02 -0500 Subject: [PATCH] MUST have content for the event so clients have something to display. --- 69.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/69.md b/69.md index 118bffa..3df48d7 100644 --- a/69.md +++ b/69.md @@ -12,7 +12,7 @@ This NIP defines ways source control (git, etc.) context can be stored using nos `kind: 69` uses tag the `b` tag to identify the base repository. The value of this tag SHALL be a list of remote source control repository URLs. These URLs MAY be a nostr relay URL or a traditional repository URL. The first URL in this list SHALL be considered the "default" repository URL for the context. -The `content` of a Source Control Event MAY contain a text description of the event or other information about the repository. +The `content` of a Source Control Event MUST contain a text description or summary of the base repository. This enables clients that don't specifically handle this kind to display meaningful text in their UI. ```json { @@ -21,7 +21,7 @@ The `content` of a Source Control Event MAY contain a text description of the ev "tags": [ ["b", , , ...], ], - "content": , + "content": , ... ```