"On Monday, Discord announced a new age verification protocol that will roll out to all users in March. By default, the app will age-lock all accounts to a "teen-appropriate experience," requiring proof of age to access the full experience. Unverified accounts will be blocked from servers or channels with age restrictions, unable to speak in livestream "Stage" channels, and unable to respond to DMs from certain users. It also won't let you change certain settings and will blur age-restricted content throughout the app."
"So, how do you prove your age to Discord? You have a few different options, including uploading a video selfie or an official government ID. If you're skeptical about uploading a selfie (or your government ID) to Discord, your concerns are warranted. Why the backlash? Just last year, the app announced that around 70,000 ID photos were leaked in a cyberattack involving its previous age verification vendor."
"Discord says its new third-party vendor handling age verification is much more secure, of course, highlighting that video selfies are fully processed on-device without the need to upload anything to the internet. With regards to government IDs, it says they are "deleted quickly - in most cases, immediately after age confirmation." But "deleted quickly" is little assurance to anyone who knows how the internet works."
Discord will roll out an age verification protocol in March that defaults all accounts to a teen-appropriate experience and restricts unverified users. Unverified accounts cannot access age-restricted servers or channels, speak in Stage livestream channels, respond to certain DMs, or change some settings; age-restricted content will be blurred. Verification options include uploading a video selfie or an official government ID. A prior vendor breach exposed roughly 70,000 ID photos and other personal data, prompting Discord to end that vendor relationship. Discord reports that video selfies are processed on-device and government IDs are deleted quickly after confirmation, but privacy concerns remain.
Read at ZDNET
Unable to calculate read time
Collection
[
|
...
]