Hey devs, would love to do a quick poll.
I've got a situation where I need to send a data object via Nostr events that, in a minority of cases, is too big to fit in a single nostr event (64kb limit).
I'm thinking of chunking the object across multiple events and then reconstituting it on the other side. nostr:npub1arkn0xxxll4llgy9qxkrncn3vc4l69s0dz8ef3zadykcwe7ax3dqrrh43w and I were doing this when we were experimenting with embedded games last year and it worked surprisingly well.
That said, it's very non-standard, so I'd love to hear some opinions.
#askNostr #nostrDev
I don't see why Its non-standard, if you can create a new kind and make it a standard, especially if it's in the minority case.
Only edge case I've been able to think about is what happens if there are two subsequent events claiming to be the successor of the first one, which is not going to happen in the usual case.
Each could contain a hash of the successor.
Yup, that's what I was planning too.
Then you just need a `head` tag, maybe, so that it builds faster.
💯 and a tag with the total number of events there are.
Well, you would know that you came to the end because it wouldn't have a successor. But that would be a good check. I mean, you could also do a mathematical check of the entire list and store that in the head and skip the successor hashes. Like, a hash of the reconstituted event.
