InfiniTeaInfiniTea Docs
Setup and Configuration

Message Sync

Message Sync lets you broadcast messages from one channel to listener channels in other servers that share the same broadcast code. This enables cross-server communication, federated announcements, and mirrored conversation channels.

How It Works

The system has two roles:

  • Broadcasts: A source channel that sends messages outward via a unique broadcast code.
  • Listeners: A target channel that receives messages from a broadcast code.

When a member posts in a broadcast channel, InfiniTea relays the message to all listener channels subscribed to that broadcast code. Edits, deletions, and reactions can optionally sync as well.

Setting Up a Broadcast

  1. Navigate to Message Sync in your server dashboard.
  2. Click New Broadcast.
  3. Select the Source Channel where messages will be captured.
  4. A Broadcast Code is generated automatically. Share this code with servers that want to listen.
  5. Configure Allowed Content toggles to control what syncs:
    • Create: Relay new messages.
    • Edit: Relay message edits.
    • Delete: Relay message deletions.
    • Attachments: Include file attachments in synced messages.
    • Reactions: Sync emoji reactions.
    • Links: Allow link content to pass through.
    • Parse Roles: Allow role mentions to render.
    • Parse Mentions: Allow user mentions to render.

Setting Up a Listener

  1. Obtain a broadcast code from another server's administrator.
  2. Click New Listener.
  3. Enter the Broadcast Code.
  4. Select the Target Channel where relayed messages will appear.
  5. Configure Content Filters to control what your server receives. Both the broadcast and listener must allow a content type for it to sync.

Content Permissions

Content types use an AND model: both the broadcaster AND the listener must have a content type enabled for it to pass through. This gives both parties control over what flows between servers.

Use Cases

  • Multi-server communities: Mirror announcements across related servers.
  • Alliance/coalition channels: Federated chat between partner communities.
  • Staff coordination: Sync moderation channels across servers managed by the same team.
  • Event broadcasts: One source pushes event updates to many listener servers.

Important Notes

  • Bot messages are not relayed to prevent infinite loops.
  • The broadcast code format is XXX-XXX. Keep it secure; anyone with the code can listen.
  • Deleting a broadcast stops all listeners from receiving further messages.