Crossposter currently fans out to 12 channels: X/Twitter, LinkedIn, Bluesky, Mastodon, Instagram, YouTube, Dev.to, Pinterest, Peerlist, Hacker News, Nostr, and Dribbble.
The interesting part isn't the count, it's that they don't all work the same way, and the dashboard hides that from you at compose time.
Under the hood it's a deliberate mix:
- Official APIs where they exist and behave: LinkedIn, Bluesky, Mastodon, Dribbble (OAuth shot uploads), Nostr (kind-1 notes to your configured relays), Dev.to (markdown articles).
- Local unofficial integrations where personal posting needs it: X and Instagram via an isolated local headless browser, YouTube via YouTube.js/InnerTube cookies, Pinterest via local session folders, Peerlist via cookies + API requests, Hacker News via its normal web submit form.
You compose once, select targets, and Crossposter routes each one to the right mechanism. The composer abstracts over "this is a clean REST call" vs "this is a browser session" so you don't think about it per post.
The tradeoff is honest: the unofficial paths can break when platforms change, and you should only use accounts you own or manage. But you get genuinely broad reach from a tool with no cloud backend.
This very post hit Dev.to through that pipeline.
Top comments (0)