Why don't social media and the web in general implement asymmetric key signing to always be able to verify the source of a content, thus eliminating the risk of deep fakes and fake news?
Why don't social media and the web in general implement asymmetric key signing to always be able to verify the source of a content, thus eliminating the risk of deep fakes and fake news?
Am I oversimplifying stuff too much?
I don't understand how this will help deep fake and fake news.
Like, if this post was signed, you would know for sure it was indeed posted by @lily33@lemm.ee, and not by a malicious lemm.ee admin or hacker*. But the signature can't really guarantee the truthfulness of the content. I could make a signed post that claiming that the Earth is flat - or a deep fake video of NASA'a administrator admitting so.
Maybe I'm missing your point?
(*) unless the hacker hacked me directly
important point, but in a federated or distributed system,
thissigned posts/comments may actually be highly beneficialforwhen tying content directly to an account for interaction purposes. I have already seen well-ish known accounts seemingly spoofed on similar looking instance domains.distribution of trusted public keys would be an interesting problem to address but the ability to confirm the association of a specific account to specific content (even if the account is "anonymous" and signing is optional) may lend a layer
toof veracity to interactions even if the content quality itself is questionable.edit: clarity (and potential case in point - words matter, edits matter).
Sure, but that has little to do with disinformation. Misleading/wrong posts don't usually spoof the origin - they post the wrong information in their own name. They might lie about the origin of their "information", sure - but that's not spoofing.