What could go wrong with playing with AI fire?
This is not an April Fool’s joke:
“OpenAI’s text-generating system GPT-3 is now spewing out 4.5 billion words a day”
You know how adults know better than children do, to not play with fire? Well, in the same way, people who do have a Computer Science degree have a similar view towards those who don’t have a Computer Science degree. This is not intended to be patronizing, however I’m quite sure the following “told you so” mini-prophecy will come true soon enough.
I feel that to safeguard against fake news, and other sorts of online fraud (which GPT-3 will happily facilitate), it’s a foregone conclusion that people will eventually need to learn how to self-host their own content on the internet, if not only to protect themselves against fraud. Why? Because one’s ability to post on one’s own server will necessarily require credentials to a place where AI can’t post (at least not without a server break-in).
Then even further assurance of fraud protection can be had by “digitally signing” the content in order to prove that it was indeed the original author who created it, and it’s not any sort of “deep fake”. To forge such a digital signature, a second break-in would be required on one’s home computer, and the private key, along with the private key passphrase, would need to be stolen.
So digital signing acts as a second factor of authentication (and third factor, if you consider the private key, and the passphrase to the private key as being separate authentication factors).
Here are a couple of quick examples of digital signatures:
Example 1:
A block of text such as this can be signed:
Hello world.
Here’s the digital signature for those words.
Example 2:
A file can be signed, such as this picture:
Here’s the digital signature for that picture.
So how can people “Subscribe” to content on a self-hosted site? Through RSS.
And how can people “Like” content on a self-hosted site? By copying and pasting a link to the “liked” content, sending the link to friends and family.
Note: my GnuPG pubkey 0x28e15963710c0624 can be found by searching here.