negentropy: Consider truncated msgids #19
Description
The negentropy protocol specifies 32 byte ids. But:
- we are extremely bandwidth constrained
- we will only ever have a tiny fraction of the number of notes that negentropy was designed for
If we used 8 byte truncated ids we would not see birthday collisions prevalent until we try to synchronize 2^32 notes. Noshtastic cannot support anything like that number of notes.
Needed changes:
- redefine MSGID_SIZE in the negentropy source to 8 bytes (probably pretty easy)
- add truncated msgid indexing to nostrdb (maybe easy)
This would us to discover missing notes with many fewer negentropy exchanges.
Related to #20