Anyone know why Flockstr is generating 4 byte values for the UUID instead of a proper UUID per RFC 4122?
Is it because its associated with pubkey author of event when referenced in calendar and thus collisions on that should be rare?
For automated, something will exhaust 4 billion records eventually.
Related... I wish clients would add a "client", or better yet a "user-agent" tag to hunt these down.
nostr:npub1fl0cktytkd80798jzh7deumdlky3yzj88fdsexfuray2uqjj79rs63mwl4
I cant find your git repo to look into fixing this and some other minor stuff
imo, 64 bytes is the right size for a nonce or fingerprint. 32 bits is barely enough for general purpose in-memory array usage ffs.
overkill in this instance. I agree 32 bits is likely too short, unless always paired with a pubkey.
UUIDs are 128 bit (16 byte). Thats on par with the uniqueness afforded by a 12 word seed phrase.
oh, i meant 64 bits. lol, 64 bytes is waaay overkill.
if the data has a frame, 64 bits will generally be enough.
for fingerprints, yeah, i hadn't really thought that much about it tbh, but 128 bits would be just about right.
