diff options
| author | Semisol <45574030+Semisol@users.noreply.github.com> | 2025-01-03 10:41:40 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-01-03 10:41:40 +0300 |
| commit | 8231c8e1e91d851df70d793c0f36ab730c33b506 (patch) | |
| tree | 7db9071511e543b372b9a2d5a680521a639150fc | |
| parent | 01926e3da2baaf5bb519658473944283da812bd7 (diff) | |
Update NIP-91
| -rw-r--r-- | 91.md | 4 |
1 files changed, 3 insertions, 1 deletions
| @@ -34,7 +34,9 @@ The first entry MUST be an object, with the keys being protocol names, and the v | |||
| 34 | 34 | ||
| 35 | A protocol offer can be sent multiple times in a connection, such as to update availability based off of their [NIP-42](./42.md) authentication status. | 35 | A protocol offer can be sent multiple times in a connection, such as to update availability based off of their [NIP-42](./42.md) authentication status. |
| 36 | 36 | ||
| 37 | Clients SHOULD be able to handle protocol offers being able to be withdrawn. The removal of a protocol from a `PN-OFFER` does not affect existing active protocols, a `PN-SHUTDOWN` must be sent if that is required. | 37 | Clients SHOULD be able to handle protocol offers being able to be withdrawn, and should treat them as if it was a `PN-SHUTDOWN` if they were in use. |
| 38 | |||
| 39 | Certain protocols, such as extensions to REQs, may not need negotiation. This is up to the specification of the specific protocol. | ||
| 38 | 40 | ||
| 39 | ## Protocol Requests | 41 | ## Protocol Requests |
| 40 | 42 | ||