Advice if you collaborate in bitcoin privacy projects. Always use anonymous development accounts (Github, Gitlab...), don't keep permanent profiles, use them a few times and never use them again. Create the profiles behind tor or vpn, obviously don't use your email account. If you need your project to have reputation keep the founding account until your project gets traction, then disappear and come back with another account (after giving up the maintenance). You'll have to leave your ego behind, but it's better that than ending up in jail.
Matthew 6:1-4 (KJV) ``` Take heed that ye do not your alms before men, to be seen of them: otherwise ye have no reward of your Father which is in heaven. Therefore when thou doest thine alms, do not sound a trumpet before thee, as the hypocrites do in the synagogues and in the streets, that they may have glory of men. Verily I say unto you, They have their reward. But when thou doest alms, let not thy left hand know what thy right hand doeth: That thine alms may be in secret: and thy Father which seeth in secret himself shall reward thee openly. ```
We should derive some type of master identity system which could be used to generate new identities from a central key, like how bitcoin uses one key to generate many public addresses. Only difference is it would have to use words and numbers, e.g. a key could be used to generate the moniker "gardenelectorate2501" and "jasmineponder7866". This way usernames could be generated with one key, and the owner of the key could prove his various entities are his (but only when/if he wants to do so).
Reminds me of SQRL project. https://www.grc.com/sqrl/sqrl.htm
This is fantastic, haven't read it through completely, but it appears to be some type of anonymous intellectual property system that's federated?
Yes, you have the right idea. It's a protocol (I think) which would allow for "deriv[ing] some type of master identity system which could be used to generate new identities from a central key, like how bitcoin uses one key to generate many public addresses." You'll see the most common use case demonstrated being a more secure website login replacement. You create a secret master identity and then derive unique usernames and login credentials for each website. This approach would be more secure than reusing the same email and password for all your logins. There are more use cases but I brought it up because it seems like it would help facilitate @Cyph3rp9nk advice on anonymous development accounts.