> As part of my use of GitLab.com, I acknowledge that the use of my information will be processed in accordance with the agreed GitLab Privacy Policy and Terms of Service. By clicking Accept terms, I am hereby providing consent to this use and agree to all of the terms and conditions.
> (For GitLab Contributors Only) As part of my voluntary contribution to any GitLab project, I acknowledge and agree that my name and email address will become embedded and part of the code, which may be publicly available. I understand the removal of this information would be impermissibly destructive to the project and the interests of all those who contribute, utilize, and benefit from it. Therefore, in consideration of my participation in any project, I hereby waive any right to request any erasure, removal, or rectification of this information under any applicable privacy or other law and acknowledge and understand that providing this information is a requirement under the agreement to contribute to the GitLab project.
> I also acknowledge that Terms of Service and Privacy Policy have been updated to reflect these changes, as well as other updates in accordance with applicable law. By clicking Accept terms, I am hereby providing consent to this use and agree to all of the terms and conditions.
Starting Wednesday, May 23rd, you will not have any access to your gitlab.com, over ssh or otherwise, until you have accepted these changes.
That's annoying, but what it signals is worse. If GDPR affects append-only logs we're in trouble all over the place. See https://social.coop/@gdorn/100067771906542790 for an initial discussion on git.
TL;DR: "I hereby waive any right to request any erasure" is obviously not valid and if #GDPR does indeed apply to e.g. git, which it probably does, we just can't use Merkle trees in the EU any more, if they contain any traces of PII.
Is my account code on bitcoin PII? If I posted it on my blog, I don't see why it wouldn't be.
Has someone ever posted their bitcoin account code on their blog? Heh.