Files
nexus/wiki/concepts/Multi-Channel-Delivery.md
2026-04-27 20:02:52 +08:00

36 lines
1.3 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
title: "Multi-Channel-Delivery"
type: concept
tags: [Notification, Delivery, Platform-Integration]
sources: [multi-source-tech-news-digest.md]
last_updated: 2026-04-27
---
# Multi-Channel-Delivery
多渠道分发——将内容或消息同步推送至多个平台Discord、邮件、Telegram 等),满足用户在不同场景下的信息消费习惯。
## Definition
同一内容通过多个独立的投递通道(频道)发送,每条通道可能有自己的格式规范、限流规则和用户触达方式。
## Common Channels
| 渠道 | 典型场景 | 特点 |
|------|----------|------|
| Discord | 社区通知、机器人推送 | Webhook、多频道、Rich Embed |
| Email | 正式报告、每日摘要 | MIME 格式、退信处理 |
| Telegram | 即时通知、私聊/频道 | Bot API、Markdown 格式 |
| Slack | 团队协作通知 | Webhook、Block Kit |
## Design Principles
- **平台适配**:每条渠道的内容格式需适配(如 Telegram 支持 MarkdownEmail 需纯文本 fallback
- **去重投递**:避免同一用户通过多个渠道收到重复通知
- **失败重试**:投递失败时的指数退避重试机制
## Related Concepts
- [[Content-Aggregation]]:多渠道分发的内容来源
- [[Cron-Job]]:定时触发多渠道分发任务的调度机制