Discord Mods Server: Five Bills, One Age Gate

Jordan: Welcome back to Server Rooms. I'm here with Thomas, and today we're doing something a little different: one server, one law, and the gap in between. Thomas Doan: Yeah. This one's been sitting on my desk for weeks. Worth digging into. Jordan: So this morning, the Senate Commerce Committee held an executive session, five kid safety and AI bills on the table. Thomas Doan: And the one bill everyone in these Discord mod servers has been arguing about, the KIDS Act, not on that list. Jordan: Hmm, right. It passed the House back in June, but it's just sitting there. So we wanted to know what that limbo actually looks like from inside a server that has to plan around it anyway. Thomas Doan: We joined a moderator-run server built for people who run other servers, bot configs, incident channels, the whole setup. Jordan: And we did not agree on everything we found in there. Thomas Doan: No, we did not. I think volunteer mods trying to interpret pending legislation creates real problems. Jordan's less convinced. Jordan: I just think somebody has to read the bill before it becomes their bot's config file. Hmm, we'll dig into that. Thomas Doan: Later in the episode, I'm also tracing something Discord actually shipped, the teen by default rollout back in March, and the pivot from face scanning to card checks and on-device estimation. Jordan: Right. I've got a moderator's own account of that week, people locked out of their own channels, mods included. Thomas Doan: And then I wanna sit with the actual text, Section 103's verification mandate, Section 104's rulemaking, a few sections buried further that quietly decide whether a platform builds one age gate or 50. Jordan: Which is where I come in, because a section number on a page and what a moderator sees on their screen at 2:00 AM are two very different things. Thomas Doan: Fair. We'll close out with a server recommendation too, small, mod-focused. Worth a look if you run anything bigger than a friend group. Jordan: So Senate hearing room today, five bills on the table, one very notable absence. Thomas Doan: Let's start there. What actually happened in that room this morning? Jordan: So 10 o'clock this morning Eastern time, Ted Cruz gavels in a full committee session in Russell 253. Commerce's own release lists five bills, all children's online safety and AI. Thomas Doan: Five bills, and the one everyone actually read isn't one of them. Jordan: Right. The KIDS Act. Crowell reported the House passed it 267 to 117 back in June, and it's been sitting in Senate Commerce ever since. Thomas Doan: GovTrack has the referred version dated July 13th, three weeks parked while Cruz moves five other bills around it. Jordan: Walk me through what's actually up for a vote then. Thomas Doan: Senator Lee's SCREEN Act, KOSA, that's Blackburn and Blumenthal's S1758, Markey's Youth AI Privacy Act, the CHATBOT Act, which Cruz co-sponsors with Schatz, and S5171, a toy safety bill from Duckworth and Murkowski. That one's actually about AI-enabled toys talking to kids. Jordan: Mm-hmm. That's the piece that catches me off guard, a bill about smart teddy bears on the same agenda as platform age verification. Thomas Doan: And Commerce's own notice shows this markup was supposed to happen a week earlier. Bloomberg Government had Cruz targeting July 27th for it. Jordan: So what moved it? Thomas Doan: Officially, the agenda is subject to change, full stop. Bloomberg Government's reporting points to something more specific. The House and Senate KOSA language don't line up, and somebody has to reconcile them before this goes anywhere. Jordan: So even if S1748 clears committee today, that's not the finish line. Thomas Doan: It's the start of a different fight. Jordan: Right. Thomas Doan: The House text and Senate text tackle overlapping problems with different tools, and nobody's built the bridge yet. Jordan: Which is what's been sitting with me since our last two episodes on this. It's not senators reading this bill line by line. It's server moderators. Thomas Doan: The people running age-gated Discord channels. Jordan: Exactly. Unpaid volunteers treating HR 7757's section numbers like something they might actually have to comply with tomorrow. Thomas Doan: Which is strange because a House bill that hasn't cleared the Senate doesn't bind anyone yet. Jordan: Doesn't stop people from building like it will, though. If you're already running a verification bot, you don't wait for a signature. You watch the calendar. Thomas Doan: That's the constraint every mod team we talk to keeps running into, building for a target that keeps sliding a week here, a week there. Today's five-bill lineup is one more version of that. Jordan: So what does that actually look like from inside a server that's been rebuilding its rules around a bill that hasn't passed? So instead of just reading about these moderators, we joined their server. It's called something dry, Server Ops Collective, and it's not small. Thomas Doan: How many members? Jordan: Just under 9,000 according to the member count on the sidebar, and the structure tells you everything about who runs it. Thomas Doan: What's the layout look like? Jordan: There's a category called Legal and Policy, and inside, two channels: Age Gate Help and General Moderation. The pinned message in Age Gate Help is a running bill tracker updated by hand. Thomas Doan: By hand? No bot pulling that from congress.gov? Jordan: Nope. Someone's typing status updates- Thomas Doan: Mm-hmm Jordan: ... at 1:00 in the morning citing section numbers off a PDF. Thomas Doan: That's the part that gets me, unpaid people doing the reading that lobbyists get paid to do. Jordan: And they take it seriously. One thread had 40 replies arguing about what counts as an adult role under a bill that hasn't passed. Thomas Doan: Right, and here's my problem with that. None of the tooling they're using was built to carry legal weight. Jordan: Walk me through what you saw. Thomas Doan: Standard stack. A verification gate bot hands out an adult role after some check. Auto mod runs word lists to catch minors posting ages, and half the channels are gated to that one role. Jordan: So the whole server hinges on that single role assignment. Thomas Doan: Exactly, and that's the failure point. If the role stops mapping to anything, if the platform's own age signal changes underneath it, every permission built on top of it is now wrong silently. Jordan: And that's not hypothetical this year. Thomas Doan: No. Discord's press release on this said the company launched teen by default settings globally on February 9th, resetting how age gets assumed for anyone who hasn't verified. Jordan: So overnight, servers built around one definition of verified adult are working against a different baseline. Thomas Doan: Right, and GameSpace reported the fall age assurance rollout got delayed to the second half of this year after backlash over how invasive the checks felt. Jordan: Which means moderators aren't rebuilding once. They're rebuilding against a target that keeps sliding. Thomas Doan: Bitdefender's coverage of the delay made basically that point. Operators had already redone their gates once in March, then had to wait on the rest. Jordan: In general moderation, nobody's debating statute language. It's just, "My auto mod list flagged a birthday message. Help." Thomas Doan: That's the more honest channel, honestly. Jordan: But watching Age Gate Help, I kept thinking, "These people care more about getting this right than some of the staffers we've covered." Thomas Doan: I don't doubt the care, I doubt the design. A volunteer moderator reading Section 103 language is doing statutory interpretation with a Discord bot and a spreadsheet. Jordan: So who should be doing it? Thomas Doan: Somebody with liability exposure, which none of these mods have, and none of them signed up for. Jordan: They'd tell you they signed up because nobody else was going to. Thomas Doan: That's fair, and it's also exactly how you end up with nine thousand people trusting a permission system nobody stress-tested for this. Jordan: Which is a good place to hand this off, because one of the people running that stress test is in our next clip. Thomas Doan: The moderator who actually rebuilt gating after March. Jordan: What broke first, how many members lost access, she'll tell us. Thomas Doan: And I wanna know what happens when the age check gets a moderator wrong, because Discord's own messaging says most of this is automatic, no action needed. Jordan: Which is not quite what the people in that server are describing. Thomas Doan: No, it really isn't. Jordan: Building on that fight over who should be carrying this, there's a pinned post in Age Gate Help from the mod who runs the verification gate bot worth reading straight. Thomas Doan: What's she saying happened? Jordan: She says the day teen by default flipped on, the bot rechecked everyone against Discord's new default, and around forty longtime members who'd never touched the adult role lost access to the paid tier channels overnight. Thomas Doan: Mm-hmm. Forty people locked out, and nobody on the mod team pushed that change themselves? Jordan: That's what got you, huh? Discord's own developer support page says no action is expected from operators. Over ninety percent of users get an age determined automatically, no extra step. Thomas Doan: So Ninety percent sorted automatically, and the other ten percent are filing tickets in that same channel. Jordan: Pretty much. Thomas Doan: So walk through the failure case that actually worries me. Age misjudges someone who isn't a random member, she's a moderator. Does she lose the mod permissions along with the adult role? Jordan: From her post, yes. The adult role and channel moderation permission sat in the same permission set, so losing one meant losing both. She had to manually grant three moderators mid-shift. Thomas Doan: So the failure isn't a kid seeing something they shouldn't, it's the person supposed to catch that locked out of the tools to fix it. Jordan: That's the reversal she flagged. Thomas Doan: And Discord's still settling on its own method here. Wired Parents update on these changes reported Discord shut down its small persona face scan trial and deleted the data tied to it. Jordan: Deleted, not archived? Thomas Doan: That's what Wired Parents says. Going forward, per that reporting, the plan is credit card checks plus on-device facial age estimation. The estimate runs on your own phone or laptop, not on Discord servers. Jordan: So the risk of holding that scan moves off the platform and onto the device. Thomas Doan: Right, which helps Discord's liability and maybe helps privacy, but the accuracy depends on whatever camera you're pointing at it. A five-year-old webcam reads age differently than a current phone. Jordan: Which loops back to her forty members. If accuracy varies that much by hardware, misclassification isn't the exception, it's built into the math. Thomas Doan: Right, and none of Discord's public messaging owns that variance. Ninety percent, no action needed. Clean number. Her week says the other side of that number is where the real work landed. Jordan: Is that the trade-off of automating identity at this scale? Catch most people cleanly, push every edge case onto whoever's holding the ticket queue. Thomas Doan: That's exactly it, and right now, that queue is unpaid volunteers. Jordan: The same ones we were just arguing about. Thomas Doan: Same ones. Jordan: So if the platform's messaging and her actual week don't line up, the next question is what the law says an operator has to build, because on paper, the only thing pending is a bill that hasn't cleared the Senate yet. Thomas Doan: Which means we open Section 103 next, the part that's supposed to define what commercially available verification even means. Jordan: See what it actually requires. And the bill sitting in the room we opened on today isn't even this one, which is the part that should worry. Thomas Doan: Pulling up the text now. Section 103. The constraint the drafters are solving for is simple to state and hard to build. Flag a minor without turning every login into a background check. Jordan: And their answer? Thomas Doan: Covered platforms have to adopt what the bill calls commercially available technology verification measures to identify users under eighteen. That's the language sitting in the version posted on Govtrack. Jordan: So in moderator terms, that's the toggle deciding whether a thirteen-year-old lands in the teen experience before they even click into a server. Thomas Doan: Right, and Section 104 sends the FTC out first to consult privacy experts, verification vendors, and child safety groups before any actual standard gets written. The toggle doesn't exist yet. The rulemaking does. Jordan: Does the text require someone to hand over a driver's license to make that call? Thomas Doan: It doesn't. Nothing in Section 103 requires submitting government ID to the platform or to a third-party vendor it hires. That absence is written in on purpose, according to the GovTrack text. Jordan: Uh, then why did the rollout we just talked about feel like an ID check? Thomas Doan: Because that's the tool the company picked. The statute doesn't choose the method, it just says adopt something available. Section 220 goes a step further. It's a rule of construction stating that- Jordan: Mm-hmm Thomas Doan: ... Title II's subtitle doesn't require age gating at all. Jordan: Wait, Title II, not Title I? Thomas Doan: That's the split. Title I, Section 103, carries the verification mandate for shielding minors from obscenity. Title II is the broader platform design subtitle, and Section 220 carves out a warning that half of the bill can't be read as an age gate requirement on its own. Jordan: So a platform could satisfy Title II's design duties without ever asking anyone's age. Thomas Doan: That's the reading. Jordan: Then what actually decides whether a company builds one gate or fifty different ones state by state? Thomas Doan: Preemption Section 106 and Section 221 both preempt state law that conflicts with the federal standard. Every general counsel reading this bill goes straight to those two sections because it's the line between one national gate and a patchwork tied to whichever state moves first. Jordan: And nobody checks the homework for years. Thomas Doan: Section 105 orders a GAO report to three years out covering effectiveness, compliance rates, how securely verification data gets handled, and the speech and economic effects of Section 103. Three years is a long runway for something moving this fast. Jordan: Right. Meanwhile, the bill we opened on today isn't even this one. Thomas Doan: Which is the part that should worry anyone tracking it closely. Crowell's reporting on the Senate calendar suggests KOSA could move as its own vehicle, and if negotiators fold Section 103-style verification language into that text, this House bill never needs its own markup to shape what platform's built. Jordan: So the language survives even if the bill never does. Thomas Doan: That's the risk. Jordan: Which is exactly why the tracker channels we walked through earlier matter. People are posting real configs against a target that keeps moving. Thomas Doan: There's a smaller server built almost entirely around that problem, mod tooling, not press releases. Worth showing people where it lives. Jordan: Building on that, let's send people somewhere useful. Not the big official Discord support servers, a smaller one we actually joined this week. Thomas Doan: It's called Gatekeeper Support, just under four thousand two hundred members last I checked. Jordan: Small enough that a mod actually answers you eventually. Two channels worth your time if you run a server, #working-configs and #post-mortems. Thomas Doan: Working-configs is exactly what it sounds like, people pasting their auto mod rule sets and verification bot settings that didn't break on them. Real JSON, real role hierarchies. Jordan: And post-mortems is the honest part. People posting screenshots of the thing that locked out forty members overnight and walking through why. Thomas Doan: That's rarer than it should be. Most servers hide their failures. This one archives them on purpose. Jordan: Now, the rough parts. Tickets sit for days. We opened one Tuesday asking about role sync timing and got an answer Friday. Thomas Doan: The onboarding flow is worse, honestly. New members land in a welcome screen with six buttons before they ever see the two channels that matter. Jordan: You have to already know to look for working-configs. Nothing points you there. Thomas Doan: And there's the legal talk. People with no bar card confidently explaining what Section 103 requires. Jordan: Right. Thomas Doan: Some of it's close, some of it isn't. Jordan: Which is the thing we flagged with the other server too. Good intentions, no lawyer in the room. Thomas Doan: Right. Except here, nobody's pretending to be an authority. It reads more like people thinking out loud, which is different. Jordan: Fair. So what should people actually watch after today's session wraps at Commerce? Thomas Doan: Whether KOSA comes out amended with Section 103-style verification language attached. If it does, the House bill's specific text effectively ships anyway. Jordan: Through a different vehicle entirely. Thomas Doan: Exactly that. And separately, whether HR 7757 gets scheduled for a Senate markup at all or just sits. Jordan: Because right now it's referred, not scheduled. Those are two very different states for a bill to be in. Thomas Doan: One of them means something's happening, the other one means it's on a shelf. Jordan: So if you're a moderator watching this, the calendar move to track isn't a vote, it's where the Commerce puts a KIDS Act markup on an agenda. Thomas Doan: Watch the committee's public schedule, not the headlines. Headlines lag by days sometimes. Jordan: And if you're just curious rather than running a server, Gatekeeper Support is worth a look, slow tickets and buried channels included. Thomas Doan: Just go straight to working-configs. Skip the Welcome screen entirely. Jordan: Best advice all episode. Thomas Doan: The other thing worth watching, whether any state moves on its own age verification law before Congress settles the preemption question we walked through. Jordan: That's the wild card, isn't it? Fifty different clocks running at once. Thomas Doan: Some of them faster than Washington's. Jordan: So that's where we leave it. A bill parked, a markup happening, and a server of volunteers building for whichever version actually lands. So that covers today's episode, from a Senate committee room straight into a mod's Discord server. Thomas Doan: Yeah. The range still gets to me. Same bill, two completely different rooms trying to read it. Jordan: The image that's staying with me is that moderator typing status updates at one in the morning, citing Section numbers off a PDF. Thomas Doan: And I disagreed with Jordan on that. Whether volunteers should even be doing the legal reading Congress hasn't finished itself. Jordan: Mm-hmm. The age gate mess on the ground is downstream of a bill still stuck in committee. Thomas Doan: Right. Until Section 103 gets language everyone can agree on, that single point of failure in the verification bot isn't going anywhere. Jordan: Gatekeeper Support, our server pick this week. Go check the config sharing channel. Ignore how slow the tickets move. Thomas Doan: Worth it for the failure post-mortems alone. Jordan: We'll be watching whether an amended KOSA picks up that Section 103 language and whether this bill ever gets a Senate markup at all. Thomas Doan: Got a server we should look at next? Email us at serverrooms@show.com or find us on our own Discord. Jordan: New episodes land every Wednesday. Thomas Doan: Thanks for spending this one with us. Jordan: See you next week.