How the community works: sharing, remixing, and moderation

Sharing a clip

The community feed is a public commons for things made here. Only your own generations can be shared: the share flow starts from your library or the studio's transport bar, and the server checks the take belongs to you before anything is published.

Sharing is consent-first. Nothing goes public until you tick a required checkbox that reads, in full:

"Share publicly: anyone can hear this clip and read its script. I made it and I am happy crediting the engine and voice."

Ticking it publishes both the audio and the script, in full, on a public page. Every post credits the engine and the voice that spoke it; a clip here never pretends to be human or unattributed. Posts carry scripts up to 2,000 characters, can take an optional tag (audiobooks, podcasts, game dev, and so on), and can be submitted to the weekly prompt while one is active.

Handles and display names

Your first share creates your public identity: a display name (how you appear) and a handle (lowercase letters, numbers, and dashes, 3 to 24 characters) that becomes your profile URL at /community/u/your-handle.

Both are editable on the account page, where you can also create the profile early and claim a handle before your first share. One honest warning, printed right next to the field: changing your handle changes your public profile URL, and old links do not redirect.

Your community picture is its own setting. It does not follow your account picture automatically; a sync button copies it over when you want them to match, and when it is empty your posts show your initial.

The feed and the remix loop

The feed has a Latest tab, a Most loved tab, and, while a weekly prompt is running, a tab for that prompt's submissions. Tags filter the feed by what people are making.

Every post page shows the full script beside the player, and an Open in your studio button. Press it and your studio opens with the script loaded and the post's engine and voice preselected, ready to regenerate, rewrite, or redirect. Clips made with a cloned voice are the one exception: clones stay with their makers, so the studio opens on the default engine with the script loaded, and the post says so.

That is the loop the community is built around: hear something good, open its script, make your own version.

Discussions

The discussions forum sits beside the clip feed, with four categories: Help & how-to, Voices & engines, Ideas & feedback, and General.

Threads in Help & how-to support accepted answers: the person who asked marks the reply that solved it, and the thread carries a check so the next person with the same problem finds the fix fast. Threads and replies can be liked, and view counts are real.

Three charter lines render wherever people write: be specific; be kind to people, honest about work; and credit voices, because clips name their engine and voice here, always.

Moderation, honestly

Moderation runs in layers, and we would rather describe them plainly than pretend the feed polices itself.

First, deterministic guards: accounts younger than a day cannot post links, established accounts get at most two links per post, and posting is rate-limited to 3 new threads and 12 replies per hour.

Second, an AI text classifier reads every new thread and reply before it goes live. The policy it enforces: block only severe, high-confidence cases (explicit sexual content, threats, slurs, scams and spam), hold the ambiguous middle for human review, and allow criticism, frustration, and heated-but-honest disagreement. Held content stays pending with an honest message until a person clears it; if the classifier is ever unreachable, content waits for review rather than being silently published. Nothing skips the pipeline: content is held unless it is cleanly allowed.

Third, people. Any signed-in member can report a post, thread, or reply (one report per person per item), and three reports auto-hide the item until the team reviews it. Reviewers approve or remove from a queue; everything written by the team carries a visible Team badge, including the seeded starter threads.

Real numbers, nothing seeded

Play and like counters are real. They move only through database triggers and a dedicated play counter, so nothing on the page can inflate them: a play is counted when audio actually starts (not on page views), and likes require signing in.

There are no seeded likes and no fake activity. When a corner of the community is quiet, the empty state says "be the first", because that is the truth.