The owner handbook.

Every large community was once three people wondering if anyone else would show up. What carried the good ones from there was rarely a clever channel layout or a viral moment. It was a founder who showed up daily, answered every early message, and treated the first members like co-founders rather than an audience. In the beginning, you are the culture. Post the way you want members to post. Ask questions in public instead of DMs so answers benefit everyone. If you disappear for a week in month one, so does your server.

Structure follows conversation, not the other way around

The most common early mistake is building a channel map of every topic you might someday cover. Twenty empty channels do not signal ambition; they signal that nobody is home. Let structure trail demand: when one subject keeps derailing a busy channel, that is your cue to split it. Threads handle the smaller forks, so a tangent can run its course without earning a permanent channel. When you do prune, do it openly and say why. Members forgive a merged channel far more easily than a ghost town.

Culture is set in the first hundred messages

Whatever your first regulars do becomes normal, and normal is nearly impossible to renegotiate later. Welcome newcomers by name. React to good posts so people learn what good looks like here. Correct gently in public and firmly in private. Give the community its own vocabulary early: custom emoji and server tags sound cosmetic, but shared symbols are how a group of strangers starts to feel like an in-group, and the tag your members carry across the platform is free, honest advertising.

Moderation is maintenance, not punishment

Most moderation is small and boring, and that is the goal. Automated filters catch the worst before anyone sees it. Slow mode cools a heated thread without silencing anyone. A quiet word fixes most of what remains. Escalate deliberately, warn before you act where you can, and write your reasoning down. Every action lands in the audit log automatically, which protects your moderators as much as your members: when someone claims they were removed "for no reason," the record answers instead of memory.

What ownership means here

On Vronify.chat, ownership cuts both ways, and you should design your rules knowing it. You own your server: its rules, its roles, its culture. Your members own their accounts: a ban only stops participation. A banned member keeps their account, every message they ever sent, and the DMs they received. Any member can also delete their account, which anonymizes it, or export their data at any time. Enforcement here controls access to your space; it never holds a person's history hostage. In practice this makes moderation calmer, because the stakes of a ban are the stakes of a ban and nothing more.

One honest trade-off worth understanding: direct messages are private, so only the people in the conversation see them, and we don't read private conversations. Community channels are visible to their community and its moderators, precisely so moderators can keep public spaces safe. Public accountability in shared rooms, real privacy in private ones. Our privacy page explains where each line is drawn.