jimbocoin on Nostr: > Currently `strfry sync` will post events it has with regular EVENT messages, and/or ...
> 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.
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.