Nostr Web Client

ok, now I understand it.

It's about escaping the content field to create the JSON string. Some implementations are escaping newline char into "\n" (2 chars) but not other characters like LSEP into \u2028 (6 chars) before hashing.

Everything is fine in interfaces because they automatically space and unescape things.

But the hash is sensitive to those differences.

The issue is that some implementations PARTIALLY escape some characters and not escape others.

I am not sure if there is a standard for these choices.

Peter Todd 2y ago

Mixing JSON and cryptographic data structures is a terrible idea. Nostr should have chosen a binary serialization format, same as Bitcoin and OpenTimestamps. Parsing JSON is much more complex than you think it is; parsing binary is much simpler.

#[0]

Reply to this note

Please Login to reply.

Discussion

nextwave 2y ago

💯

Dave Jones 2y ago

🎯 So true. The lazy typing and schema-less nature of JSON is a source of constant developer time waste. It’s useful, but overused.

lucash.dev 2y ago

Thank you! I think I would be the only one who was going to post about limitations and issues in the Nostr protocol.

💯 agree with you on this.

BTW I had been looking for you on this thing 😂😂😂😂