From f367d820d48b79f42770496087f79b0d60691ebd Mon Sep 17 00:00:00 2001 From: "Robert C. Martin" Date: Sun, 5 Jun 2022 14:32:01 -0500 Subject: [PATCH] update to nip01 to specify syntax for usernames. --- 01.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/01.md b/01.md index 8b818282..8bf7fc3f 100644 --- a/01.md +++ b/01.md @@ -97,7 +97,10 @@ This NIP defines no rules for how `NOTICE` messages should be sent or treated. ## Basic Event Kinds - - `0`: `set_metadata`: the `content` is set to a stringified JSON object `{name: , about: , picture: }` describing the user who created the event. A relay may delete past `set_metadata` events once it gets a new one for the same pubkey. + - `0`: `set_metadata`: the `content` is set to a stringified JSON object `{name: , about: , picture: }` describing the user who created the event. A relay may delete past `set_metadata` events once it gets a new one for the same pubkey. + * Where `` is a string that matches the pattern: `[\w+\-]` (java regular epression). Or, in other words, a sequence of the following + characters: `[a-zA-Z_\-0-9]`.
+ Thus `George-Washington-1776` is a valid ``, but `George Washington` is not. Clients may reject metadata that does not comply. - `1`: `text_note`: the `content` is set to the text content of a note (anything the user wants to say). - `2`: `recommend_server`: the `content` is set to the URL (e.g., `https://somerelay.com`) of a relay the event creator wants to recommend to its followers.