From 1bc98b5cdbd074c69f27646438cb417a78837639 Mon Sep 17 00:00:00 2001 From: dskvr Date: Sat, 30 Dec 2023 20:30:17 +0100 Subject: [PATCH] fix as/asn tags and verbage for 1066 --- 66.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/66.md b/66.md index 5902e93a..19c33ad0 100644 --- a/66.md +++ b/66.md @@ -142,8 +142,10 @@ Tags should be used to represent the Relay's abilities and meta at any given poi - `as`/`asn` the relay ISPs "Autonomous System (Number)" ``` - [ "as", "QUAD9-AS-1, CH" ] - [ "asn", "19281" ] + [ "L", "as" ] + [ "l", "QUAD9-AS-1, CH", "as" ] + [ "L", "asn" ] + [ "l", "19281", "asn" ] ``` - String values from `NIP-11` using dot notation, for example @@ -290,10 +292,10 @@ Any test results that cannot be expressed through `NIP-66` **should** be ammende Relay History events can contain any of the tags defined for kind `30066` (Including the `d` tag which is used to filter these events by relay). There is one new indexable tag #### Special Considerations -- These events can potentially store a lot of data. +- These events can potentially demand a lot of disk space if not used wisely. #### Guidelines -Tags containd with this event should only be included when their values have changed compared to the last event. If there have been no changes, then the event should not be published. +Tags representing less-volatile values, for instance `nip11.software` vs `rtt`, contained with this event should only be included when their respectiive values have changed compared to the last Relay History event of the same `d` tag. If there have been no changes, then the event should not be published. ##### Use Cases - Generate a time series from one or many data-point(s) for a specific relay.