Daniel sent us this one, and it's a topic that's been sitting in the back of my mind for a while. The question is essentially: why did Discord win? Not just among gamers, which we all knew about, but specifically in AI developer circles. Why are builders, founders, researchers, people who spend their days in terminals and notebooks, why are they defaulting to Discord over Slack? And more practically, what do you actually do with that? Because most of us are already in a dozen servers and drowning. Daniel wants us to dig into the cultural and feature dynamics, the real value of company Discords, and how to manage the noise without missing the signal.
The scale of it is striking. Over seventy percent of AI-focused developer communities are now primarily on Discord. That's not a plurality, that's a near-monopoly.
Which is remarkable when you consider that five years ago the conventional wisdom was that Slack was for professionals and Discord was for teenagers arguing about video games.
That conventional wisdom aged badly. And I think the interesting thing is it didn't flip because Discord did something dramatically new. It flipped because the nature of AI developer communities is fundamentally different from what Slack was built to serve.
We're going to get into exactly why that is. Oh, and by the way, today's script is powered by Claude Sonnet four point six, doing its usual thing behind the scenes.
The friendly AI down the road. So let's actually start with what Discord is now versus what people assume it is, because the gamer reputation is genuinely misleading at this point.
It's not wrong, it's just incomplete. Discord started as a gaming coordination tool around 2015, voice channels, persistent text, low latency, free. It was solving a real problem for gaming communities that were stuck on TeamSpeak or scattered across subreddits. But the infrastructure it built for that use case turned out to be almost perfectly suited for something else entirely.
The pivot to tech communities happened gradually and then all at once. The pandemic accelerated it significantly. You had open source projects, machine learning reading groups, research collectives, all of them looking for a place to live that wasn't a Slack workspace with a ninety-day message limit and a pricing wall.
That ninety-day limit on Slack's free tier is actually doing a lot of work in this story and I don't think it gets enough credit.
It's enormous. Think about what that means for a developer community. Someone asks a question about how to configure a particular model architecture in January. Someone else has the exact same question in April. On a free Slack workspace, that conversation is gone. On Discord, it's searchable indefinitely. The institutional memory of the community lives in the channel history, and Discord gives you that for free.
Whereas Slack is essentially saying: pay us or lose your history. Which works fine for a company with a budget and a relatively small team. It does not work for a community of three thousand developers who joined because someone posted a link on Hacker News.
That's the key distinction. Slack was designed for teams. Bounded groups of people with a shared employer or project. Discord was designed for communities. Open-ended, permeable, variable-commitment social structures. Those are different things.
AI developer communities are very much the second thing.
The people building in AI right now are distributed across companies, academia, independent research, hobbyist projects. They don't have a shared org chart. They have shared interests and shared tools. Discord is structurally better suited to that.
Which brings us to the cultural dimension, because I think the feature arguments, as good as they are, don't fully explain the seventy percent figure. There's something about the vibe of Discord that matches AI developer culture in a way Slack doesn't.
I'd agree with that. Slack has a professional tone baked into its design. The interface, the conventions, the implicit expectation that you're there for work. Discord is more like a social space that happens to also be where work gets done. And for a lot of AI developers, especially the younger cohort, that informality is actually a feature.
It lowers the activation energy for asking a dumb question.
If you're in a Slack workspace, there's an implicit professional cost to posting something that reveals you don't know something. In a Discord server, the social norms are more forgiving. People post half-formed ideas, they share experiments that failed, they ask questions they'd be embarrassed to ask in a more formal setting.
For a field that moves as fast as AI, where everyone is perpetually behind and perpetually confused about something, that matters enormously.
The OpenAI Discord is a good example here. It grew by three hundred percent in 2025. That's not because OpenAI did some brilliant community management campaign. It's because people building on the API needed a place to troubleshoot in real time, share what was working, and occasionally yell into the void when the rate limits changed without warning.
Which is a form of community that Slack's design actively discourages.
Slack wants you to use threads, to keep things organized, to maintain a certain signal-to-noise discipline. Discord lets things be messy and that messiness is sometimes where the interesting stuff happens.
I want to push back on one thing though, or at least complicate it. Because the argument that Discord is better for communities isn't universally true. There are contexts where Slack is clearly the right choice.
If you're running a company's internal developer community, a relatively small group of people who are all paying customers or enterprise partners, Slack's integrations with the rest of the productivity stack are valuable. The AI features Slack has added, meeting summaries, threaded conversation analysis, those work well for structured teams.
The choice between them is actually diagnostic. What you pick tells you something about what kind of community you think you're running.
That's a good way to frame it. Slack says: we are a professional group with shared accountability. Discord says: we are an open community and you're welcome to show up however you show up.
AI companies, at least the ones building developer ecosystems, have largely concluded that the second framing serves them better.
Which makes sense when you think about their incentives. If you're Anthropic or Mistral or one of the inference providers, you want as many developers as possible experimenting with your platform. A low-friction entry point is worth more than a polished, gated professional space.
The Runpod job posting I came across recently was interesting on this front. They're actively hiring a developer relations community manager whose explicit requirements include deep fluency with Discord, managing communities of ten thousand or more members, and scaling developer engagement. That's not a Slack job description.
No, and the ten-thousand-member threshold is telling. At that scale, Slack's free tier is completely unworkable, and Slack's paid tier for ten thousand users is a serious budget line. Discord's cost at that scale is essentially zero.
Which is a compelling argument even before you get to any of the feature comparisons.
The pricing asymmetry is real and it's not going away. Discord has built a business model around Nitro subscriptions and server boosts that doesn't depend on charging communities for access. Slack's model requires monetizing the workspace itself. Those are structurally different bets.
The AI developer community has voted with its feet.
Now the question is what you do with that, because being in all these servers is its own problem.
We're going to dig into the real value of company Discords and how to manage the noise without losing your mind. But first, it’s worth understanding how Discord evolved into what it is today.
And Discord’s path is worth tracing quickly. The gaming origin story is real, but it’s also kind of a red herring. The core infrastructure Discord built for gamers—persistent channels, voice that doesn’t require scheduling, role-based permissions—turned out to generalize almost perfectly to technical communities. It wasn’t repurposed; it just found a second home.
The voice channel piece in particular is underrated. Slack has Huddles now, but Discord had always-on voice rooms from the beginning. You can drop into a voice channel, see who's there, and leave without it being an event. That changes the social physics of a community.
It removes the meeting overhead. Which for developers who already have too many meetings is appealing. The AI developer relations landscape has also changed in ways that made Discord's feature set more valuable over time. Two or three years ago, developer relations for an AI company meant documentation, maybe a newsletter, a Slack workspace for enterprise customers. Now it means managing a community of tens of thousands of people who are actively building on your platform and need answers fast.
That shift happened because the platforms themselves became accessible enough that independent developers could actually use them. When the API is fifty cents per million tokens, you don't need a procurement department. You just need a Discord server where someone can tell you why your context window is behaving strangely.
The developer relations function has essentially become community management at scale. Which is a discipline Discord was built for and Slack wasn't.
The fit isn't accidental. It's structural, and it compounds. More AI developers on Discord means more institutional knowledge on Discord, which pulls in more developers.
Now that seventy percent figure starts to look less like a snapshot and more like a stable equilibrium.
Stable equilibrium is a strong claim. What breaks it?
Honestly, the main threat is Discord itself making a product decision that alienates developers. But absent that, the network effects are pretty entrenched. The cultural fit piece is what I'd want to dig into more, because I think it's doing more explanatory work than it gets credit for.
The informality thing isn't just a vibe. It's structurally encoded in how Discord presents information. There's no read receipt pressure. There's no "so-and-so is typing" anxiety in a channel with two thousand members. The interface doesn't make you feel like you're filing a ticket or submitting a report. You're just... And for developers who are in experimental mode, trying things, breaking things, that psychological framing matters.
Slack's design implies accountability. Discord's design implies participation.
And AI developer culture right now is much more participation than accountability. The field is too young, too fast, too uncertain for anyone to be held to a standard of professional polish. People are sharing half-baked fine-tuning experiments at two in the morning. That fits Discord's social contract.
The role-based permissions system is also doing real work here that I don't think gets discussed enough outside of community management circles.
It's underappreciated. You can build sophisticated access structures. Verified developers get one set of channels, beta testers get another, general community gets a third. You can gate access to early model releases, to office hours, to direct engineer contact, all within the same server. That's not trivial to replicate in Slack without significant administrative overhead.
You can add a role category for a new product line without restructuring the entire workspace.
Which is something AI companies need constantly, because they're shipping new things constantly. The permission architecture grows with the product roadmap rather than fighting it.
The feature advantages compound in the same way the network effects do.
And the pricing argument closes the loop. Slack's paid tier at ten thousand members is a meaningful budget decision. Discord at ten thousand members is essentially free. For an AI startup that's pre-revenue or running lean, that's not a minor consideration.
It's often the deciding one.
And the ninety-day message limit on Slack's free tier isn't just an inconvenience, it's a community knowledge problem. The accumulated troubleshooting, the answered questions, the workarounds people discovered, all of that disappears. Discord's indefinite history means a server that's two years old has two years of institutional memory that any new member can search.
Which is worth something you cannot put a price on when you're trying to figure out why your embeddings are behaving strangely at three in the afternoon.
The searchable history alone has probably saved millions of developer-hours across the ecosystem.
The tradeoff, though, is that Discord's professional credibility ceiling is lower. There are contexts where showing up in a Discord server feels less serious than a Slack workspace, and companies navigating enterprise sales have to think about that.
That's real. If your buyer is a procurement team at a Fortune five hundred company, a Discord server can read as hobbyist infrastructure. The optics aren't neutral.
The choice is also a signal about who you're building for.
Which is probably why you see some AI companies running both. Discord for the developer community, Slack for enterprise customer success. Two different audiences, two different social contracts.
And the community that actually generates the cultural momentum, the builders, the experimenters, the people posting about what broke at midnight—that one lives on Discord. But what do you actually get from being in one of these servers?
There's a version of this where you join the Anthropic Discord or the Mistral Discord and it's mostly noise and promotional announcements. And there's another version where it's one of the more valuable professional resources you have access to.
The gap between those two experiences is almost entirely about what the company decides to put there. The ones that are worth your time are the ones where something real is happening. Office hours with an actual engineer who can answer your API question on the spot. Beta access to a model before it's publicly announced. A channel where a founder is posting about product decisions and occasionally responding to pushback.
Which is a kind of access that simply didn't exist before this infrastructure. You couldn't cold-email your way into a conversation with the person who built the tokenizer.
The companies offering that access aren't doing it out of generosity. They're doing it because the feedback loop is worth more to them than the cost of the engineer's time. A hundred developers stress-testing an edge case in real time is better than any internal QA process.
The value flows both ways, and knowing that should change how you engage.
The lurker's dilemma is real here. Most people join these servers, get overwhelmed, mute everything, and then feel vaguely guilty about the servers they never check. Which is a completely understandable response to the volume, but it means they're missing the actual value.
The notification problem is where most people give up. And Discord's tools for managing it are good if you know they exist.
Server-level mute is the starting point. You can mute an entire server but still get pinged when someone uses your keyword highlights. So if you're in the Hugging Face server and you only care when someone mentions a specific model architecture or a library you use, you set those as keywords, mute everything else, and you surface only what's relevant.
Category collapsing is underused too. Most servers have fifteen categories and half of them are things like introductions and off-topic and announcements. You can collapse those permanently and only keep the two or three channels where technical discussion actually happens.
The mobile versus desktop distinction matters more than people realize. Desktop Discord is where you do the active monitoring, the keyword search, the channel browsing. Mobile should be configured to only notify you for direct mentions and keyword hits. If your mobile Discord is pinging you every time someone posts in a busy general channel, you've already lost.
The practical protocol I'd suggest is: pick two or three servers where something irreplaceable is happening. Maybe that's direct engineer access, maybe it's a tight community of people working on the same problem you are. Treat those as active. Everything else is either muted-with-keywords or it should probably go.
The pruning question is one people avoid because there's a fear-of-missing-out logic. What if the server I leave has the breakthrough conversation next week?
That conversation will get posted somewhere else within forty-eight hours. The AI community is not good at keeping secrets.
And the cost of staying in a server you never meaningfully engage with isn't zero. It's attentional debt. Every server you're nominally in is a small claim on your mental model of where information lives.
Etiquette in the busy servers is its own thing. The cardinal sin is asking a question that's been answered seventeen times in the last month without searching first.
Discord's search is actually decent now. There's no excuse for not checking whether your question has been answered, especially in a server with indefinite history. The second sin is posting a wall of text in a general channel. Nobody is reading four paragraphs of context before they know what you're asking.
One sentence, specific question, relevant error message if applicable. That's the format that gets answered—but it’s not just about the content.
The format question is really where engagement lives or dies. You can have the right question and still get ignored because of how it lands.
Which brings us back to the core problem most people have with Discord. They're in too many servers, engaging in none of them well, and the whole thing becomes a background source of low-grade anxiety rather than anything useful.
Let's be direct about what the protocol actually looks like. Notification settings first. Server-level mute is table stakes. But the keyword highlight system is where real filtering happens. You're not trying to read the server. You're trying to surface the three percent of it that's relevant to what you're building right now.
The keywords should be specific. Not "AI" or "model." Something like the name of the specific library you're debugging, or the architecture you're working with. The more precise the keyword, the higher the signal.
Once the notifications are handled, the pruning question becomes easier. The frame I'd use is: does this server give me something I cannot get anywhere else? Direct engineer access, early beta channels, a specific community of people working on exactly your problem. If the answer is no, the server is probably costing you more than it's giving you.
The Runpod job posting I came across was interesting on this front. They were explicitly hiring a Developer Relations Community Manager whose entire job was managing Discord communities of ten thousand plus members, running office hours, handling beta feedback loops. That's a real dedicated function now. Which means the servers worth staying in are the ones where that function is being taken seriously.
If there's a human being whose job is to make that server useful for you, that's a meaningful signal.
And on the flip side, if the last post in the announcements channel was four months ago, you already have your answer.
The professional goals question is worth sitting with for a minute. Most people join servers reactively. Something gets recommended, they join, it sits in the sidebar. The more useful exercise is to start from what you're actually trying to accomplish in the next six months and work backward to which two or three communities are most likely to accelerate that.
That framing changes the whole thing. It's not about being in the right places generally. It's about being present in the places that are specifically useful to you right now.
And that framing is probably the most useful thing we've said today. Not "which servers should I be in," but "what am I trying to build, and where do the people who can help me actually gather.
The open question for me is how long Discord holds this. The dominance is real, over seventy percent of AI-focused developer communities running primarily through Discord at this point. But that kind of concentration has a way of attracting challengers, and Discord itself has monetization pressure that could push it in directions that erode exactly what makes it valuable.
The informal social contract is fragile. The reason engineers show up and answer questions honestly in these servers is partly because it doesn't feel like a formal support channel. The moment it starts feeling like a company-managed PR surface, the candor goes with it.
Which is the tension every platform faces when it scales. The thing that made it good becomes the thing that's hardest to preserve.
Whether Discord figures that out, I don't know. But right now it's where the conversations that matter are happening, and that's not nothing.
It's actually quite a lot.
Thanks to Hilbert Flumingtop for producing, and to Modal for keeping the infrastructure running so we can keep doing this. This has been My Weird Prompts. Today's script, by the way, was written by Claude Sonnet four point six, which we should have mentioned earlier but here we are.
Better late than never.
If you found this useful, leave us a review wherever you listen. We'll see you next time.
