diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2023-04-09 08:50:24 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2023-04-09 08:50:24 -0300 |
| commit | fb5b7c739ff92cec4962990aa99c54fac9f5de81 (patch) | |
| tree | e20260d2ed02c68cb9741577b424fc573f474592 /15.md | |
| parent | dee546ed9ead06135522307c7effafb8e7095afd (diff) | |
merge NIP-15 into NIP-01.
Diffstat (limited to '15.md')
| -rw-r--r-- | 15.md | 21 |
1 files changed, 0 insertions, 21 deletions
| @@ -1,21 +0,0 @@ | |||
| 1 | NIP-15 | ||
| 2 | ====== | ||
| 3 | |||
| 4 | End of Stored Events Notice | ||
| 5 | --------------------------- | ||
| 6 | |||
| 7 | `final` `optional` `author:Semisol` | ||
| 8 | |||
| 9 | Relays may support notifying clients when all stored events have been sent. | ||
| 10 | |||
| 11 | If a relay supports this NIP, the relay SHOULD send the client a `EOSE` message in the format `["EOSE", <subscription_id>]` after it has sent all the events it has persisted and it indicates all the events that come after this message are newly published. | ||
| 12 | |||
| 13 | Client Behavior | ||
| 14 | --------------- | ||
| 15 | |||
| 16 | Clients SHOULD use the `supported_nips` field to learn if a relay supports end of stored events notices. | ||
| 17 | |||
| 18 | Motivation | ||
| 19 | ---------- | ||
| 20 | |||
| 21 | The motivation for this proposal is to reduce uncertainty when all events have been sent by a relay to make client code possibly less complex. | ||