Solutions ยท For Open source maintainers
Your release deserves more than a post and a prayer.
Publish and amplify project milestones across project and maintainer profiles on GitHub, Slack, Hacker News, Reddit, LinkedIn, X and Bluesky, from one queue.
Sound familiar?
Schedulers skip developer channels
None of the schedulers we checked support Hacker News, and most skip GitHub and Slack.
Maintainers are scattered
Everyone means to share the release. Few remember in the first hour.
Credibility is everything
One spammy post costs more trust with developers than a quiet launch.
What Blowhorn does for Open source maintainers
Every developer channel in one queue
Slack messages and GitHub reactions sit in the same queue as LinkedIn, X, Reddit, Hacker News and Bluesky.
Maintainers amplify as themselves
Each maintainer adds their own profile and joins the wave, posting as themselves.
No spam, no votes
Hacker News submit and comment only, at human pace, with built-in caps.
Scriptable
Every command has --help with examples, most have --json, and anything that publishes takes --dry-run.
Frequently Asked Questions
Does every maintainer need a Mac?
Each machine that acts needs macOS 13 or newer today. Windows and Linux: not today.
Will it upvote our launch?
Never. Blowhorn submits and comments on Hacker News and caps link submissions at 2 per profile per day.
Does the project need an account?
Yes. Every install signs in to one account, which keeps the queue, schedule and profiles in sync.
Not a bot. You, at full volume.
Read more before you download:
Blowhorn for other roles
-
For Agencies and consultants
Show the client the dry-run. Then send it once.
-
For Community managers
Rally the community. Everyone speaks for themselves.
-
For DevRel
Ship the release. Announce it everywhere, as you.
-
For Founders
You're the company's voice. Keep its keys.
-
For Marketing managers
Your team is the amplifier.