Circuits and Threads: How Whistlr Rebuilt Community Conversation

Threaded conversation is the part of social media everyone uses and almost nobody designs well. With Circuits, Whistlr rebuilt community discussion from the reply up—indented threads that stay readable, a "Best" ranking that surfaces the most thoughtful replies instead of the loudest, and moderation woven into the structure rather than bolted on after. This is the deep dive on how threaded conversation actually works inside Circuits, and the philosophy that shaped every decision.

If you have read our Introducing Circuits piece, you already know the shape of the feature: Circuits are Whistlr's home for interest-based communities, organized into focused sub-communities where people gather around a shared topic. That piece was the map. This one is the terrain. We want to walk through what happens after someone taps "Reply"—how a single comment becomes a tree of conversation, how that tree stays legible at depth, how the best contributions rise without a popularity contest taking over, and how moderators keep a discussion healthy without smothering it.

Most of what follows is grounded in how Circuits is actually built across Whistlr's web app and its native iOS and Android apps, on a shared Supabase backend. The terminology, the ranking behavior, the depth limits, the collapse rules—these are real mechanics, not marketing abstractions. Conversation design is unglamorous work, and the details are where it lives or dies.

Why Threaded Conversation Needed a Rebuild

The flat comment section is one of the oldest patterns on the internet, and one of the most broken. When every reply lands in a single chronological column, conversation collapses into noise. You cannot tell who is responding to whom. A sharp rebuttal sits three hundred comments away from the claim it answers. The first comment posted—often the least considered—wins the top slot purely because it was early. Anyone who has scrolled a viral post knows the feeling: thousands of replies, almost none of them in conversation with each other.

The other dominant pattern, the engagement-optimized feed of replies, is worse in a quieter way. When a system ranks replies by raw engagement, it learns that outrage travels faster than insight. The reply that makes people angry enough to quote-dunk it climbs higher than the reply that actually answers the question. Over time the incentives reshape behavior: people stop writing to be understood and start writing to be amplified. That is engagement bait, and it is the default failure mode of social conversation at scale.

Circuits was designed against both of these failures at once. Threading solves the "who is talking to whom" problem structurally—replies nest under what they reply to. And a deliberately non-viral ranking model solves the "loudest wins" problem—the default sort rewards quality and balance, not heat. The result is a conversation surface that reads like a discussion rather than a scoreboard.

"We did not want to build the fastest way to win an argument. We wanted to build the most readable way to have a conversation. Those are opposite goals, and almost every social platform quietly picked the first one."

— ETAPX Product Team

The Anatomy of a Thread in Circuits

Inside a Circuit, the top-level unit of discussion is the thread. A thread has a title, an author, and a body—and it can be a text post, a link, an image, or a video. That flexibility matters, because not every conversation starts the same way. Some begin with a question. Some begin with a shared article. Some begin with a clip. Circuits treats all of them as first-class openers for discussion rather than forcing everything into one mold.

Underneath each thread lives the conversation itself: a tree of comments. Every comment knows three things that make threading possible—the thread it belongs to, the parent comment it replies to (if any), and its depth in the tree. A top-level comment has no parent and sits at depth zero. A reply to that comment sits at depth one, nested and indented beneath it. A reply to the reply sits at depth two, and so on. This parent-child relationship is the spine of the entire system.

What a comment carries

A single comment in Circuits is richer than a line of text. Each one carries its author, its content, optional media or a GIF, an upvote and downvote count, a running tally of how many replies it has, its depth in the tree, and flags for whether it is pinned or has been edited. That metadata is not decoration—it is what lets the interface make smart decisions about how to display the conversation. The reply count tells the UI whether to show a "view replies" affordance. The depth tells it how far to indent. The pinned flag tells it to float a moderator's note to the top. The edited flag keeps the record honest.

