Social media scheduling for developers
seenpaid schedules posts for developers and developer advocates across the networks developers read: Dev.to, Mastodon, Bluesky, Lemmy, Nostr and a project Discord. Write a release note or an article once, and seenpaid checks each network’s length and media rules before anything is queued.
Card required. Billed when the trial ends unless you cancel in Settings first.
Which platforms matter
Our pick of networks for developers, and how often to post on each.
Full tutorials and write-ups in markdown. Reactions, comments and, when Forem reports them, page views come back into seenpaid.
How often: One solid article every week or two. (Our recommendation)
Instances such as Fosstodon and Hachyderm host many open-source maintainers. Favourites, boosts and replies are read back.
How often: One to three posts a day. (Our recommendation)
Custom feeds let people follow a topic such as a language or framework, not just accounts.
How often: One to three a day, same rhythm as Mastodon. (Our recommendation)
Link posts into programming communities. Upvotes and comments come back to seenpaid. Read each community’s rules first.
How often: No more than once a week per community. (Our recommendation)
A small, technical audience on an open protocol. seenpaid signs your note and sends it to relays.
How often: Mirror your short posts. (Our recommendation)
Release notes straight into your project server’s announcements channel through a webhook.
How often: Every release, nothing else. (Our recommendation)
Five posts to schedule
Sample drafts. Replace anything in brackets with your own details.
- 1
The release note, cut per network
v2.4.0 is out: --dry-run on every command, and Windows paths finally work. Full notes: [link]
- 2
The TIL
TIL: git worktree add checks out a second branch in its own folder, no stash needed. I use it to review PRs without losing my place.
- 3
The debugging write-up
How we cut CI from [before] to [after] minutes: the three caches that mattered and the one that made it slower.
- 4
The good first issue call
Looking for a first contribution? #[issue] adds a missing flag to the CLI, and a failing test is already waiting for you.
- 5
The deprecation heads-up
Heads up: the v1 config format stops loading in [version]. The migration script converts yours in one command: [link]
How the agent runs it
- 01Point seenpaid at your project’s homepage or docs at signup; it reads the page and drafts three first posts from it.
- 02Connect Dev.to, Bluesky, Lemmy and Nostr with your own token or app password, Mastodon through its sign-in, and Discord with a channel webhook. None of them wait on an app review.
- 03Write the release note once. The composer shows each network’s character limit as you type, so the short version gets written on purpose instead of cut off.
- 04Or let your coding assistant do it after you tag a release: it drafts the posts, runs validate_post, and schedule_post puts the Dev.to article and the short posts on the calendar.
- 05Check Results for reactions, boosts and upvotes per post, network by network.
Does revenue attribution apply to you?
If you sell sponsorware, a paid tier or a template through Polar, Lemon Squeezy, Gumroad or Stripe, attribution matches each sale to the post whose link the buyer followed. For an open-source project that sells nothing, leave it off: seenpaid is a scheduler without it.
Plan that fits
Solo
$19.99/mo · 5 workspaces, every platform in each
One workspace connects every developer network above, plus a personal LinkedIn or X later. Accounts are not capped. Every workspace connects all the platforms above, with as many accounts as you need. Every plan has every feature; they differ only by how many workspaces (brands) you run.
Questions
Can I cross-post a Dev.to article to Hashnode or Medium?
Dev.to is the one to rely on. Hashnode has required its Pro plan for API publishing since 13 May 2026, and Medium stopped issuing new integration tokens, so a new Medium account may not be able to connect at all.
Do I need to register a developer app on each network?
Not for these. Dev.to, Bluesky, Lemmy and Nostr take your own key or app password, Discord takes a webhook URL, and Mastodon signs in through seenpaid’s own app.
Which engagement numbers come back?
Dev.to reactions and comments, Mastodon favourites, boosts and replies, Bluesky likes, reposts and replies, Lemmy upvotes and comments, Nostr reactions counted over the relays the note went to, and Discord emoji reactions. There are no follower numbers.
Can I schedule from my editor or terminal?
Yes, through an AI coding assistant such as Claude Code or Cursor connected to seenpaid. The setup for each one is on the agent pages.
Also a fit
Schedule the week in one sitting.
Seven days to try it with your own accounts. Card required; cancel in Settings before it ends and you pay nothing.
Start the 7-day trial