nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-20 06:45:49 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

add self-reporting

Browse Source
This commit is contained in:
dskvr 2023-12-30 22:17:31 +01:00
parent 1bc98b5cdb
commit 9a3c5c0230
1 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
66.md
View File

@ -2,7 +2,7 @@
`draft` `optional` `draft` `optional`
This NIP defines three event kinds, `10066`, `30066` and `1066`. This NIP defines four event kinds, `10066`, `30066`, `10066` and `1066`.
## `10066`: "Relay Monitor" Events ## `10066`: "Relay Monitor" Events
@ -106,7 +106,7 @@ Tags should be used to represent the Relay's abilities and meta at any given poi
["rtt", "read", "35", "60", "46"], ["rtt", "read", "35", "60", "46"],
["rtt", "write", "701", "497", "508"] ["rtt", "write", "701", "497", "508"]
``` ```
- `"count" == tagCount[0]` Meta values for arbitrary counts related to a relay. `tagCount[1]` is the value expressed as the string representation of an integer or float. `tagCount[2]` is the key and describes the count, such as `total_users` or `total_events`. Counts **should** only be included when representing unique or computationally expensive counts, not ones that can be easily achieved via NIP-XX counts, via NIP-XX searches or other filters. There **may** be zero (0) to many count tags. - `"count" == tagCount[0]` Meta values for arbitrary counts related to a relay. `tagCount[1]` is the value expressed as the string representation of an integer or float. `tagCount[2]` is the key and describes the count, such as `total_users` or `total_events`. Counts **should** only be included when representing unique or computationally expensive counts, not ones that can be easily achieved via `NIP-45` counts. There **may** be zero (0) to many count tags.
``` ```
["count", "total_events", "502341"], ["count", "total_events", "502341"],
@ -283,6 +283,14 @@ Any test results that cannot be expressed through `NIP-66` **should** be ammende
10. **Data-Driven Relay Selection**: Make informed choices about which relays to connect to, based on comprehensive metadata including user counts, event frequencies, network types and more. 10. **Data-Driven Relay Selection**: Make informed choices about which relays to connect to, based on comprehensive metadata including user counts, event frequencies, network types and more.
## `10066`: "Self-Reported Relay Statuses"
### Summary
A `30066` event with an `r` tag instead of a `d` tag.
### Purpose
For relays to self-report
## `1066`: "Relay Status History" Events ## `1066`: "Relay Status History" Events
### Summary ### Summary