Discord will require a face scan or ID for full access next month

Original Article ↗ Hacker News Discussion ↗

Discord’s plan to require facial scans or government ID to access “adult” channels and unblur sensitive content is drawing sharp criticism from users who see it as a major escalation in online identity checks and surveillance. Commenters debate whether child-safety and anti-bot goals justify the privacy risks, pointing to past data leaks, regulatory pressure, and the likelihood of scope creep and normalization of ID-for-access across the web. Many say they will cancel paid subscriptions or migrate to open-source, self-hosted or federated alternatives such as IRC, Matrix, Stoat, Jitsi, and Zulip, though others doubt large communities will actually move.

Immediate Reaction and Privacy Concerns

  • Strong visceral backlash: many say they will delete accounts, cancel Nitro, or stop using Discord rather than submit an ID or face scan, especially for “shitposting with friends.”
  • Others predict this will be a temporary boycott: users will cave under social pressure and fear of losing communities and history, as happened with phone-number requirements.
  • Some explicitly reject the notion that “you mellow with age,” arguing it’s more important than ever to resist normalization of ID-for-everything.

Child Safety, Regulation, and Motives

  • Supporters frame this as a necessary response to real harms: grooming, CSAM, blackmail, and “industrial-scale” abuse on large platforms.
  • Critics see “protect the children” as a pretext for surveillance, censorship, and destroying anonymity; slippery-slope fears that “adult” will expand to political, LGBT, or otherwise disfavored content.
  • Several note lawmakers are forcing platforms’ hands, especially in EU/UK and some US states, but argue Discord is going beyond what’s legally required in many jurisdictions.
  • Some call for privacy-preserving age proofs (government-issued anonymous tokens, ZKPs) instead of raw IDs and selfies.

Scope, Implementation, and Effectiveness

  • Policy as understood in-thread: “teen-by-default” globally; ID/face check only needed to access age-restricted channels/servers or unblur “sensitive” content; background “age inference” model may silently classify adults to skip checks.
  • Debate over how many users actually need NSFW access; others point out that NSFW flags are often used just to disable aggressive filters, so practical impact may be wider.
  • Many expect easy evasion: AI deepfake webcams, fake or borrowed IDs, adults “renting” verification, making this mostly regulatory CYA rather than real protection.

Trust, Security, and Data Handling

  • The 2025 breach of ~70k ID images is repeatedly cited as proof Discord and its vendors can’t be trusted; “immediate deletion” claims are doubted, especially given fine print (“in most cases”).
  • Concern about opaque third-party verifiers, data brokers, insider threats, and state actors copying IDs before deletion.
  • Accessibility issues: blind users and others with disabilities often cannot realistically complete video/ID scans, making this de facto exclusionary.

Alternatives, OSS, and the Future Internet

  • Large subthread on alternatives: Matrix/Element, Stoat (Revolt), IRC+Mumble/Jitsi, Zulip, Signal, TeamSpeak, forums (Discourse, phpBB), Keet, etc., each with tradeoffs in UX, voice/screen share, mobile stability, and self-hosting burden.
  • Many argue OSS and federated systems should replace Discord, especially for open-source projects that currently trap knowledge in private, non-searchable servers.
  • Others are pessimistic: network effects, user tech-illiteracy, and moderation headaches make a mass exodus unlikely; expectation that similar ID regimes will spread to most large platforms.