• Author identity: every comment shows who wrote it, with verification and account-type badges where they apply, so context travels with the words.
• The OP marker: when the original poster of a thread replies inside it, their comment is tagged "OP," so you always know when the person who started the conversation is the one answering.
• Vote state: each comment tracks upvotes, downvotes, and your own current vote, which is what powers the ranking models we will get to shortly.
• Reply lineage: the parent-comment link and depth value are what turn a pile of comments into an actual tree.
• Edit and pin status: edited comments are labeled, and pinned comments rise to the top—both small honesty mechanics that add up.

From "Reply" to a Living Thread: The Composing Flow

The most important moment in any conversation system is the one right before someone contributes—the half-second where they decide whether replying is worth the friction. If composing a reply feels heavy, slow, or risky, people simply do not do it, and the conversation thins out into a few committed voices. Circuits treats the act of replying as something to make light and low-stakes without making it careless.

When you tap "Reply" on a comment, the composer opens inline, right beneath the comment you are answering, rather than yanking you away to a separate screen. That placement matters more than it sounds. Keeping the parent comment visible while you write keeps you anchored to what you are actually responding to—you are answering a specific person about a specific point, and the interface never lets you forget that. It is a small but constant nudge toward replies that are in conversation rather than replies that are just shouted into the thread.

A reply in Circuits is not limited to plain text. You can attach images, drop in a GIF, and your text is rendered with rich formatting and link previews, so a reply that includes a URL shows a clean preview card instead of a naked link. Mentions and links are parsed automatically. The goal is for a reply to be able to carry whatever the moment needs—a screenshot of the thing being discussed, a clip that makes the point faster than words, or just a sentence—without the composer ever feeling like a form to fill out.

Who is allowed to reply, and why that is a feature

Not everyone can reply to everything, and that restraint is deliberate. Replying inside a Circuit requires being a member of that Circuit, and a thread that has been locked accepts no new replies from anyone. There is also the depth rule we will get to in a moment: once a branch reaches the maximum visible depth, the inline reply affordance gives way to the "continue this thread" path. Each of these is a quiet form of conversation design. Membership-gated replies mean a community's discussion belongs to the people who have actually joined it, not to drive-by accounts looking for a megaphone. Locked threads mean a conversation that has ended stays ended. These are not limitations bolted on to frustrate people; they are the guardrails that let a community feel like a community.

"The cheapest way to ruin a conversation is to let anyone, from anywhere, drop in with no skin in the game. Requiring membership to reply is not a wall—it is the difference between a town square and a comment section."

— ETAPX Product Team

How Threads Stay Readable: Depth, Indentation, and the Branch Line

The single biggest enemy of threaded conversation is runaway nesting. Allow infinite depth and a long back-and-forth between two people drifts so far to the right that the text squeezes into a useless sliver. Cap it too aggressively and you flatten genuine sub-conversations back into the chaos you were trying to escape. Circuits draws this line carefully.

A deliberate depth limit

Circuits renders nested replies down to a maximum visible depth of four levels. Within those four levels, each reply is clearly indented under its parent, with a curved branch line drawn from parent to child so your eye can follow the lineage at a glance. The indentation shrinks the avatar size slightly at deeper levels, which keeps deep threads compact without making them illegible.

When a conversation runs deeper than the visible limit, Circuits does not silently truncate it. Instead it offers a "Continue this thread" link. Tap it and you drop into that branch as its own focused view, where the depth counter effectively resets and you can keep reading the sub-conversation in full. This is the crucial trick: the main view stays readable because it never indents past a sane limit, but no part of the conversation is ever lost. You can always go deeper—you just do it intentionally, in a view built for it.

"Four levels of nesting is enough to show a real exchange and short enough to stay readable on a phone. Everything past that becomes its own page. We would rather make you tap once than make every comment unreadable."

— ETAPX Engineering

Collapsing the noise

Depth limits handle width. Collapsing handles volume. A popular thread can accumulate hundreds of replies, and showing all of them expanded by default would bury the comments most people actually want to read. Circuits handles this with a simple, opinionated rule: when a comment has more than two replies, its reply tree starts collapsed.

