Discord publishing happens inside an active community. A bot message can interrupt people, create a new forum thread, expose a link preview, or land in the wrong operational channel. Safe defaults and exact destination verification matter as much as copy quality.
Current BlendDuck publishing contract
BlendDuck publishes a bot-authored message to one selected server channel or forum. Text supports up to 2,000 Unicode characters. A message can contain up to ten images or videos, including mixed media.
Each attachment must remain below BlendDuck's 24 MiB safety limit, and all attachments together must total at most 24 MiB so multipart overhead stays below the 25 MiB API boundary.
Mentions are non-notifying by default. Publishers can explicitly notify mentioned users, suppress push notifications, suppress link embeds, and mark attachments as spoilers. Forum and Media channels require a thread name from one to 100 characters and can include up to five comma-separated numeric tag IDs.
Choose the exact channel or forum
Confirm server, channel name, channel purpose, audience, bot permission, and moderation policy. Similar channel names are not sufficient evidence. For a forum, confirm the thread title and tag IDs against their visible labels.
Write for the channel's role. An announcements channel needs concise context and one next step. A support or feedback channel needs ownership and response expectations. A forum post should be searchable and durable rather than formatted like a transient chat line.
Avoid sending the same announcement to several channels without a channel-specific reason. Duplicate pings and repeated content can reduce trust even when the message is technically valid.
Control mentions, embeds, and attachments
Keep mention notifications disabled unless the campaign genuinely needs to alert named users and the community policy permits it. Review every mention in the final rendered text. A copied role-like string should never become an unexpected mass notification.
Choose silent delivery based on urgency and community norms. Inspect link embeds for accurate title, image, and destination, or suppress them when they add noise or expose stale metadata.
Use spoiler attachments when the community expects a deliberate reveal. Spoiler treatment does not replace safety review, content warnings in text, rights, or consent. Compress and validate attachments before scheduling rather than relying on the final API rejection.
Approval and delivery verification
Approval should bind the bot, server, channel, forum title, tag IDs, text, mentions, silent and embed settings, spoiler state, media order, size evidence, rights, and response owner.
After sending, verify the public message identity, destination, thread title, tags, mention behavior, notifications, embeds, attachments, and order. Record provider acceptance separately from a verified visible message.
For unknown states, inspect the channel before retrying. A duplicate forum thread or announcement can be more disruptive than a delayed post.
Measure community impact
Metrics should match the channel: link actions for announcements, resolved questions for support, qualified discussion for feedback, or participation in a forum topic. Include moderation effort, negative reactions, and notification complaints.
Record channel role, mention mode, delivery setting, format, outcome, response load, and next change. Use the result to improve community fit, not merely message volume.
Discord publishing checklist
- Exact server, channel or forum, bot identity, and permissions verified
- Text is within 2,000 characters
- Up to ten attachments remain within the 24 MiB safety total
- Mention notifications are intentionally enabled or disabled
- Silent, embed, and spoiler settings reviewed
- Forum title is 1–100 characters and tag IDs are correct
- Rights, media order, response owner, and approval checked
- Visible message, notifications, thread metadata, and delivery state verified
Current product limits were verified on 2026-08-23 against BlendDuck's Discord platform contract. Server permissions and community policy remain authoritative.
