I Automated Cross-Posting to 5 Platforms and Broke 3 Things

说明与用途

自动化跨平台发布导致三大问题：共享草稿冲突、Markdown不兼容和隐藏的速率限制。解决方案包括为每个草稿使用独立数据库行、为每个平台使用Markdown模板以及使用节奏控制的调度器。

问题

Automating cross‑posting to multiple platforms caused failures due to shared mutable state, inconsistent Markdown rendering, and silent rate‑limit throttling.

结果

The pipeline now reliably publishes drafts to all five platforms without collisions, formatting errors, or silent throttling.

工作流

• 1. Store each draft in a separate database row with a unique ID.
• 2. For each platform, apply a per‑platform Markdown template to the draft body.
• 3. Use a scheduler that ensures a minimum time gap between posts to the same platform.
• 4. Publish the formatted draft to the target platform via its API.

证据

The fix was boring and correct: drop the shared file entirely. Each draft now lives in a database row with its own id, and the publisher reads by id.

来源

The fix wasn’t a universal formatter. It was a per-platform template: the same body, but headers, fences, and tags rewritten to each site's dialect before send.

来源

The fix was a scheduler with a real cadence: each pair gets a minimum gap, and no two posts share an hour.

来源