From 447f9b3a87bb576a6ac61dc1555f9e1ec2217e93 Mon Sep 17 00:00:00 2001 From: Vitor Pamplona Date: Tue, 17 Oct 2023 10:35:16 -0400 Subject: [PATCH] Adds a clarification that Client must keep an AsSeenOn relay list for each event to make sync work well. --- 29.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/29.md b/29.md index 2496989d..0c279ad4 100644 --- a/29.md +++ b/29.md @@ -50,6 +50,8 @@ The weekly hash MUST happen in the client and in the relay in the exact same way 4. For each group, create an array of event ids: [id1, id2, id3], JSON-serialize it and hash it using SHA-256 5. Return a list of the formatted `.created_at` and the hashes. +Clients must keep records of which events are coming from which relays to sucessfully filter only events from that relay and compare hashes. + ### Why weekly? Simplicity. We could do a recursive approach where the Client chooses the format (e.g: `YYYY`, `YYYY-ww`, `YYYY-MM`, `YYYY-MM-dd`, `YYYY-MM-ddHH`, `YYYY-MM-ddHHmm`). This flexibility allows for some cost savings but adds complexity to the implementation of this NIP.