> Currently `strfry sync` will post events it has with regular EVENT messages, and/or download events it needs with regular REQ messages.
It’s fine, IMO, that reconciliation is performed out-of-band. A sentence describing what you just said would be fine.
> Maybe we should also describe the Negentropy protocol there?
Whatever the relay is expected to produce should be defined—or at minimum linked to a specification.
Also, IMO, sending hex strings of binary seems to be both inefficient and against the Nostr ethos of legible messages/events. If you’re sending binary, base64 only inflates by 33% compared to hex strings’ 100%.
Personally, I’d prefer to see the message format specified explicitly as debuggable JSON, if feasible.
jimbocoin / jimbocoin 🃏
npub1v9…x9q3h
2024-09-13 20:37:50
in reply to nevent1q…a2dz
Author Public Key
npub1v9qy0ry6uyh36z65pe790qrxfye84ydsgzc877armmwr2l9tpkjsdx9q3hPublished at
2024-09-13 20:37:50Event JSON
{
"id": "3af39991a14aba1a6989ef12df454d6333e022261af1c605e63e453dc5650b51",
"pubkey": "6140478c9ae12f1d0b540e7c57806649327a91b040b07f7ba3dedc357cab0da5",
"created_at": 1726259870,
"kind": 1,
"tags": [
[
"e",
"8623be03632bdf85e140c275fdf7f39b20e1393c381164f5b25662724663058a",
"",
"root"
],
[
"e",
"efbed711793748eb44e21603e4b0bedcb5882f98bc6baeeb54f8d8ac8e2e4cb6",
"",
"reply"
],
[
"p",
"218238431393959d6c8617a3bd899303a96609b44a644e973891038a7de8622d"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
]
],
"content": "\u003e Currently `strfry sync` will post events it has with regular EVENT messages, and/or download events it needs with regular REQ messages.\n\nIt’s fine, IMO, that reconciliation is performed out-of-band. A sentence describing what you just said would be fine.\n\n\u003e Maybe we should also describe the Negentropy protocol there?\n\nWhatever the relay is expected to produce should be defined—or at minimum linked to a specification.\n\nAlso, IMO, sending hex strings of binary seems to be both inefficient and against the Nostr ethos of legible messages/events. If you’re sending binary, base64 only inflates by 33% compared to hex strings’ 100%.\n\nPersonally, I’d prefer to see the message format specified explicitly as debuggable JSON, if feasible.",
"sig": "a34f2ec54348abc0100f2bc0b92dcc4f045f22831ab0ff3574bc1f2248451d3297052c2662aa05f924f9e06a304d69f38e0aa6c031738a0dad361b395042a8a6"
}