nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-18 19:23:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

update to nip01 to specify syntax for usernames.

Browse Source
This commit is contained in:
Robert C. Martin 2022-06-05 14:32:01 -05:00 committed by fiatjaf
parent 947fe3044a
commit f367d820d4
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
01.md
View File

@ -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: <string>, 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.
- `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 epression). 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).
- `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.