A collapsed branch shows a compact pill—a small stack of the avatars of the people who replied, plus a count like "8 replies." Tap it and the branch expands, with a brief skeleton placeholder while the replies settle into place. Tap the vertical thread line again and the whole branch collapses back. Conversations with one or two replies stay open, because there is nothing to hide. Big branches stay tidy until you choose to dig in. The effect is that a thread with a thousand comments still reads like an outline you can navigate, not a wall you have to scroll past.

There is a quiet bit of state management behind this, too. If a branch is collapsed but new replies arrive and bring the count back down into the "small" range, Circuits will re-open it automatically. The goal is for the collapse behavior to feel like it is helping you, not fighting you—hiding bulk, never hiding the last word of a small exchange.

Surfacing the Best Replies—Without a Popularity Contest

This is the heart of the rebuild. Ordering replies is where a conversation platform reveals what it actually values. Circuits gives readers three sort modes for comments, and the choice of which one is the default says everything.

• Best: the default. Ranks replies by a blend of vote score and recency, so genuinely good comments rise but the conversation never goes stale.
• Top: pure vote score, highest net votes first. Useful when you want the most-endorsed take, with no time weighting.
• New: strict reverse-chronological, newest first. Useful for live threads where you want to see the latest as it lands.

What "Best" actually does

"Best" is intentionally not the same as "Top." A pure top-voted sort has a well-known pathology: early comments accumulate votes simply because they were visible early, then stay on top because they are on top. The rich get richer, and a thread freezes into whatever its first hour produced. "Best" breaks that loop by applying time decay.

Under the hood, each comment's score—its upvotes minus its downvotes—is divided by a function of its age. The older a comment gets, the larger the denominator grows, so its ranking gently fades unless fresh votes keep it relevant. A newer comment with a strong early signal can climb past an older comment with a bigger raw total. In practice this means a thoughtful reply posted an hour after the thread started still has a real chance to reach the top, instead of being permanently buried under whatever was fastest. It is the same family of time-decayed ranking that powers a healthy front page, applied at the level of a single conversation.

Two more rules sit on top of every sort. First, pinned comments always come first, regardless of mode—because a pin is an editorial decision, and the system should respect it. Second, ties are broken by recency and then by a stable identifier, so ordering never flickers or jitters when scores are equal. Small guarantees like stable ordering are invisible when they work and maddening when they do not.

"Defaults are policy. If we made 'Top' the default, we would be telling everyone that the goal is to win votes fast. By making 'Best' the default, we are telling them the goal is to say something worth reading—because a good comment posted late still has a path to the top."

— ETAPX Product Team

Up, down, and the honesty of a downvote

Voting in Circuits is two-directional: you can upvote a comment or downvote it, and your vote toggles—tap the same arrow twice and it clears. The interface updates instantly and optimistically the moment you tap, then reconciles against the server's authoritative answer so the count is always correct even if you tap quickly or your connection hiccups. That reconciliation logic exists specifically to prevent the drift that makes vote counts feel untrustworthy.

The downvote is a deliberate design choice, not an oversight. A platform that only lets you signal approval forces every reaction into a single channel, which is why like-only systems so often reward provocation—any reaction is a like-adjacent signal. A real downvote lets a community quietly de-rank a comment that is off-topic, hostile, or wrong, without anyone having to write an angry reply. It moves moderation pressure off the loudest voices and distributes it across everyone who is reading. The score that feeds "Best" and "Top" is net votes, so a community's collective judgment, not just its enthusiasm, shapes what rises.

Organizing Discussion: Categories, Flair, and Thread Kinds

Surfacing the best replies is only half the readability problem. The other half is helping people find the right conversation to begin with. Circuits solves this above the level of the individual thread, through a layer of organization that gives every discussion a place and a label.

