COVERAGE

14 platforms wired. 3 more coming.

Springy cascades one anchor essay into native drafts for every platform listed below. Each draft is critiqued against that platform's culture — a LinkedIn post, an X thread, and a Bluesky quick take all start from the same idea but read differently.

14 wired 3 roadmap API-first Playwright fallback Idempotent queue
Platform Category Format Auth Mode Status
LinkedIn Social / Micro 150–300 words ideal OAuth 2.0 API wired
X / Twitter Social / Micro 5–8 tweet thread OAuth 2.0 PKCE API wired
Threads Social / Micro ≤500 chars, conversational Meta Graph API API wired
Bluesky Social / Micro ≤300 chars / post App password API wired
Instagram Short-form / Video 30–60s Reel Meta + browser fallback API + Browser wired
TikTok Short-form / Video Vertical video + caption Content Posting API API wired
Facebook Social / Micro Page posts + photos Meta Graph API API wired
YouTube Short-form / Video Shorts only for now Google OAuth API wired
Medium Long-form SEO article (draft) Integration token API wired
Dev.to Long-form Markdown + tags (draft) API key API wired
Pinterest Social / Micro Pin + canonical link OAuth 2.0 API wired
Reddit Community Subreddit-targeted post Browser session Browser wired
Telegram Social / Micro Channel broadcast Bot API API wired
Discord Community Webhook → server channel Webhook URL API wired
Substack Newsletter Weekly newsletter Browser session (TBD) Browser roadmap
Rumble Short-form / Video Video upload Browser session (TBD) Browser roadmap
Quora Community Answer existing questions Browser session (TBD) Browser roadmap

API-first, browser fallback when there isn't one.

Where a platform exposes a usable API, springy uses it — faster, more reliable, better error handling. Where it doesn't (Reddit killed its free tier; Rumble / Quora / Substack never had one), springy uses Playwright to drive a real browser session you logged into once via springy browser:login <platform>. Session cookies are stored at 0o700 under config/.browser-data/.

Want a platform that isn't here?

Two paths, in order of how much time you want to spend:

  1. File a platform-request issue. Include a link to the API docs, the auth model (OAuth / API key / browser only), and whether you'd want to use it yourself.
  2. Write a plugin. Most simple text-posting platforms are 150-200 lines: a client, a setup flow, and a publisher. The plugin interface is documented, and plugins:new <name> scaffolds everything.