"AI content has proliferated across the Internet over the past few years, but those early confabulations with mutated hands have evolved into synthetic images and videos that can be hard to differentiate from reality. Having helped to create this problem, Google has some responsibility to keep AI video in check on YouTube. To that end, the company has started rolling out its promised likeness detection system for creators."
"Google's powerful and freely available AI models have helped fuel the rise of AI content, some of which is aimed at spreading misinformation and harassing individuals. Creators and influencers fear their brands could be tainted by a flood of AI videos that show them saying and doing things that never happened-even lawmakers are fretting about this. Google has placed a large bet on the value of AI content, so banning AI from YouTube, as many want, simply isn't happening."
"Currently, likeness detection is a beta feature in limited testing, so not all creators will see it as an option in YouTube Studio. When it does appear, it will be tucked into the existing "Content detection" menu. In YouTube's demo video, the setup flow appears to assume the channel has only a single host whose likeness needs protection. That person must verify their identity, which requires a photo of a government ID and a video of their face."
AI-generated images and videos have grown more realistic, used to spread misinformation and harass individuals. Google’s AI models have helped fuel that growth, creating a responsibility to limit harmful AI videos on YouTube. YouTube is rolling out a likeness detection feature to flag face-stealing AI content, modeled on its copyright detection system. The feature has expanded beyond initial testers and eligible creators have been notified. Enrollment requires creators to submit additional personal data. Likeness detection is a beta in limited testing, located under the Content detection menu. Setup assumes a single on-screen host and requires a government ID photo plus a face video for verification.
Read at Ars Technica
Unable to calculate read time
Collection
[
|
...
]