Communities
Organize rooms into communities, assign power intentionally, and keep moderation transparent.
Spaces and Moderation
ECCP spaces collect rooms, identities, and policy into a single navigable surface. They are a Layer 3 and Layer 4 experience built on top of Layer 1 and Layer 2 primitives.
Create a Space
A space is best treated as a governance boundary:
- it groups rooms under a shared purpose
- it defines who can invite, publish, or moderate
- it gives members a durable navigation entry point
Add Rooms Deliberately
Not every room needs to be attached to a space. Use spaces for discoverable communities, onboarding paths, and public or semi-public project structure. Keep sensitive rooms detached unless membership policy is clear.
Moderation Baseline
| Role | Can invite | Can redact | Can publish rooms | | --- | --- | --- | --- | | Member | Limited | No | No | | Moderator | Yes | Yes | Limited | | Admin | Yes | Yes | Yes |
Community Safety Checks
- Publish rules where new members can read them before posting.
- Separate moderation bots from ordinary chat automation.
- Document whether reports are handled locally or across federated nodes.
Switching Providers
ECCP keeps homeserver choice open. If a community outgrows its current provider, the migration plan should cover:
- space ownership
- room aliases and invites
- moderator identities and device verification
- bridge credentials and bot scopes