a metadata header event that is sent first which helps with preparing expectations, it would contain the IDs of the chunks
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
Discussion
No replies yet.