The Third Place Problem With Discord

August 2, 2026

Discord is the most successful digital third place ever built. 200 million people use it every month. Millions of communities live there — gaming groups, study circles, maker spaces, open source projects, friend groups, neighborhoods. It’s where people go to hang out.

And it’s being sold out from under them.

The pattern

Every platform that becomes a third place goes through the same cycle:

1. Launch. Free, open, no ads, no friction. “We’ll never sell out.” The community grows because it feels safe.
2. Growth. Investment pours in. The platform scales. Features ship. The community deepens. People invest years building their space.
3. Monetization pressure. Investors want returns. The platform needs revenue. Ads appear. Premium tiers launch. Data gets harvested.
4. Enshittification. The community becomes ad inventory. The experience degrades. The rules change. The third place you built is now a storefront, and you’re the product.

This isn’t hypothetical. It’s a documented pattern.

AIM was where a generation hung out online. AOL killed it in 2012. Everyone moved.

IRC was the original chat third place. Networks shrank, spam increased, and people migrated to platforms that felt more modern. The communities that had spent a decade on IRC scattered.

Early Reddit felt like a collection of third places — small subreddits with regulars and culture. Then Reddit killed third-party apps (2023), went public (March 2024), and started selling API access. The subreddits are still there, but they’re not yours.

Discord is in step 3-4 right now.

What happened to Discord

The timeline is clear:

• 2024: Discord ships sponsored content and ads. Your community server now displays ads to your members.
• October 2025: Data breach. User data exposed. The community you built on Discord had its data compromised by Discord, not by you.
• January 2026: Discord files for IPO. The platform is now accountable to shareholders, not to the communities that live on it.
• 2026: Age verification requirements introduced. A friction barrier that makes it harder for new members to join your community — the “low barrier” requirement of a third place, broken by the platform.

Each of these changes was unilateral. Nobody voted. Nobody was asked. The communities that spent years building their spaces had no say. Discord decided, and the communities lived with it.

This is the core problem: you don’t own your third place on Discord. You rent it. And the landlord can change the lease whenever they want.

Why a third place can’t be a product

Ray Oldenburg’s third place theory has specific requirements. Let’s check Discord against them:

Three of six requirements broken, one degrading. The third place is dying because the platform that hosts it has different incentives than the community that lives in it.

Discord’s incentive: maximize revenue per user. Your incentive: build a community. When those conflict — and they do, constantly — Discord wins, because it’s their platform.

The tenant farmer problem

Think of it like farming. You can work land you own, or you can work land you rent. If you rent, you can build a beautiful farm, improve the soil, plant orchards, invest decades of labor. But the landlord owns the land. When the lease is up, they can raise the rent, change the terms, or sell the land out from under you.

Every Discord community is a tenant farmer. You’ve invested time, members, culture, history, infrastructure — and it all sits on someone else’s land. The landlord went public. They need quarterly growth. Your community is how they’ll get it.

The solution isn’t a better landlord. The solution is to own the land.

What ownership looks like

A self-hosted community server inverts the power dynamic. Instead of a platform owning your community, you own the platform.

• You control the rules. No terms-of-service update can change how your community works. You write the rules, because you run the server.
• You control the data. Your members’ messages, files, profiles — all on your server. Not in a data center owned by a public company. Not in a breach target. Not in an ad-targeting pipeline.
• You control the boundary. You decide who joins, who’s banned, what’s visible. Not a platform’s trust-and-safety team that has never met your community.
• You control the future. No IPO can enshittify your server. No shareholder can vote to ship ads to your members. No acquisition can shut you down. The server is yours.

This isn’t a theoretical advantage. It’s the difference between a third place and a product.

“But self-hosting is hard”

This was true in 2010. It’s not true now.

A community server used to mean a rack in a closet, a static IP, a domain name, an SSL certificate, a database, a web server, security patches, and a weekend of configuration. That’s why people used Discord instead. The convenience was worth the loss of ownership.

The math has changed. A self-hosted BBS in 2026:

• Costs $5/month — a basic VPS, or $0 if you have a Raspberry Pi
• Takes one command to install — no build pipeline, no Docker compose, no Kubernetes
• Runs on Postgres or H2 — H2 is embedded, zero-setup, auto-detected. No database to configure.
• Configures in a readable language — write .phos files, save, done. No recompile, no restart.
• Accesses from anywhere — SSH, Telnet, or web browser. No app to install.

The convenience gap between “use Discord” and “own your server” has collapsed. What remains is the ownership gap — and it runs in your favor.

The federation answer

“But I don’t want to be isolated” — the most common objection to self-hosting, and the most valid one. A third place with only your community isn’t enough. You want connection to a wider world.

This is what federation solves. Your server is yours — your rules, your data, your boards. But your server can also talk to other servers. A post on your node appears on peer nodes in real time. Your community is part of a larger community, but your local space stays yours.

board "General" {
    federated = true    // syncs with peer nodes — global community
}

board "Internal" {
    federated = false   // stays on your server — never leaves
}

Discord gives you one server in their walled garden. Federation gives you your own garden with gates to other gardens. The sysop controls the gates. Not a platform.

The choice

Every community on Discord is making a bet: that Discord won’t enshittify their experience before they find an alternative. It’s the same bet people made with AIM, with IRC, with early Reddit. They all lost.

You can wait until the next change — the next ad format, the next data breach, the next price hike — and then scramble to rebuild your community somewhere else. Or you can build it on land you own now, while you still have the community to move.

The third place you build on your own server can’t be sold out from under you. It can’t go public. It can’t ship ads. It can’t have a data breach at the platform level. It can’t change the terms.

Because it’s yours.

ssh phosphorbbs.net -p 2222

Part of our series on digital third places. Read the hub article: What Is a Digital Third Place? | Previous: The Internet You Visit on Purpose

Tags: #digitalthirdplace #socialterminal #communityserver #enshittification