From c8a95a0968acb4ba463b6395d93bc667ca022705 Mon Sep 17 00:00:00 2001 From: DZ Date: Fri, 7 Oct 2022 22:16:17 +0200 Subject: [PATCH] Update 01.md fix typo --- 01.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/01.md b/01.md index e0def1e..6a5c2ac 100644 --- a/01.md +++ b/01.md @@ -98,7 +98,7 @@ 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. - * Where `` is a string that matches the pattern: `[\w+\-]` (java regular epression). Or, in other words, a sequence of the following + * Where `` is a string that matches the pattern: `[\w+\-]` (java regular expression). 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).