ETAPX is opening Campus, our official Discord server, as the new real-time home for the Whistlr community. It's not a replacement for the SubCircuits you already post in inside the app — it's the other half of the conversation, the place for live chat, direct access to the team, behind-the-scenes updates, and a front-row seat to what we're building next. If you want a say in where Whistlr goes, this is where that conversation actually happens.
Most companies treat community as a one-way channel. They ship a feature, write a changelog, post an announcement, and call it communication. We've never been comfortable with that model, mostly because it isn't actually a relationship — it's a broadcast. The people using Whistlr every day notice things we don't. They catch bugs in edge cases we didn't test, they have opinions about features we're mid-build on, and they often understand their own use cases better than any internal spec document ever could. The harder problem has always been infrastructure: where does that feedback actually go, and how fast can it move?
That's the gap Campus is built to close. It's our official Discord server, live now at discord.gg/P67zcX9Ra, and it exists for exactly one reason: to give the ETAPX community a real-time place to talk to us and to each other, separate from the more structured, topic-based world of in-app Circuits. Both matter. They're just built for different jobs, and understanding the difference is the whole point of this post.
Why Direct Community Access Matters to ETAPX
Whistlr is a friend-first, creator-focused social platform, and that philosophy doesn't stop at the product. If "friend-first" means anything as a design principle, it has to extend to how we build the thing in the first place. A platform that asks people to be more present, more direct, and more real with each other shouldn't turn around and manage its own community through a support ticket queue and a quarterly survey.
So we've leaned into the opposite approach: get as close to the community as the infrastructure allows. That means real-time conversation instead of delayed replies. It means the people building Creator Studio, Whistlr Go, and the AI video editor are reachable, not hidden behind a brand account. It means when something breaks, you can say so immediately, in a channel where someone on the team is actually going to see it, rather than hoping a bug report form gets triaged before it stops mattering.
There's a practical case here too, not just a philosophical one. Building a creator-monetization stack as deep as ours — WTC Gems, Whistlr Go storefronts, Live Shopping, brand partnerships, native advertising — means we are constantly making decisions that directly affect how creators earn a living on the platform. Those are not decisions we want to make in a vacuum. The faster the feedback loop between "we shipped this" and "here's what's actually happening for real creators," the faster we can correct course, double down on what's working, or kill something that sounded good in a planning doc and turned out to be friction in practice.
"We didn't want a community channel that exists so we can say we have one. We wanted a place where the distance between 'someone has an idea' and 'someone on the team hears it' is as close to zero as we could make it. That's the entire design brief for Campus."
— Priya Okonkwo-Hale, Head of Community at ETAPX
What Discord Offers That In-App Circuits Doesn't
If you're active in Whistlr's Circuits, you might reasonably ask why we need a second community space at all. The honest answer is that SubCircuits and Campus are solving different problems, and trying to force one tool to do both jobs would make it worse at both.
Circuits are built around SubCircuits — focused, topic-based communities with the handle format c/<name>, each with its own banner, rules, membership, and threaded posts sorted by upvotes and downvotes, including a dedicated "Best" sort. That structure is exactly right for durable, organized, searchable discussion. A SubCircuit about streaming setups, or about a particular creator niche, or about Whistlr Go storefront tips, accumulates value over time. Old threads stay useful. The voting system surfaces the best answer to a question someone will ask again six months from now. It's built for permanence and organization.
Discord is built for the opposite instinct: the moment. Real-time chat moves at the speed of a conversation, not the speed of a thread. That difference unlocks a few things SubCircuits structurally can't:
- Real-time chat: When something is happening right now — a launch, an outage, a live event in the app — Discord lets the conversation happen at the speed it deserves, instead of accumulating as disconnected comments over hours.
- Direct access to the team: Product managers, engineers, and support aren't behind a ticket system in Campus. They're in the server, in the channels, answering questions in line with everyone else.
- Behind-the-scenes updates: Work-in-progress screenshots, early concepts, the reasoning behind a decision before it's a finished feature — the kind of texture that doesn't belong in a polished release note but matters enormously to people who care about the product.
- Tight feedback loops: A team member can post a question, get fifty reactions and a dozen replies within the hour, and have a real read on community sentiment before the day is out — something that's much slower to gather from scattered in-app comments.
- Beta testing opportunities: Campus is where we'll recruit testers for features before they roll out broadly, and where the first wave of feedback on something half-finished can shape it before it ships to everyone.
None of that is a knock on Circuits. It's a different shape of value. A SubCircuit thread with a "Best" answer pinned at the top is a permanent resource. A great Discord conversation is a living one — useful in the moment, harder to surface later, but capable of moving at a speed no threaded forum can match. We want both, because creators and users need both: a library to search, and a room to talk in.
How Campus Fits Alongside Circuits, Not Against Them
We thought carefully about this before launching Campus, because community fragmentation is a real risk. The wrong outcome would be two half-populated spaces, each missing context the other has, with the team splitting attention thin enough that neither gets a real answer. So Campus is deliberately scoped as a complement, not a competitor, to in-app Circuits — and that scoping shows up in a few concrete decisions.
First, SubCircuits remain the home for organized, topic-specific, durable discussion. If you're building a resource — a guide, a recurring discussion, a place for a specific niche to gather long-term — that belongs in c/whatever-fits, where the voting system and threading will do their job over months and years. We're not pulling that content into Discord, and we're not trying to recreate SubCircuit-style structure inside Campus either. Discord is bad at being a searchable knowledge base, and we're not going to pretend otherwise.
Second, Campus is the place for everything that's time-sensitive, exploratory, or in-progress: real-time reactions to a new release, live chat during a launch, direct back-and-forth with the team while something is still being decided, and beta programs that need fast iteration. That's content that would get lost or stale in a SubCircuit, and content where the format of a server — channels, threads, voice if we need it, instant replies — is simply the right tool.
Third, and maybe most important, your Whistlr identity is still your Whistlr identity. Campus doesn't ask you to start over. It's an additional room, not a replacement front door. We'd rather you think of it as: Circuits is where the community organizes itself by topic, and Campus is where the community and the team are all in the same room at the same time.
"I'd been posting in a couple of SubCircuits for months, and honestly I assumed nobody from ETAPX actually read them. Then I joined Campus the day it opened and watched an engineer answer a question about Live Shopping latency in real time, in public, with an actual technical explanation. That changed how I think about the whole platform."
— Soraya Bennett-Vance, Whistlr creator
A Practical Walkthrough: What You'll Find When You Join
If you click the invite at discord.gg/P67zcX9Ra and land in Campus for the first time, here's roughly what to expect, laid out the way most well-run Discord communities organize themselves, and the way we've structured ours specifically around Whistlr's community and creator base.
- Welcome and rules: A landing channel that explains what Campus is for, how it relates to in-app Circuits, and the ground rules for keeping discussion useful and respectful. This is also typically where role assignment lives, so you can flag whether you're a creator, a viewer, a developer, or just curious.
- Announcements: The first-stop channel for anything official — feature releases, downtime notices, policy changes, event timing. If you only ever check one channel, this is the one that keeps you current.
- General chat: The unstructured heart of the server. This is where most of the day-to-day conversation happens — what people are streaming, what they're building with the AI video editor, reactions to whatever just happened in the app.
- Feedback: A dedicated channel for product feedback, feature requests, and the "have you considered..." conversations that are easy to lose in a support queue but valuable for us to see directly and immediately.
- Support: A space for account issues, bug reports, and troubleshooting, with team members and experienced community members both able to jump in. Real-time support beats a ticket number when the issue is urgent.
- Creator talk: A channel oriented around the monetization stack — WTC Gems, Whistlr Go storefronts, Live Shopping, brand partnerships — where creators compare notes on what's working and ask questions about payouts, catalog setup, or going live to sell.
- Beta and early access: Where we'll recruit testers for upcoming features, post early builds, and gather the kind of fast, blunt feedback that only comes from people willing to poke at something unfinished.
- Behind the scenes: Work-in-progress looks at what the team is building, the reasoning behind decisions, and updates that are too informal or too early for an official announcement but too interesting to sit on.
That structure isn't arbitrary. It mirrors the actual shape of what a community needs from a real-time space: somewhere to be told things, somewhere to say things back, somewhere to get help, and somewhere to see what's coming. We expect the channel list to evolve as Campus grows — new SubCircuit-adjacent topics will probably earn their own channel once there's enough sustained conversation to justify it — but this is the foundation.
The Case for Community-Driven Product Development
It would be easy to frame Campus as a support channel with a friendlier name. That undersells what we actually think is at stake. The platforms that age well are the ones that build a genuine feedback loop with the people using them, not the ones that ship in one direction and measure reaction after the fact. We'd rather know we're wrong about something on day one, from a hundred creators saying so in real time, than discover it three months later in a churn report.
This matters more, not less, as Whistlr's feature set gets more sophisticated. Creator Studio's analytics and streaming command center, the AI video editor's timeline and voiceover tools, Live Shopping's real-time mechanics — these are the kinds of features where the difference between "technically works" and "actually good" is almost entirely a function of what real usage reveals. No amount of internal testing replicates the texture of a creator going live to sell a physical product for the first time, hitting friction, and being willing to tell you about it in the next five minutes instead of the next support cycle.
There's also a trust dimension that compounds over time. A community that has direct, real-time access to the team that builds the product tends to trust that product more, because trust is built less by announcements than by visible, repeated proof that someone is listening and responding. Every time a question gets a real answer in Campus instead of a canned reply, that compounds. Every time feedback visibly leads to a shipped change, that compounds too. We don't expect Campus to make every decision unanimous — no community discussion does — but we do expect it to make our decisions better informed and our community more invested in the outcome, because they had a hand in shaping it.
"The best feature decisions we've made as a company were not made in a vacuum by a roadmap committee. They came from watching real usage and listening to people who were blunt enough to tell us when something didn't work. Campus is us building that listening process into our actual infrastructure instead of hoping it happens informally."
— Priya Okonkwo-Hale, Head of Community at ETAPX
Frequently Asked Questions
What is the ETAPX Discord server called, and how do I join?
It's called Campus, and you can join with the invite link at discord.gg/P67zcX9Ra. It's free and open to anyone in the Whistlr community, whether you're a creator, a viewer, or just interested in what ETAPX is building.
Is Campus replacing SubCircuits inside the Whistlr app?
No. Campus and SubCircuits are complementary, not competing. SubCircuits remain the home for organized, topic-based, durable discussion with threaded posts and upvote/downvote sorting. Campus is for real-time chat, direct access to the team, and time-sensitive conversation that doesn't fit a threaded forum format. Both will keep existing side by side.
Do I need a separate account to join Campus?
You'll need a Discord account to join the server, since Campus runs on Discord's platform rather than inside Whistlr itself. Your Whistlr identity and your Discord identity are separate, though we recommend using a recognizable username so the community and team can connect the two if you're an active creator.
Can I actually talk to the ETAPX team in Campus, or is it just other users?
Real people from the ETAPX team are active in Campus, including product, engineering, and support. That direct access is the main reason we built the server — it's not a community-managed space that the team checks occasionally, it's a place where you can expect real answers from the people actually building Whistlr.
How do I get access to beta features or early testing through Campus?
Beta opportunities are posted in the dedicated beta and early access channel inside Campus. We recruit testers directly from the community there, and being active and constructive in the server is generally the best way to get noticed when a new beta opens up.
What should I post in Campus versus a SubCircuit?
If it's time-sensitive, exploratory, or a direct question for the team, post it in Campus. If it's something durable you want the broader community to find later, like a guide or a recurring topic, a SubCircuit with its own c/ handle is the better home, since it's built for long-term searchability and upvote-sorted quality.
Campus is open now at discord.gg/P67zcX9Ra, and the best way to understand what it's for is to show up and see who's talking. Drop into general chat, ask a question in feedback, or just lurk in announcements for a week. Either way, you'll be closer to how Whistlr actually gets built than a release note could ever get you.
