Segregated payloads #64

Open
opened 2025-07-05 11:26:23 +12:00 by mikedilger · 0 comments
mikedilger commented 2025-07-05 11:26:23 +12:00 (Migrated from github.com)

Content payloads could be segregated, with just the hash of the contents being in the event, and the actual content shipped separately and available as a blob.

This approaches small events all of the same size... except for tags.

I guess tags could be stored separately too using the same mechanism.

Not certain the benefit is great, but it's an idea I hadn't even thought of before.

Content payloads could be segregated, with just the hash of the contents being in the event, and the actual content shipped separately and available as a blob. This approaches small events all of the same size... except for tags. I guess tags could be stored separately too using the same mechanism. Not certain the benefit is great, but it's an idea I hadn't even thought of before.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
mosaic/nostr-next#64
No description provided.