Do those 12,000 events include Contact Lists? :)
The one I measured was for ~50,000 events from me or with a p tag on my user, with 7 indexes. But I am just doing the dumb storing of full hexes in the DB, which is not great.
A good use case is if you can download everything about your user (author + p-tags) to the phone.
Login to reply
Replies (1)
Contact lists encode the most efficiently, because hex references are encoded as bytes. 55705 bytes -> 34322 bytes (1.68). But the main goal isn’t minimal size, it’s O(1) field access and mapping to Swift/Rust/etc data structures without encoding/decoding.