Circuits themselves are grouped into categories—broad topic areas, each with its own icon and color—so the universe of communities is browsable rather than a flat alphabetical list. Within a Circuit, individual threads can carry flair: a small colored label that classifies what kind of post it is. A flair might mark a thread as a question, a discussion, an announcement, or whatever taxonomy a given community decides matters to it. Flair is lightweight, but it does real work: it lets a reader skim a busy Circuit and instantly tell a help request from a hot debate, and it gives moderators a way to encode a community's structure into the feed itself.

Threads also come in distinct kinds—text, link, image, and video—and Circuits renders each appropriately. A link thread shows a preview of its destination and tracks the domain it points to, which is both a convenience and a quiet trust signal: you can see where a link goes before you tap it. An image or video thread leads with its media. A text thread leads with its words. By treating the opening post's format as a first-class property rather than cramming everything into a single template, Circuits lets the shape of a conversation match the thing it is about.

Pinned context, set once

Every community accumulates the same recurring questions and the same need to state its norms. Circuits gives moderators pinning at both levels—a pinned thread at the top of the Circuit and a pinned comment at the top of a thread—precisely so that context can be set once and stay visible. A well-run Circuit often opens with a pinned thread explaining what the community is for and how to participate. It is the difference between a space that re-litigates its own rules every week and one that simply points newcomers at the pin.

The Conversation Design Philosophy: Healthy Discussion Over Engagement Bait

It is worth stating the philosophy directly, because every mechanic above is downstream of it. Whistlr's position is that the dominant metric of modern social media—time on platform, driven by engagement at any cost—is actively hostile to good conversation. Engagement bait works precisely because it short-circuits judgment: it provokes, it polarizes, it demands a reaction. A platform that optimizes for engagement will, over enough iterations, become a platform that optimizes for bait. That is not cynicism; it is just what the gradient points toward.

Circuits is built to point the other way. The design choices are small individually but consistent in direction:

1. Reward considered replies, not fast ones. Time-decayed "Best" ranking gives late, thoughtful comments a fair shot, so being early stops being a strategy.
2. Make the structure carry the meaning. Threading means a good reply is valuable because it answers something specific, not because it floats free as a standalone hot take.
3. Give communities a quiet way to say "less of this." Downvotes let a group de-rank bait without feeding it the angry-reply attention it is fishing for.
4. Keep the room legible. Collapse and depth limits mean the signal in a thread is findable, so the incentive to win by sheer volume drops.
5. Let moderators set the tone, not the algorithm alone. Pinning, locking, and rules give human stewards real leverage over the character of a space.

None of this makes Circuits slow or sleepy. Conversations still move fast, and "New" is right there for anyone tracking a thread live. The point is not to suppress energy. The point is to make sure the energy flows toward the comments worth reading instead of the comments engineered to enrage.

Moderation Built Into the Structure

Healthy conversation needs more than good defaults; it needs stewards with real tools. Circuits gives community owners and moderators a layered set of controls that operate at the level of the thread, the comment, and the community itself.

Roles that map to responsibility

Every Circuit has a clear role hierarchy: an owner, one or more moderators, and members. Owners and moderators carry the permissions that members do not—pinning, locking, removing content, and shaping the community's identity. This is not a flat free-for-all where everyone can do everything, nor a top-down lock-box where only the owner can act. It mirrors how real communities actually distribute trust: a small group of accountable stewards, supported by the collective signal of the members.

Thread-level controls

• Pinning: moderators can pin a thread to the top of a Circuit, or pin a comment to the top of a thread, to surface rules, context, or the answer everyone is looking for.
• Locking: a thread or conversation can be locked when it has run its course or turned toxic. Locking stops new replies while leaving the existing discussion readable—a far better outcome than deletion, because the record stays intact.
• Removal: threads and comments can be removed via soft deletion, which keeps the underlying structure consistent—replies do not orphan, counts stay coherent—while taking the offending content out of view.

Comment-level controls and self-governance

