What you're saying makes sense, but nostr was designed with ease of use rather than optimization in mind. You're right that if there's ever a binary format it could probably be excluded from it.

Reply to this note

Please Login to reply.

Discussion

That's fair I guess. nostr *does* seems oddly byte conscious in some places though (many single digit tags, integer kinds instead of namespaced string identifiers)