nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-22 08:25:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update 01.md

Browse Source 
fix indentation
This commit is contained in:
DZ 2022-10-07 22:20:03 +02:00 committed by William Casarin
parent 147cd0a2ea
commit 6d86133118
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
01.md
View File

@ -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: <username>, about: <string>, picture: <url, string>}` 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 `<username>` is a string that matches the pattern: `[\w+\-]` (java regular expression). Or, in other words, a sequence of the following
* Where `<username>` 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]`. <br>
Thus `George-Washington-1776` is a valid `<username>`, 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).