WRONG! They got it completely correct ONE time: when they accused Trump of being sent by God to fight a cabal of powerful international satanic pedophiles.
I also link to a Github project where anyone can verify the DKIM signature for themselves which is a game changer. We're not saying "trust this article" we're saying "okay, here's how to validate this email with Google's DKIM signature"
BTW, the Github wasn't mine, but I did get some conversations started on it and someone else connected the dots. It is a good idea to keep posting Google's DKIM keys around for later validation, too.
EDIT: one more thing to avoid replying to you too many times, but I didn't realize at first that you were the one posting that key last night. Good work on that and thanks for the help, because it did lead to me discovering the Github. I hope this site adds a friends list someday, because I'd add you.
I've been posting this all morning and yeah, you gotta have your archives covered before they get a chance to nuke it.
The Github link has a very solid technical argument that they can't deny, but if anyone gives you the "DKIM doesn't validate the contents" bit, point them to the bh (body hash) argument in the signature that proves this to not be correct. Yes, it's true that DKIM may not be set to validate the body, but it was set to do so here.
I see on conspiracy on reddit that there's some idiot pushing that lie, I don't think I have an account there any more so anyone who can help push the debunk is welcome.
But "muh Russia"!!!!
MAYBE THE REAL COLLUSION WAS THE FRIENDS WE MADE ALONG THE WAY.
Do you watch Nathan for You? Lol
Always has been
WRONG! They got it completely correct ONE time: when they accused Trump of being sent by God to fight a cabal of powerful international satanic pedophiles.
Reported to Google and Twitter
Too late. It's already archived:
https://thedonald.win/p/11PW3ECiBz/-cryptographic-validation-of-hun/c/
I also link to a Github project where anyone can verify the DKIM signature for themselves which is a game changer. We're not saying "trust this article" we're saying "okay, here's how to validate this email with Google's DKIM signature"
I think that's game :)
BTW, the Github wasn't mine, but I did get some conversations started on it and someone else connected the dots. It is a good idea to keep posting Google's DKIM keys around for later validation, too.
EDIT: one more thing to avoid replying to you too many times, but I didn't realize at first that you were the one posting that key last night. Good work on that and thanks for the help, because it did lead to me discovering the Github. I hope this site adds a friends list someday, because I'd add you.
I've been posting this all morning and yeah, you gotta have your archives covered before they get a chance to nuke it.
The Github link has a very solid technical argument that they can't deny, but if anyone gives you the "DKIM doesn't validate the contents" bit, point them to the bh (body hash) argument in the signature that proves this to not be correct. Yes, it's true that DKIM may not be set to validate the body, but it was set to do so here.
I see on conspiracy on reddit that there's some idiot pushing that lie, I don't think I have an account there any more so anyone who can help push the debunk is welcome.