Release 0.14.2 - #104
Merged
Merged
Release 0.14.2#104
Conversation
Carries the control-byte escaping fix from #103. The id computed for content or tags containing a byte below 0x20 changes with this release, because the escaping now matches nostr-tools and go-nostr rather than the literal wording of NIP-01. Nothing else about the id moves, and no existing vector carried such a byte. Consumers pinning this library by tag pick the change up when they bump. Anything that signs content a person typed or pasted wants it: the wire form previously carried raw control bytes, which is not valid JSON, so a relay would have refused the event.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.