Authors can edit their own comments, and every edit is marked as such, so the conversation can be corrected without rewriting history. Authors can delete their own comments; moderators can delete any comment in their community. Crucially, the permission model is checked in the interface and enforced on the backend—the "Delete" button only appears for the comment's author or a moderator, and the action is validated server-side regardless of what the client claims. Trust and safety controls that live only in the UI are theater; Circuits enforces them where it counts.

Community rules and content moderation up front

Every Circuit can publish its own rules—short, numbered, community-authored standards that set expectations before anyone posts. When a moderator edits a community's description, rules, avatar, or banner, that content runs through automated moderation checks before it is saved. The same proactive checking applies to media uploaded to a community. The philosophy is the one we have written about before across ETAPX: catch problems at the moment of creation, not weeks later in a backlog. Moderation that happens up front is moderation that actually shapes behavior.

"A lock is more humane than a delete. When a thread gets heated, locking it preserves what everyone said and just stops the pile-on. We would rather freeze a conversation than erase it—erasure is how communities lose their memory."

— ETAPX Product Team

What the Old Way Got Wrong—and What Circuits Does Instead

It helps to be specific about the patterns Circuits is reacting against, because "we built better comments" is easy to say and hard to mean. Threaded discussion has decades of prior art, and most of the lessons are negative ones—things that seemed reasonable and turned out to corrode conversation. Circuits is, in large part, a catalog of those mistakes deliberately avoided.

• The old way: infinite nesting that turned long exchanges into a one-word-per-line column drifting off the right edge of the screen. Circuits: a four-level visible cap with a dedicated continuation view, so depth never destroys legibility.
• The old way: top-voted-forever ranking that locked threads into whatever their first hour produced. Circuits: a time-decayed "Best" default that keeps the conversation alive and gives late, good replies a fair shot.
• The old way: like-only reactions that funneled every feeling into approval and quietly rewarded provocation. Circuits: real downvotes, so a community can express disagreement structurally instead of through dogpiles.
• The old way: deletion as the only moderation hammer, erasing context and breeding distrust. Circuits: locking and pinning as primary tools, with soft deletion that keeps thread structure intact when removal is genuinely needed.
• The old way: open comment sections where anyone could parachute in with no stake in the community. Circuits: membership-gated replies that tie the conversation to the people who actually joined.
• The old way: walls of expanded replies that buried the good comments under sheer volume. Circuits: automatic collapsing of large branches into navigable, scannable outlines.

Read as a list, the pattern is obvious: nearly every choice trades a little raw engagement for a lot of readability and trust. That trade is the entire thesis. A platform optimizing for time-on-site would make the opposite call at almost every line. Circuits makes it on purpose, every time.

Accessibility and the Quiet Mechanics of Trust

A conversation surface is only as good as it is usable, and usability includes the people navigating with a keyboard, a screen reader, or simply a slow connection. Circuits carries the small affordances that make threaded reading workable for everyone: collapse and expand controls are labeled for assistive technology, the branch lines that connect parent to child are decorative and marked as such so screen readers do not narrate them as content, and loading states show lightweight skeleton placeholders so the layout never jumps under you while replies settle in.

There is a deeper kind of trust mechanic at work, too—the kind that lives in honesty rather than convenience. Edited comments are always labeled as edited, so no one can silently rewrite what they said after the fact. Soft deletion removes content from view without orphaning the replies beneath it, so a thread never becomes a confusing graveyard of replies pointing at comments that have vanished. Vote counts reconcile against the server so the numbers you see are the numbers that are real. Each of these is invisible when it works. Collectively, they are why a conversation in Circuits feels like a record you can rely on rather than a surface that might be quietly rearranged beneath you.

What This Means for Creators and Communities

