drop pseudonym scope, legacy format/hash support #835
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.
A couple things to note:
scope == null
in the email case; so legacy hashes of emails and v0.4 hashes of emails are byte-wise equivalent, although there is a minor encoding difference. legacy pseudonyms invented a url-safe encoding (replacing+
and/
with_
and.
), instead of using the standard RFC one (_
and-
).Features
h_4
)Change implications