Community-Level Moderation
Security isn't just about technology — it's also about governance. RSocial gives community administrators built-in moderation and admin tools to enforce their own rules, remove unwanted content, and manage membership.
Because each RSocial instance is independently operated, community leaders set the standards for what is acceptable in their space. There is no distant corporate policies overriding local moderation decisions. You control who enters your community and what happens within it.
Read more — why local control beats distant policy
On mainstream platforms, the rules are written far away by a company balancing advertisers, public relations, and a billion strangers, then applied to your community whether they fit it or not. A post can be removed by a policy you never agreed to, or left up despite your objections, and there is rarely anyone to appeal to. RSocial inverts this: because every instance runs entirely on its own, with no central authority above it, the people who run a community — not a faraway company — hold the tools and make the decisions for their own space.
There's a practical reason this works better, not just a philosophical one. Moderating a billion strangers with one rulebook is an impossible job: any single policy is simultaneously too strict for some contexts and too loose for others, and the people enforcing it have no way to know the local norms of the countless communities it lands on. A small, self-run community is the opposite situation — the people setting the rules are the same people the rules affect, they know the context, and they can be reached and held accountable. Decentralising moderation doesn't mean "no rules"; it means rules made close to the people they govern, by people who actually have to live with the results.
Read more — what an administrator can actually do
In practice, that means an administrator can manage who is allowed to join, lock or remove accounts that break the community's own rules, and keep the content that belongs there. The standards are set by the community they actually affect, and enforced by the people who live in it — a small group that knows its members can moderate with context and fairness that a distant, one-size-fits-all policy never could. Different communities can run by different values, and none of them can override another. These controls are tied to roles, so only trusted administrators hold them — see Login & Account Security for how role-based access works.
Technically, these are privileged actions gated by the same admin authorization used everywhere else: the server checks the admin role carried in your signed token before it will carry out an account lockout, a removal, or a bulk clean-up, so the tools genuinely can't be triggered by an ordinary member poking at the interface. Account management — locking an account effectively sets a lockout on it, and removal deletes it — runs through the identity service, while content actions run against the graph store that holds posts, comments, and likes. It's worth being straight about the current state: today the toolkit covers membership management and clearing content at the category level, and it's still growing — finer-grained tools such as per-item moderation queues, reporting workflows, and an audit trail are on the roadmap rather than finished. What already holds firm is the principle: whatever tools exist are held by the local administrators of each independent instance, and no outside party can reach in.
Common Questions
Who decides the rules on an RSocial community?
The people who run that instance. There is no central company policy sitting above them, so each community sets and enforces its own standards.
Can another community, or "RSocial," override my moderation decisions?
No. Each instance is independent. Your decisions apply to your space, and no outside party can reach in to reverse them.