nostr/strfry
1
0
Fork 0
mirror of https://github.com/hoytech/strfry.git synced 2025-06-19 09:36:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

wip

Browse Source
This commit is contained in:
Doug Hoyte
2023-03-08 08:46:06 -05:00
parent c93ba8ca90
commit 9ef8ca7677
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/xor.md
View File

@ -12,10 +12,10 @@ We'll call the two sides engaged in the sync the client and the relay (even thou
* A subscription ID that will be used by each side to identify which query a message refers to * A subscription ID that will be used by each side to identify which query a message refers to
* A nostr filter, as described in [NIP-01](https://github.com/nostr-protocol/nips/blob/master/01.md), or an event ID whose `content` contains the JSON-encoded filter * A nostr filter, as described in [NIP-01](https://github.com/nostr-protocol/nips/blob/master/01.md), or an event ID whose `content` contains the JSON-encoded filter
* The truncation byte size for IDs, called `idSize. An integer between 8 and 32, inclusive. * The truncation byte size for IDs, called `idSize. An integer between 8 and 32, inclusive.
2. Both sides collect all the events they have stored/cached that match this filter. 1. Both sides collect all the events they have stored/cached that match this filter.
3. Each side sorts the events by their `created_at` timestamp. If the timestamps are equivalent, events are sorted lexically by their `id` (the canonicalised hash of the event). 1. Each side sorts the events by their `created_at` timestamp. If the timestamps are equivalent, events are sorted lexically by their `id` (the canonicalised hash of the event).
4. Client creates an initial reconcilliation message and sends it to relay. 1. Client creates an initial reconcilliation message and sends it to relay.
5. Each side processes an incoming message and replies with its own outgoing message, along with a list of "have IDs" and "need IDs", stopping when one party receives an empty message. 1. Each side processes an incoming message and replies with its own outgoing message, along with a list of "have IDs" and "need IDs", stopping when one party receives an empty message.
## Nostr Protocol ## Nostr Protocol