Messaging that keeps up with your community.

A quiet channel needs almost nothing. A busy one needs structure, or it turns into a wall of text nobody reads. Every tool on this page exists to solve a specific readability problem, and each one comes with a judgment call. Here is how we think about them, including the trade-offs.

Replies for short detours, threads for long ones

A reply quotes the original message and keeps the exchange in the main channel, where everyone can see it. A thread moves the conversation into its own space. The trade-off is visibility: replies keep the channel informed but add noise, threads keep the channel clean but hide the activity from people who do not open them. Our rule of thumb: reply when the answer is useful to the whole room, thread when the detour would drown everything else. Either way, context stays attached, so nobody has to ask what a message is responding to.

Mentions that respect attention

Mentioning someone notifies them directly, which is exactly why mentions are easy to overuse. Save them for things genuinely worth interrupting a person for; a channel where every message pings somebody trains everyone to ignore the ping. Because members can carry per-server nicknames, the name you mention is the name people know them by in that community, not a username from somewhere else. And who can post where is shaped by your roles and permissions, so a busy announcements channel can stay writable by the few and readable by the many.

Pins are shared, bookmarks are yours

Pinning is a channel-level act: the pinned message becomes part of the channel's shared reference material, visible to everyone. Rules, schedules, the answer to the question that gets asked weekly; pin those. Bookmarks are the opposite: private markers only you can see, ideal for the message you want to act on later without announcing it. If you find yourself bookmarking the same message other people keep asking about, that is a hint it should be a pin instead.

Polls end circular debates

Some questions do not need forty messages of discussion; they need a count. A poll puts the options in the channel, collects votes where the conversation is already happening, and shows the result without anyone leaving to a third-party form. When a decision has stalled, a poll is often the politest way to close it.

Files without the friction

Attachments up to 25 MB ride along with messages. Images, video, and audio play inline, so a clip is watched in the channel instead of downloaded on faith; documents and everything else arrive as a clearly labeled download. One honest limit: this is a chat tool, not a file locker. For archives larger than the cap, share a link and let the channel carry the conversation around it.

When structure needs enforcement

Sometimes readability is not a formatting problem but a behavior problem. That is where slow mode, automated filters, and the rest of the moderation tools come in, with every staff action recorded in the audit log. Channels themselves can be grouped into categories, so a growing server splits cleanly instead of piling everything into one room. And custom emoji and server tags give each community its own shorthand, which does more for channel culture than you would expect.

And soon: automation

The upcoming bot engine adds an automation layer on top of all of this: welcome cards, auto-reactions, custom commands, a message log for moderators, and more. It is not live yet; it is built into the platform rather than bolted on, and it will arrive as a single switch in your server settings.