Segregated payloads #64
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
mosaic/nostr-next#64
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.