barkyq
commented
1 year ago There is an accepted compression extension called permessage-deflate for transmitting data through websockets, see: https://www.rfc-editor.org/rfc/rfc7692#section-7
Both the client and relay need to implement permessage-deflate in order for the compression to be used. Some relays do not implement it (yet), but I know for a fact that knostr and strfry relay do implement it.
It allows pretty good compression for nostr messages, sometimes hitting around your desired 75%. The compression is best when there is a lot of repetition between returned messages (often there is repetition, as subscription ids, pubkeys, etc are repeated across many messages in a row).
EDIT: shameless plug. finally my relay implementation gnost-relay also has it.
alltheseas
hoytech
Please bear with my non-technical nature & understanding of nostr. In a former professional life the ability to compress certain data types made a lasting impression on me.
Per my limited understanding, it seems NIP-01 describes JSON.
NIP-65 talks about "compressed form", and I understand this to be a different type of compression (i.e. relaying less info/in more compact form).
Doing a quick search, JSON size appears to be compressible by ~75% per https://tukaani.org/lzma/benchmarks.html.
Is it feasible technically to have relay + client compress, and uncompress events, thereby saving bandwidth? For small event size, might this make sense and benefit client + relay?
If yes, what might the tradeoffs be (for instance, increased compute, and therefore battery drain)?