SDCC Discord Backchannel: The Con Behind the Con

Jordan: Welcome back to Server Rooms. I'm here with Thomas and this week we're doing something a little different. Thomas Doan: We are no general news roundup today, one convention, one set of Discord servers start to finish. Jordan: Comic-Con 2026. 6,000 seats in Hall H. Over 130,000 people trying to get into a building that can't hold them. Thomas Doan: Right. And that's the constraint that got me interested. The official app can't tell you which line is moving. So who's filling? Who's filling that gap? Jordan: A fandom-run Discord server. People who don't work for the Con running the actual logistics for thousands of strangers. Thomas Doan: And it's not just fans anymore- we're seeing Sony and DC start building their own Discord activations around the Con. Jordan: Which raises the question we're going to sit with all episode: Can a volunteer mod team really hold up against Con week traffic? Thomas Doan: We joined a couple of these servers cold this week-verification gates, scheduling bots, the whole It's the whole thing. Jordan: And honestly some of it worked better than I expected, some of it did not. Thomas Doan: Later on we've got a technical look at how these servers are actually built to survive that one chaotic week a year. Jordan: And we'll close out with a server pick, a small convention server that's got some real lessons in it, good and bad. Thomas Doan: But first, Hall H, thirty thousand people, one line, let's start there. Jordan: Thomas, tell me you've seen the videos of people camping outside Being outside overnight for that room- According to SDCCBlog, every single badge for Comic-Con 2026 is gone, sold out since the open registration window closed back in November. Thomas Doan: And that's for a show running Wednesday, July 22nd through Sunday the 26th, preview night then four full days on the floor. Jordan: SDCCBlog had this locked in from an ad in last year's Quick Guide. They even flagged the Returning Registration date and the Open Registration date. The date almost a year out. Thomas Doan: So the whole cycle was set before anyone knew what panels would even be on the schedule. Jordan: Right; and once you're inside, Fox Five San Diego's guide puts attendance above one hundred and thirty thousand, the convention center filled to capacity. Thomas Doan: Hall H alone seats six thousand one hundred for the biggest studio panels, per that same guide. Picture that many people camped out for one trailer reveal. Jordan: Honestly I have stood in that line; it's not glamorous. Thomas Doan: So here's my question. Comic-Con has an official app. It has a website. Why does every fandom on earth still spin up its own Discord server for this week? Jordan: Because the app gives you the schedule; it doesn't tell you the whole Hall H line already wrapped the building by six AM. Thomas Doan: That's the gap nobody's built into the official tools. Real time, second by second. Is the panel full? Did the SDCC-exclusive Funko just drop? Where's the line? mine right now in Jordan: An app that refreshes once an hour can't answer any of that. Thomas Doan: this year the studios noticed. The SDCC Unofficial Blog reported Sony Pictures partnered directly with Discord. They're running a Resident Evil fan experience at the Quartyard July 23rd through the 25th. Jordan: So a studio is building its own activation instead of leaving that space to fans. Thomas Doan: That's the shift. Fox 5 San Diego reported DC's official server is marking its It's first anniversary with an SDCC-exclusive poster giveaway at booth four five five four tied to a Superman experience. Jordan: Which tells you the fan built backchannel got popular enough that studios decided to build their own version rather than watch fans do it better. Thomas Doan: I'd still bet the fan run servers win on trust, though. Nobody thinks a Sony server is going to tell them the truth about a bad line. Jordan: Maybe. Depends entirely who's modding it. Thomas Doan: Fair point. So we actually went and joined a few of these fandom-run servers ourselves this week just to see what that back channel looks like from inside. Jordan: And I wanted to see what's holding it together during a spike like Con Week. A Discord with 10 people is easy to run. One with thousands, all typing live about a line that's moving in real time? Thomas Doan: That's a different animal entirely. Jordan: So what happens when 500 people all hit send in the same channel? The second Hall H doors open. Okay, so before we get into the interview, Thomas and I actually went and joined a few of these servers cold, like no invite from a friend, just found them. Thomas Doan: Right. And the first thing you hit isn't a welcome message. It's a gate. Jordan: It really is. I joined one called something like SDCC Linewatch and I sat in a locked channel for a solid two minutes just reading rules. Thomas Doan: That's a verification bot doing its job. You can't see anything past the entry channel until you. until you react to a message agreeing to the no spoiler and no scalping rules, which Jordan: And it's not optional. One server actually timed me out after 10 minutes of not reacting. Thomas Doan: tells you something about intent. These aren't casual chat rooms. They're built as access-controlled tools for the week. Jordan: Once you're in, the channel list is honestly kind of impressive. There's a hashtag whole-hall line channel that's just constant real-time posts. Line and Petco now, wristbands being handed out. Thomas Doan: That's the one that actually matters most, I'd argue. People are making decisions about their whole day off that channel. Jordan: Then there's a hashtag exclusives alert for merch drops and hashtag cosplay meetups where people coordinate photo shoots by franchise or by hallway. Thomas Doan: And scheduling wise, some servers lean on Sesh while others just use Discord's native events feature to post a meet up with the time and location baked in. Jordan: I actually RSVP'd to one, a cosplay meetup near the The other Sails Pavilion didn't go, but the coordination looked clean. Thomas Doan: The bot config underneath that is doing real work, too—verification bot gates entry, a rules acceptance flow logs who agreed to what, and then events just handles the calendar layer on top. Jordan: And what got me was the moderation. Some of these servers have, what, twelve, fifteen volunteer mods for thousands of members? Thomas Doan: That's the part I'm less impressed by, honestly. Jordan: Really, I thought it held up pretty well when I was watching. Thomas Doan: It holds up on a Tuesday in June. My question is what happens the moment Con Week actually starts and message volume spikes. Jordan: Fair; but I watched a mod handle three simultaneous line updates and a spoiler post within about ninety seconds. That's not nothing. Thomas Doan: It's not nothing on a normal day, but volunteer mods usually aren't on shifts and shifts, right? There's no engineering team behind this deciding who covers Burr's two a m Pacific when the line updates about her most. Jordan: So you're saying the structure's solid, but the staffing behind it is the weak point. Thomas Doan: Exactly that. A verification bot can gate a thousand new joins in a second. A volunteer mod cannot read a thousand messages in a second. Jordan: That's a really different kind of scaling problem than the bots solve. Thomas Doan: Right, bots handle access control fine; humans handle judgment calls, and judgment doesn't scale the same way. Jordan: I did notice when I searched around for these servers, a bunch of them show up tagged Comic-Con on Discord, that server listing site. Some have a few hundred members, some have a few thousand. Thomas Doan: And that range matters. A 500-person server with three mods is a very different operation than a 10,000-person server with the same three mods. Jordan: So the disagreement here really is about capacity under load, not whether the system works day to day. Thomas Doan: That's my whole issue: works fine most of the time and works fine during the exact week it matters most are two different claims. Jordan: Which honestly feels like a question for someone who's actually lived through a Con Week traffic spike from the inside. Thomas Doan: Someone running the moderation queue or building the tools underneath it. Jordan: Which is exactly who we're bringing in next. Next! Instead of guessing, let's see what Discord itself says about this. There's a support article and a blog post straight from Discord on running these stage channels under load. Thomas Doan: Good, because I want numbers, not vibes. Jordan: Fair, so Discord's documentation on stage channels puts the audio only cap at up to ten thousand listeners in one stage, with a hard split between speakers and everyone else. Thomas Doan: Ten thousand people listening, but only a handful actually able to Speaker 3: speak. Thomas Doan: able to talk. That's the whole design, right? You're not moderating conversation, you're moderating a queue. Jordan: Exactly. And Discord's own best practices post on running and moderating stages spells out how that queue works day to day. Moderators are told to line up backup moderators before a big event even starts, not after traffic spikes. Thomas Doan: Which tracks with what we saw last segment. Bots gate who gets in, but a human still has to run the room once they're inside. They're inside. Jordan: Right; and the guidance is specific about the raised hand cue. When someone wants to speak, they raise their hand, a moderator sees the request, and only a moderator can promote them to speaker. Thomas Doan: So, during a live panel recap for, say, the Hall H reveal, you'd have one moderator just triaging hands while another actually runs the discussion. Jordan: That's the split Discord recommends, yeah, and here's the part that matters for Con Week specifically: Briefly, the post talks about what to do when a moderator has to step away mid-panel. The advice is to hand off moderator permissions to someone already in the room rather than letting the stage run unsupervised. Thomas Doan: Hand off, not shut down. Jordan: Correct, because a stage with speakers but no moderator watching the queue is technically still live, it's just nobody's steering it. Thomas Doan: Okay, but I want the failure case. What happens when the last moderator- The operator actually disconnects, not steps away-actually drops off Wi-Fi in a packed convention center. Jordan: That's the scenario the FAQ on Discord's support site actually addresses: If every moderator and speaker leaves a stage, the stage ends automatically. Thomas Doan: Ends, as in the whole panel recap just stops? Jordan: As in the audience gets kicked back to the text channel mid sentence. No graceful handoff, no... Please hold. Thomas Doan: So the Con week nightmare isn't a rude comment slipping through moderation, it's a single moderator's phone dying during the Hall H and 10,000 people getting dumped out of the room. Jordan: Which is exactly why the backup moderator recommendation exists. It's not decoration, it's the whole point. Thomas Doan: It also tells you something about how these servers actually staff for con week. If one person's disconnect can end the stage, you need at least two moderators live at all. Live at all times, not just to moderators total. Jordan: And from what we saw poking around the scheduling channels last time, most of these servers list two or three names per event slot in their sesh posts. Now we know why that's not just politeness. Thomas Doan: It's redundancy, same reason you don't run a server on one machine. Jordan: Right, and that's a nice bridge, actually, because the reason this holds up at all-the queue, the hand off, the auto end-comes down to how Discord built built permissions for stages in the first place. Thomas Doan: Which is where I actually want to go next because moderator can promote a speaker sounds simple until you ask what permission that actually is under the hood. Jordan: Is it a role, a per channel grant, something else? Thomas Doan: That's the constraint I want to open with. Give me a second and I'll walk through it. Jordan: Deal. So the guest we just heard from mentioned stage channels almost in passing; but that feature has a real history worth looking at. Thomas Doan: Go on-you've got that technical rabbit hole face." Discord's own FAQ on stage channels lays out the original problem plainly: open voice chat just stopped working when servers hit thousands of members. Anyone with a mic could jump in and talk over a panel. Jordan: Right-the free for all model. I remember servers where every voice channel turned into chaos the second more than twenty people joined. Thomas Doan: Exactly the failure mode Discord was solving for. Stage channels split the room into speakers and audience by design, so a moderator decides who talks, not whoever mashes the unmute button first. Jordan: And that pairs with the EVENTS feature we saw in the fandom service, doesn't it? Thomas Doan: It does. An organizer sets a topic, picks a stage channel as the location, and members And members RSVP. Discord Steve's channel's documentation notes the platform sends a notification thirty minutes before start automatically. Jordan: Thirty minutes, not just five? That's actually useful lead time if you're wandering the convention floor. Thomas Doan: Which matters more during con week than almost any other week of the year. But here's the part that got me: the permission design underneath it. Jordan: Okay, walk me through it. Thomas Doan: A stage moderator can pull someone out of the audience and make Speaker 3: them a speaker. Thomas Doan: And make them a speaker through the raised hands cue. That person gets a mic for exactly as long as the moderator allows it. Jordan: So it's temporary, Thomas Doan: completely temporary, and this is the key detail: it never touches the server's broader channel permission structure. You're not editing roles, you're not granting someone access to moderate the whole server, you're granting one voice slot in one stage for one session. Jordan: Okay, that's a narrower blast radius. radius than I expected; what happens if a moderator gets it wrong-promotes the wrong person? Thomas Doan: They demote them-one click, no cleanup elsewhere. That's the constraint we had to solve for in any permission system: what's the smallest unit of trust you could hand someone, and how fast can you take it back? Jordan: And that's exactly what makes a five thousand person panel recap possible without three moderators drowning in modmail. Right. Thomas Doan: My honest read is that this permission model wasn't built for con week at all. It was built years earlier for tiny AMAs, a host, a couple of guests, 40 people listening. Discord's own blog post on moderating stage channels frames it around small, structured conversations, not stadium-sized ones. Jordan: So it's scaled by accident? Thomas Doan: Not by accident. By design, that happens to work at larger scale. Moderation is a rule you assign, not a permission you manually grant person by person. Once that's true, the size of the audience barely matters. Fifty people or five thousand, the moderator still just promotes from the queue. Jordan: That's the difference between a system that bends and one that snaps. Thomas Doan: And it's why the Fandom server is running SDCC recap panels this week. They aren't quietly rebuilding their permission structure from scratch every July. They're using a feature Discord shipped for something much smaller. Jordan: Which is a pretty good argument for boring infrastructure decisions paying off later. Thomas Doan: The jury is underrated; ship the small thing, and if the model's right, scale finds it eventually. Jordan: Okay, speaking of smaller, we spent this whole episode on the giant Fandom servers and the official studio activations. Thomas Doan: There's a smaller one worth mentioning before we close. Jordan: One nobody's heard of, running the exact same problem at a Speaker 3: - Jordan: at a tenth the size. Thomas Doan: Let's get into that next. Jordan: Quick pivot, server time before we close out, I found one called Artist Alley Underground. Thomas Doan: Never heard of it; what's the pitch? Jordan: It's for people who sell at conventions generally, not just SDCC; table swaps, booth sitting requests, printer recommendations. Thomas Doan: So way smaller than the hubs we've been lurking in all episode. Jordan: Maybe four thousand members; and it's tight-one channel for badge trades, one for table logistics, one for shipping questions. No overlap, no spam. Thomas Doan: The part that stands out to me is the mods actually enforce those boundaries. Post a badge trade in the shipping channel, you get redirected within a minute. Jordan: Compare that to some of the giant servers this week, where one general channel turns into five conversations at once. Thomas Doan: Right, but the rough part, outside con season, the voice channels are dead. Actually empty for months. Jordan: Which makes sense, for a server built around one event. The problem is, onboarding doesn't account for it. Thomas Doan: New members join in March, see silence, and just leave. Jordan: No welcome flow pointing them to the text channels where the real activity lives. Thomas Doan: The SDCC backchannel servers we covered earlier at least pin messages during newcomers' to the sesh events. Jordan: So, the lesson for anyone running a small, Con-adjacent server of their own: Thomas Doan: Structure your channels for the slow months, not just the big week. Jordan: According to sdccblog, SDCC This SDCC twenty twenty six runs Thursday the twenty third thru Sunday the twenty sixth of July, with preview night on the twenty second. Thomas Doan: Four days plus a preview night-that's the entire calendar the server organizes itself around. Jordan: If you're running something similar, that's your Model two-one intense week, fifty one quiet ones. Thomas Doan: The fix isn't complicated: pin a monthly discussion thread, roll out a prep checklist channel six weeks before the event. Jordan: Give people a reason to check in during the off-season. Thomas Doan: If you search DISBOARD's comic con tag, you'll find dozens of servers exactly this size, the same problem. Jordan: Some solve it. Artist Alley Underground still needs that fix, but the moderation approach, narrow channels, fast redirects, holds up regardless. Thomas Doan: If they close that onboarding gap before next July, this could hold members all year round. Jordan: Worth checking in on. Go take a look. See where it stands before badges open again. So that's SDCC twenty twenty six sold out badges whole h madness and apparently a whole shadow network of Discord servers keeping fans sane through con Thomas Doan: Right. And the thing that stuck with me is the moderation question. Volunteer mods holding a verification gate together during Con week traffic? That's a real gamble. Jordan: It is; and I think the honest takeaway here is that fandom infrastructure is doing work the official apps just aren't built for. Thomas Doan: Exactly. Ship it, learn from it, patch it live. That's basically how every one of these servers gets built. Jordan: Which brings us to Artist Alley Underground, our server tour pick this week. Thomas Doan: Tight moderation in the vendor channels, I'll give it that, but the voice channels go dead the second con season ends. Jordan: And the onboarding needs work. No clear welcome flow for new vendors joining cold. Thomas Doan: Small server owners take note: build for the slow months, not just the one big week. Jordan: That's the real lesson from this whole episode to me. Thomas Doan: Got a server we should dig into next? Jordan: Email us serverrooms at show dot com or find us on our own Discord. Thomas Doan: New episodes drop every Wednesday. Jordan: Thanks for spending this one with us. Thomas Doan: See you next week.