diff options
| author | Mohammed Alotaibi <a@4rs.nl> | 2025-02-04 15:50:20 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-02-04 21:50:20 +0900 |
| commit | 4e564ba4d99f247a6c2c1734d01a12c9bda8c1db (patch) | |
| tree | 10ca988619b6b43f3a25c84736833f066b893278 /31.md | |
| parent | a70e49e21cf286889568ce034011a29ba994faa0 (diff) | |
Fix NIPs refs (#1740)
Diffstat (limited to '31.md')
| -rw-r--r-- | 31.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -12,4 +12,4 @@ The intent is that social clients, used to display only `kind:1` notes, can stil | |||
| 12 | 12 | ||
| 13 | These clients that only know `kind:1` are not expected to ask relays for events of different kinds, but users could still reference these weird events on their notes, and without proper context these could be nonsensical notes. Having the fallback text makes that situation much better -- even if only for making the user aware that they should try to view that custom event elsewhere. | 13 | These clients that only know `kind:1` are not expected to ask relays for events of different kinds, but users could still reference these weird events on their notes, and without proper context these could be nonsensical notes. Having the fallback text makes that situation much better -- even if only for making the user aware that they should try to view that custom event elsewhere. |
| 14 | 14 | ||
| 15 | `kind:1`-centric clients can make interacting with these event kinds more functional by supporting [NIP-89](https://github.com/nostr-protocol/nips/blob/master/89.md). | 15 | `kind:1`-centric clients can make interacting with these event kinds more functional by supporting [NIP-89](89.md). |