nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-10 06:09:08 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix formatting

Browse Source
This commit is contained in:
sandwich 2024-01-16 17:17:28 +00:00
parent 26ef08c90b
commit 913dd3a018
1 changed files with 3 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
66.md
View File

@ -13,7 +13,7 @@ An event that contains data about a relay. These events are self-reported by rel
### Purpose ### Purpose
An event that makes relays discoverable. An event that makes relays discoverable.
## Schema ### Schema
#### `event.content` #### `event.content`
**Should** be empty. **Should** be empty.
@ -89,8 +89,8 @@ Tags should be used to represent the Relay's abilities and meta at any given poi
- String values from `NIP-11` using dot notation, for example - String values from `NIP-11` using dot notation, for example
``` ```
[ "L", "nip11.tags" ] [ "L", "nip11.tags" ]
[ "l", "sfw-only" ] [ "l", "sfw-only", "nip11.tags" ]
[ "l", "bitcoin-only" ] [ "l", "bitcoin-only", "nip11.tags" ]
[ "L", "nip11.language_tags" ] [ "L", "nip11.language_tags" ]
[ "l", "en", "nip11.language_tags" ] [ "l", "en", "nip11.language_tags" ]
[ "l", "en-419", "nip11.language_tags" ] [ "l", "en-419", "nip11.language_tags" ]
@ -162,10 +162,6 @@ _**It adds some additional tags**_
["rtt", "write", "701", "497", "508"] ["rtt", "write", "701", "497", "508"]
``` ```
- `"e" === tagE[0]` An association to another standard nostr event (`0/1/2/4-9999` kind-range). An example would be an event containing the most recent check log or an archival event representing the check. Such a reference may contain duplicate or ommitted tags from a `30066` event.
- `"a" === tagE[0]` An association to another replaceable nostr event. An example would be an event containing the most recent check log or an archival event representing the check. Such a reference may contain duplicate or ommitted tags from a `30066` event.
#### Methodology #### Methodology
A Relay Monitor publishes `30066`` events exclusively when a relay is operational. This approach ensures that the last known active state of the relay is maintained and recorded. Based on this data, several inferences can be drawn about the relay's status and characteristics A Relay Monitor publishes `30066`` events exclusively when a relay is operational. This approach ensures that the last known active state of the relay is maintained and recorded. Based on this data, several inferences can be drawn about the relay's status and characteristics