upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--01.md2
-rw-r--r--04.md2
-rw-r--r--09.md2
-rw-r--r--11.md2
-rw-r--r--13.md2
-rw-r--r--17.md2
-rw-r--r--26.md2
-rw-r--r--29.md2
-rw-r--r--40.md2
-rw-r--r--42.md2
-rw-r--r--43.md2
-rw-r--r--45.md2
-rw-r--r--46.md2
-rw-r--r--50.md2
-rw-r--r--59.md2
-rw-r--r--62.md2
-rw-r--r--66.md2
-rw-r--r--70.md2
-rw-r--r--77.md2
19 files changed, 19 insertions, 19 deletions
diff --git a/01.md b/01.md
index 1f56427..eb9f60c 100644
--- a/01.md
+++ b/01.md
@@ -4,7 +4,7 @@ NIP-01
4Basic protocol flow description 4Basic protocol flow description
5------------------------------- 5-------------------------------
6 6
7`draft` `mandatory` 7`draft` `mandatory` `relay`
8 8
9This NIP defines the basic protocol that should be implemented by everybody. New NIPs may add new optional (or mandatory) fields and messages and features to the structures and flows described here. 9This NIP defines the basic protocol that should be implemented by everybody. New NIPs may add new optional (or mandatory) fields and messages and features to the structures and flows described here.
10 10
diff --git a/04.md b/04.md
index a561a2f..107d872 100644
--- a/04.md
+++ b/04.md
@@ -6,7 +6,7 @@ NIP-04
6Encrypted Direct Message 6Encrypted Direct Message
7------------------------ 7------------------------
8 8
9`final` `unrecommended` `optional` 9`final` `unrecommended` `optional` `relay`
10 10
11A special event with kind `4`, meaning "encrypted direct message". It is supposed to have the following attributes: 11A special event with kind `4`, meaning "encrypted direct message". It is supposed to have the following attributes:
12 12
diff --git a/09.md b/09.md
index 23ffeab..f061464 100644
--- a/09.md
+++ b/09.md
@@ -4,7 +4,7 @@ NIP-09
4Event Deletion Request 4Event Deletion Request
5---------------------- 5----------------------
6 6
7`draft` `optional` 7`draft` `optional` `relay`
8 8
9A special event with kind `5`, meaning "deletion request" is defined as having a list of one or more `e` or `a` tags, each referencing an event the author is requesting to be deleted. Deletion requests SHOULD include a `k` tag for the kind of each event being requested for deletion. 9A special event with kind `5`, meaning "deletion request" is defined as having a list of one or more `e` or `a` tags, each referencing an event the author is requesting to be deleted. Deletion requests SHOULD include a `k` tag for the kind of each event being requested for deletion.
10 10
diff --git a/11.md b/11.md
index 0497883..26b5c26 100644
--- a/11.md
+++ b/11.md
@@ -4,7 +4,7 @@ NIP-11
4Relay Information Document 4Relay Information Document
5-------------------------- 5--------------------------
6 6
7`draft` `optional` 7`draft` `optional` `relay`
8 8
9Relays may provide server metadata to clients to inform them of capabilities, administrative contacts, and various server attributes. This is made available as a JSON document over HTTP, on the same URI as the relay's websocket. 9Relays may provide server metadata to clients to inform them of capabilities, administrative contacts, and various server attributes. This is made available as a JSON document over HTTP, on the same URI as the relay's websocket.
10 10
diff --git a/13.md b/13.md
index cf5b1ac..d7e7725 100644
--- a/13.md
+++ b/13.md
@@ -4,7 +4,7 @@ NIP-13
4Proof of Work 4Proof of Work
5------------- 5-------------
6 6
7`draft` `optional` 7`draft` `optional` `relay`
8 8
9This NIP defines a way to generate and interpret Proof of Work for nostr notes. Proof of Work (PoW) is a way to add a proof of computational work to a note. This is a bearer proof that all relays and clients can universally validate with a small amount of code. This proof can be used as a means of spam deterrence. 9This NIP defines a way to generate and interpret Proof of Work for nostr notes. Proof of Work (PoW) is a way to add a proof of computational work to a note. This is a bearer proof that all relays and clients can universally validate with a small amount of code. This proof can be used as a means of spam deterrence.
10 10
diff --git a/17.md b/17.md
index 900b6dd..3ccdc77 100644
--- a/17.md
+++ b/17.md
@@ -4,7 +4,7 @@ NIP-17
4Private Direct Messages 4Private Direct Messages
5----------------------- 5-----------------------
6 6
7`draft` `optional` 7`draft` `optional` `relay`
8 8
9This NIP defines an encrypted chat scheme which uses [NIP-44](44.md) encryption and [NIP-59](59.md) seals and gift wraps. 9This NIP defines an encrypted chat scheme which uses [NIP-44](44.md) encryption and [NIP-59](59.md) seals and gift wraps.
10 10
diff --git a/26.md b/26.md
index 645ec44..6cd32f4 100644
--- a/26.md
+++ b/26.md
@@ -6,7 +6,7 @@ NIP-26
6Delegated Event Signing 6Delegated Event Signing
7----------------------- 7-----------------------
8 8
9`draft` `optional` 9`draft` `optional` `relay`
10 10
11This NIP defines how events can be delegated so that they can be signed by other keypairs. 11This NIP defines how events can be delegated so that they can be signed by other keypairs.
12 12
diff --git a/29.md b/29.md
index 9099e4d..a1f035e 100644
--- a/29.md
+++ b/29.md
@@ -4,7 +4,7 @@ NIP-29
4Relay-based Groups 4Relay-based Groups
5------------------ 5------------------
6 6
7`draft` `optional` 7`draft` `optional` `relay`
8 8
9This NIP defines a standard for groups that are only writable by a closed set of users. They can be public for reading by external users or not. 9This NIP defines a standard for groups that are only writable by a closed set of users. They can be public for reading by external users or not.
10 10
diff --git a/40.md b/40.md
index 909747f..9450b3c 100644
--- a/40.md
+++ b/40.md
@@ -4,7 +4,7 @@ NIP-40
4Expiration Timestamp 4Expiration Timestamp
5-------------------- 5--------------------
6 6
7`draft` `optional` 7`draft` `optional` `relay`
8 8
9The `expiration` tag enables users to specify a unix timestamp at which the message SHOULD be considered expired (by relays and clients) and SHOULD be deleted by relays. 9The `expiration` tag enables users to specify a unix timestamp at which the message SHOULD be considered expired (by relays and clients) and SHOULD be deleted by relays.
10 10
diff --git a/42.md b/42.md
index 24f7f5d..c2b6ded 100644
--- a/42.md
+++ b/42.md
@@ -4,7 +4,7 @@ NIP-42
4Authentication of clients to relays 4Authentication of clients to relays
5----------------------------------- 5-----------------------------------
6 6
7`draft` `optional` 7`draft` `optional` `relay`
8 8
9This NIP defines a way for clients to authenticate to relays by signing an ephemeral event. 9This NIP defines a way for clients to authenticate to relays by signing an ephemeral event.
10 10
diff --git a/43.md b/43.md
index 6455c08..d0742b4 100644
--- a/43.md
+++ b/43.md
@@ -4,7 +4,7 @@ NIP-43
4Relay Access Metadata and Requests 4Relay Access Metadata and Requests
5---------------------------------- 5----------------------------------
6 6
7`draft` `optional` 7`draft` `optional` `relay`
8 8
9This NIP defines a way for relays to advertise membership lists, and for clients to request admission to relays on behalf of users. 9This NIP defines a way for relays to advertise membership lists, and for clients to request admission to relays on behalf of users.
10 10
diff --git a/45.md b/45.md
index 8758c87..14d656e 100644
--- a/45.md
+++ b/45.md
@@ -4,7 +4,7 @@ NIP-45
4Event Counts 4Event Counts
5------------ 5------------
6 6
7`draft` `optional` 7`draft` `optional` `relay`
8 8
9Relays may support the verb `COUNT`, which provides a mechanism for obtaining event counts. 9Relays may support the verb `COUNT`, which provides a mechanism for obtaining event counts.
10 10
diff --git a/46.md b/46.md
index 1701964..e951b5b 100644
--- a/46.md
+++ b/46.md
@@ -41,7 +41,7 @@ There are two ways to initiate a connection:
41 41
42_remote-signer_ provides connection token in the form: 42_remote-signer_ provides connection token in the form:
43 43
44``` 44 `relay`
45bunker://<remote-signer-pubkey>?relay=<wss://relay-to-connect-on>&relay=<wss://another-relay-to-connect-on>&secret=<optional-secret-value> 45bunker://<remote-signer-pubkey>?relay=<wss://relay-to-connect-on>&relay=<wss://another-relay-to-connect-on>&secret=<optional-secret-value>
46``` 46```
47 47
diff --git a/50.md b/50.md
index 9eea1f8..08ce4fd 100644
--- a/50.md
+++ b/50.md
@@ -4,7 +4,7 @@ NIP-50
4Search Capability 4Search Capability
5----------------- 5-----------------
6 6
7`draft` `optional` 7`draft` `optional` `relay`
8 8
9## Abstract 9## Abstract
10 10
diff --git a/59.md b/59.md
index 680250b..e570151 100644
--- a/59.md
+++ b/59.md
@@ -4,7 +4,7 @@ NIP-59
4Gift Wrap 4Gift Wrap
5--------- 5---------
6 6
7`optional` 7`optional` `relay`
8 8
9This NIP defines a protocol for encapsulating any nostr event. This makes it possible to obscure most metadata 9This NIP defines a protocol for encapsulating any nostr event. This makes it possible to obscure most metadata
10for a given event, perform collaborative signing, and more. 10for a given event, perform collaborative signing, and more.
diff --git a/62.md b/62.md
index a00ddfc..e0398d8 100644
--- a/62.md
+++ b/62.md
@@ -4,7 +4,7 @@ NIP-62
4Request to Vanish 4Request to Vanish
5----------------- 5-----------------
6 6
7`draft` `optional` 7`draft` `optional` `relay`
8 8
9This NIP offers a Nostr-native way to request a complete reset of a key's fingerprint on the web. This procedure is legally binding in some jurisdictions, and thus, supporters of this NIP should truly delete events from their database. 9This NIP offers a Nostr-native way to request a complete reset of a key's fingerprint on the web. This procedure is legally binding in some jurisdictions, and thus, supporters of this NIP should truly delete events from their database.
10 10
diff --git a/66.md b/66.md
index 59ac1a2..89f5a5f 100644
--- a/66.md
+++ b/66.md
@@ -4,7 +4,7 @@ NIP-66
4Relay Discovery and Liveness Monitoring 4Relay Discovery and Liveness Monitoring
5------------------- 5-------------------
6 6
7`draft` `optional` 7`draft` `optional` `relay`
8 8
9This NIP defines events for relay discovery and the announcement of relay monitors. 9This NIP defines events for relay discovery and the announcement of relay monitors.
10 10
diff --git a/70.md b/70.md
index 043d5fb..32853d3 100644
--- a/70.md
+++ b/70.md
@@ -4,7 +4,7 @@ NIP-70
4Protected Events 4Protected Events
5---------------- 5----------------
6 6
7`draft` `optional` 7`draft` `optional` `relay`
8 8
9When the `"-"` tag is present, that means the event is "protected". 9When the `"-"` tag is present, that means the event is "protected".
10 10
diff --git a/77.md b/77.md
index dd5ef07..ff4eba7 100644
--- a/77.md
+++ b/77.md
@@ -4,7 +4,7 @@ NIP-77
4Negentropy Syncing 4Negentropy Syncing
5------------------ 5------------------
6 6
7`draft` `optional` 7`draft` `optional` `relay`
8 8
9This document describes a protocol extension for syncing events. It works for both client-relay and relay-relay scenarios. If both sides of the sync have events in common, then this protocol will use less bandwidth than transferring the full set of events (or even just their IDs). 9This document describes a protocol extension for syncing events. It works for both client-relay and relay-relay scenarios. If both sides of the sync have events in common, then this protocol will use less bandwidth than transferring the full set of events (or even just their IDs).
10 10