For creators, Circuits changes the relationship between an audience and the person at the center of it. On a fast feed, a creator broadcasts and the audience reacts in a scattered, ephemeral stream. In a Circuit, a creator can host—starting threads that become durable gathering points, pinning the context that matters, and watching the best contributions from their community rise to where everyone can see them. Because verification and account-type badges travel onto a creator's comments, their voice is identifiable inside the conversation without being automatically dominant. A creator's pinned answer carries weight; their downvoted hot take does not get a free pass. That balance—presence without unearned authority—is exactly what a healthy community around a creator needs.

For community builders who are not creators in the broadcast sense, Circuits offers something the big platforms quietly stopped providing: ownership of a room. When you create a Circuit, you set its rules, choose whether it is public or private, shape its identity, and recruit its moderators. You are not renting space inside someone else's algorithm; you are stewarding a community whose conversation you actually control. The threading, ranking, and moderation tools are the same powerful machinery whether your Circuit has fifty members or fifty thousand—the difference is only in what you choose to do with them.

"The platforms taught a generation that an audience is something you accumulate and a community is something you cannot have. Circuits is built on the opposite belief: that the community is the point, and the conversation is where it actually lives."

— ETAPX Product Team

Private Circuits and the Right to a Smaller Room

Not every conversation should happen in public. Circuits can be public—anyone can view and join—or private, which makes them invite-only and keeps them out of open discovery. A private Circuit's content is locked behind membership, so a smaller group can have the kind of candid, lower-stakes discussion that simply is not possible on a fully open stage.

This connects directly to Whistlr's friend-first philosophy. The biggest social platforms collapse every relationship into one undifferentiated audience, which is why posting on them feels like performing. Private Circuits restore the idea that some rooms are smaller than others—that you can have a tight community of a few dozen people who actually know each other's context, alongside the big public Circuits where you go to meet new people around a shared interest. Threaded conversation works in both, but it means something different in each, and Circuits lets you choose.

Real Conversations: How It Plays Out

The question thread

Someone posts a genuine question to a public Circuit. Early on, a few quick answers come in—some helpful, some half-right. An hour later, a more knowledgeable member posts a careful, complete answer. On a pure top-voted system, that late answer would start at the bottom and likely stay there. Under "Best," its early upvotes, weighted against its young age, let it climb past the rushed replies. The original poster pins it. Now anyone who lands on the thread sees the right answer first, the question's author has signaled it, and the messy early attempts are still there for anyone who wants the full picture.

The heated debate

A controversial link sparks a long argument. Two members go back and forth, and their exchange nests four levels deep. Rather than letting it dominate the whole thread, Circuits caps the visible depth and offers "Continue this thread," so the two of them can take their debate into a focused branch while the main view stays readable for everyone else. When the argument curdles into personal attacks, a moderator locks that branch. Nothing is deleted, the disagreement is preserved, and the pile-on stops. The rest of the Circuit's conversation carries on undisturbed.

The big thread that stays navigable

A thread blows up to several hundred comments. Because every branch with more than two replies starts collapsed, the thread opens as a clean outline of top-level takes, each showing a little stack of replier avatars and a reply count. A reader scans the top-level comments, opens the two or three branches that interest them, and ignores the rest. The same thread on a flat comment system would be an unscrollable wall. Here it is a table of contents.

The Engineering Behind the Calm

A conversation surface that feels calm is doing a lot of work to stay that way. Circuits is served from a Supabase backend through a set of purpose-built database routines—listing comments by sort mode, creating and editing and soft-deleting them, toggling votes—each one a single round trip that returns exactly the shape the interface needs. The web app and the native iOS and Android apps share that same backend, which is why a thread reads consistently whether you open it on a laptop or a phone.

On the client side, requests are deduplicated so that two parts of the screen asking for the same comments do not fire two identical queries, and comment lists are cached so reopening a thread feels instant rather than reloading from scratch. Votes apply optimistically and reconcile against the server, so tapping an arrow never makes you wait. Web addresses for Circuits follow a clean, shareable, human-readable scheme, so a link to a specific thread carries its community, its identity, and its title right in the URL. None of this is the kind of thing a reader notices—but all of it is the difference between a conversation that feels responsive and one that feels like work.

