renames nicknames to petnames

This commit is contained in:
Vitor Pamplona 2024-02-14 15:01:55 -05:00
parent 3ff65d1d64
commit a401682a58

14
81.md
View File

@ -19,11 +19,11 @@ Example of Public Status
"kind": 30382,
"tags": [
["d", "<randomUUID>"],
["n", "Clients"],
["n", "Developers"],
["n", "Client List"],
["n", "Special Holidays List"],
["p", "<pubkey>", "relay"],
["trust_level", "1"],
["nickname", "<My buddy>"],
["petname", "<My buddy>"],
["summary", "<Summary of the relationship>"]
],
"content": "",
@ -38,12 +38,12 @@ Example of Private Status
"kind": 30382,
"tags": [
["d", "<randomUUID>"],
["n", "Clients"],
["n", "Clients List"],
["n", "6064460175057025"], // see private n-tags below
],
"content": nip44Encrypt(JSON.stringify([
["p", "<pubkey>", "relay"],
["nickname", "<My buddy>"],
["petname", "<My buddy>"],
["summary", "<Summary of the relationship>"],
["nip82secret", "<secret used to decrypt medical data for this pubkey>"]
])),
@ -51,7 +51,7 @@ Example of Private Status
}
```
`nickname` SHOULD be used instead of the person's display name in all interfaces
`petname` SHOULD be used instead of the person's display name in all interfaces
Profile screens MAY display the summary of the relationship and allow the user to change the tags of this event.
@ -72,7 +72,7 @@ Clients MAY hide human readable `n`-tags behind a code and list their code maps
"kind": 10008,
"content": nip44Encrypt(JSON.stringify([
["map", "<Code used in other events>", "<Human readable name>"],
["map", "Clients", "Clients"], // public list of my Clients
["map", "Clients List", "Clients List"], // public list of my Clients
["map", "6064460175057025", "Idiots"] // private list of idiots
])),
// ...other fields