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.

Источник