Recipient Email Hashing

[LarmuseauNiels]

No description provided.

[jeborsel]

How should I interpret the labels? As in 'hashing email address is low priority' or as in 'we are not going to use email as recipient identifier' ... because if it is the first, I would highly discourage putting non-hashed email-addresses in the badge assertions ....

[jeborsel]

Actually I also see in the mock-up now the "personal information screen" ... please do not put any plain personal information into the badge assertions. Also the linking with google or facebook services I really think is NOT a good idea (I know a partner suggested it, but he is missing the point of using public/private key profiles ... users don't need to define in the badge assertion itself what other personal information they want to share, this can happen outside of it (and should happen outside of it) ... @wschella @LarmuseauNiels @chloedevriese . The badges created should be pseudonymous ... de-anonymisation & possible authentication can happen elsewhere ... think of it as if the badge assertion are public visible to all ..