Just like https certificate authorities, the only way to fight all the AI slop will be “trusted” camera firmware that signs every image with a full chain of trust that the output was a real physical video taken will a real device at a real location.
Just like https certificate authorities, the only way to fight all the AI slop will be “trusted” camera firmware that signs every image with a full chain of trust that the output was a real physical video taken will a real device at a real location.
This is terrible for privacy, and can be exploited by bad actors in a multitude of ways far worse than AI slop. A better option would be the ability to load your own cryptographic key into a device and “sign” images with an open standardized protocol in such a way that you can prove you took the image with x camera, and have the option to publicly attest that it was signed by your key at the moment of creation, but the camera images can’t be cross referenced to a specific individual or camera otherwise. If someone is posting unmodified content to social media, it’s in their interests to sign and attest that authenticity. You could also give users the choice to hide everything not attested.
This is how software is signed and released by (not shit) developers currently. It’s also optional, so you can write and release code anonymously if you choose.
Why is it in their interests?
Later, they may find copies of their original content, with trivial edits and others’ signatures attesting to the authenticity of “their” work, even though “they” didn’t travel to Antarctica and spend the winter to get that photo of the emperors incubating their eggs…