How Circuits Fits the Wider Whistlr Ecosystem

Threaded conversation does not live in isolation. Circuits is one surface in a platform that also includes a personalized feed, short-form video in Minis, stories, live streaming, messaging, and in-app commerce. The connective tissue is identity and intent: the same profile that posts a Mini can start a thread in a Circuit, and the verification and account-type badges that travel with a creator everywhere on Whistlr show up on their comments too, so reputation is portable.

Where the feed is built for discovery and Minis are built for moments, Circuits is built for depth—the place you go when a topic deserves more than a caption. A creator might break news in a Mini and then host the real discussion about it in a Circuit. A community might form around a live stream and keep the conversation going in threads long after the broadcast ends. Circuits is the part of Whistlr designed to slow down just enough to let people actually talk—which is exactly the gap that fast-scrolling, engagement-maximizing social media leaves wide open.

Frequently Asked Questions

What are Circuits on Whistlr?

Circuits are Whistlr's interest-based communities, organized into focused sub-communities where people gather around a shared topic. Inside each Circuit, conversation happens in threads—posts with nested, indented replies—designed to stay readable and to surface the best contributions rather than just the loudest.

How does threaded conversation work in Circuits?

Every comment can reply to another comment, and replies nest beneath their parent with a branch line connecting them. Circuits shows up to four levels of nesting in the main view; deeper branches open in their own focused view via a "Continue this thread" link, so conversations stay legible without ever truncating the discussion.

What is the difference between the Best, Top, and New comment sorts?

"Best" is the default and ranks replies by vote score weighted against age, so good comments rise even if they were posted late. "Top" ranks purely by net votes, highest first. "New" shows the most recent replies first. Pinned comments always appear at the top regardless of which sort you choose.

Why does Circuits use a time-decayed ranking instead of just showing the most-upvoted comments?

Pure top-voted ranking rewards comments for being early rather than for being good—early visibility builds an unbeatable lead. By blending vote score with recency, "Best" gives a thoughtful comment posted later a real chance to reach the top, which keeps conversations fresh and discourages racing to comment first.

Can comments be downvoted, and why does that matter?

Yes. Circuits supports both upvotes and downvotes, and the ranking score is based on net votes. Downvotes let a community quietly de-rank off-topic or hostile comments without writing angry replies that would only amplify them—distributing moderation across everyone reading rather than concentrating it on the loudest voices.

How does moderation work inside a Circuit?

Each Circuit has owners and moderators who can pin threads and comments, lock conversations that have run their course, and remove content via soft deletion that keeps the thread's structure intact. Communities publish their own rules, and community content runs through automated moderation checks at the moment it is created or edited.

What happens when a thread gets locked?

Locking stops new replies while leaving the existing conversation fully readable. It is a deliberately gentler tool than deletion—it ends a pile-on without erasing what people said, so the community keeps its record of the discussion.

Are Circuits available on mobile as well as the web?

Yes. Circuits work across Whistlr's web app and its native iOS and Android apps, all sharing the same Supabase backend, so threads, votes, sorting, and moderation behave consistently wherever you open them.

Where Threaded Conversation Goes Next

Circuits as it exists today is the foundation, not the finish line. The architecture—comments that know their parent and their depth, ranking that values quality over speed, moderation woven into the structure—was built to be extended. The work ahead is about deepening the conversation, not just widening it: richer ways for moderators to highlight the contributions that define a community's culture, smarter tools for newcomers to find the threads where they can actually contribute, and more ways for the best discussions in a Circuit to reach the people who would care about them most.

What will not change is the principle underneath it all. Whistlr is betting that the future of social media belongs to platforms that treat conversation as something to be cultivated rather than harvested—that a readable thread of people genuinely talking is worth more than an endless scroll of people performing. Circuits is where that bet gets tested, one reply at a time. If we have built it right, you will not notice the engineering at all. You will just notice that, for once, the comments are worth reading.