Skip to content
Bloom · For developer relations

Bloom for developer relations and community.

Bloom is built for developer relations: it publishes to dev.to with a canonical URL back to your own blog, to Mastodon, Bluesky, Lemmy, Mbin, Misskey and Nostr where developer communities gather, and to the mainstream networks too — 18 in all, every one of which publishes. It reads comments and DMs back from 7 of them into one inbox so you can answer a thread without leaving, states plainly which networks it does and does not cover, and traces a click from a launch post to a named lead for community-program reporting. AI drafting runs on your own key.

Its own app & sign-in · honest coverage · your own AI key
18
networks, all publish
7
dev-community networks
7
answer in one inbox
10
report engagement
01 · Where developers actually are

Post to the networks devrel lives on.

Developer audiences are not concentrated on one feed — they are on dev.to, on Mastodon and Bluesky, in Lemmy and Mbin communities, on Misskey and Nostr. Mainstream schedulers skip most of these, so Bloom reaching all of them from one compose box is the difference between a devrel program that is present where its audience is and one that only shows up where scheduling tools happen to support.

dev.to, without cannibalising your blog

A dev.to cross-post carries a canonical URL back to your own site, so the republished article does not compete with the original in search. For a devrel team that writes long-form, that one detail is what makes dev.to a distribution channel rather than a duplicate-content risk.

Lemmy and Mbin, in their own shape

Link-aggregator communities expect a title-first post, not a caption. Bloom composes in that shape rather than forcing a microblog format onto them, which is the difference between a post that reads as native and one that reads as a bot cross-posting from elsewhere.

Nostr, signed in-house

Nostr events are signed with BIP-340 Schnorr signatures generated in-house and verified three ways against the official test vectors, so no third-party signer ever holds your key.

The full per-network detail — what publishes, what reads back, and why — is on the networks page.

02 · Answer the thread you started

The conversations come back into one inbox.

A devrel post is the start of a conversation, not the end of one. Seven of the eighteen networks return those conversations into one inbox — Instagram, Facebook, Threads, LinkedIn, Mastodon, Bluesky and Telegram — so you answer the developer who replied without opening seven tabs, and you answer as your project rather than a third-party handle.

Seven networks, five with DMs

Five carry real direct messages; Threads and LinkedIn are comments only — stated, not implied. Bloom replies through the same connected account the message arrived on.

Like from exactly two

Mastodon and Bluesky are the two whose APIs still allow it. A poll roughly every 60 seconds keeps a Mastodon reply feeling live; Meta accounts refresh every five minutes.

A reply is a send, not a post

Answering a comment does not wait for a publishing slot, and a revoked token stops that one account’s stream rather than the whole inbox.

The full coverage table and the Meta reply-window rules are on the inbox page.

03 · Communities punish bursts

Show up steadily, not all at once.

Developer communities are quick to read automation as spam, and a burst of catch-up posts the moment a worker recovers is exactly what that looks like. Bloom’s queue is built to show up steadily: rate limiting scoped to each account, and a hard cap on how fast a backlog can drain.

A cap that makes recovery gradual

After any downtime Bloom releases at most ten catch-up posts per five-minute tick, so a backlog drains over minutes rather than arriving as one wall of launch-day noise. A post more than 24 hours stale is skipped rather than published late, since a changelog that escapes two days late is worse than one that never went out.

No cold outreach, by design

Bloom does not do unsolicited DMs — they are not available on these APIs and would be the fastest way to lose a community’s goodwill. The inbox answers people who already replied or commented.

Spaced by a per-account governor

Each connected account has its own maxPerDay and minIntervalMinutes, so a release day that fans out across dev.to, Mastodon, Bluesky and Lemmy is paced per account rather than fired all at once.

The scheduling constants and their reasoning are on the publishing page.

04 · Honesty is a devrel asset

What Bloom covers, and what it refuses.

Developer audiences reward a straight answer and punish an overclaim, so Bloom prints its coverage rather than implying it. Here is what publishes and what Bloom refuses outright — each refusal stated here rather than discovered the week it matters.

Capability
Bloom
Note
dev.to article, canonical set
Publishes
Canonical URL points back to your own blog.
Mastodon / Bluesky native threads
Publishes
Up to 25 parts; engagement and inbox both read back.
Lemmy / Mbin title-first posts
Publishes
The link-aggregator shape those communities use.
Nostr, signed locally
Publishes
BIP-340 Schnorr signatures; no third-party signer.
Instagram Reels / YouTube Shorts
Publishes
Video publishing works on exactly these two.
Facebook / LinkedIn video
Refused
The publisher refuses rather than failing hours later.
TikTok, Instagram Stories
Refused
No adapter, no code path — stated, not implied.
Cold / unsolicited DMs
Refused
Not available on any of these APIs; the inbox answers replies.

Everything that publishes publishes today. The refusals are real product limits, not roadmap hedging: Bloom blocks a Facebook or LinkedIn video rather than accepting it and failing later, and it has no TikTok adapter at all. Stating that plainly is worth more to a technical audience than a coverage claim they will test and catch.

05 · Prove the program worked

Tie a signup back to the post that earned it.

Developer-relations programs are chronically hard to justify on impressions. Bloom’s short links carry a click from a dev.to article, a Mastodon thread or a talk announcement through to a conversion and a named lead, so a program reports the signups it produced rather than the reach it accumulated.

Short codes that survive a conference slide

Eight characters from a 32-character alphabet with the ambiguous glyphs removed, so a link read off a slide or typed from a talk lands where it should. Per-platform UTM parameters are written automatically, so the dev.to click and the Mastodon click do not collapse into one undifferentiated bucket.

Numbers a sceptical engineer will trust

Clicks are classified as bot, mobile or desktop, so an automated crawler does not inflate a program’s result. The loop closes on the 10 networks that report engagement; where a network will not — Nostr needs relay subscriptions — Bloom shows the reason rather than a zero that reads as failure.

Report the post, not the impression

A devrel program can say which migration guide, which release thread or which office-hours invite actually drove developer signups — one dataset from launch post to named lead, rather than a reach number nobody can connect to revenue.

Who it’s for

However your devrel program is shaped.

A team of one or a full platform-advocacy function, the same dev-community reach and the same honest coverage hold.

DevRel team of one

Present everywhere, alone

Publish a release to dev.to, Mastodon, Bluesky and Lemmy from one compose box and answer the threads it starts from one inbox — without opening seven tabs.

Platform advocacy

Where developers gather

Reach the fediverse networks mainstream schedulers skip, in each community’s native shape, so a post reads as a participant rather than a bot cross-posting from elsewhere.

OSS maintainer

Changelogs that land right

Pace a launch-day run with a per-account governor and a catch-up cap, and never publish a changelog two days late — a community reads a burst as spam.

Community program

Prove the program paid

Trace a talk announcement or a dev.to article through to a named lead, so the program reports signups it produced rather than impressions it accumulated.

06 · Questions

Developer-relations questions, answered plainly.

Which developer-community networks can Bloom post to?

dev.to, Mastodon, Bluesky, Lemmy, Mbin, Misskey and Nostr — the places developer communities actually gather — plus the mainstream networks, eighteen in all, every one with a real publisher. dev.to posts carry a canonical URL back to your own blog so a cross-post does not compete with your site, Lemmy and Mbin take title-first link-aggregator posts, and Nostr events are signed in-house with BIP-340 Schnorr keys so no third-party signer holds yours.

Can I answer comments and DMs from inside Bloom?

Yes, on seven networks: Instagram, Facebook, Threads, LinkedIn, Mastodon, Bluesky and Telegram. Five carry real direct messages; Threads and LinkedIn arrive as comments only, because Threads publishes no messages API and LinkedIn's is partner-only. Bloom replies through the same connected account the message came in on, so a developer sees your project, not a relay handle, and it can like from exactly two — Mastodon and Bluesky.

How does Bloom avoid looking like spam to a community?

A rate governor sits in front of each connected account with its own maxPerDay ceiling and minIntervalMinutes gap, and after downtime Bloom releases at most ten catch-up posts per five-minute tick rather than dumping a backlog. It also refuses cold or unsolicited DMs outright — the inbox answers people who already engaged, which is the behaviour a developer community rewards rather than punishes.

What can Bloom not publish?

No TikTok and no Instagram Stories — there is no adapter or code path for either. It cannot upload video to Facebook or LinkedIn and refuses the attachment rather than failing hours later; video publishing works on Instagram Reels and YouTube Shorts. X's v2 API is metered per post and its read access is paid, so there are no X analytics and no X inbox. Each limit is stated rather than discovered later.

Can a community program prove a post produced a lead?

Yes. Bloom's own eight-character short links carry per-platform UTM parameters automatically, classify each click as bot, mobile or desktop, and follow the click through to a conversion and a named lead. A devrel program can report which talk announcement, which dev.to article or which Mastodon thread actually drove signups rather than citing impressions.

Does Bloom read engagement from the dev-community networks?

From most of them. Engagement reads back from ten of the eighteen networks, including Mastodon, Bluesky, dev.to, Lemmy and Misskey. Nostr, Mbin and Plurk do not report it — Nostr needs relay subscriptions rather than a request — so Bloom shows the reason rather than an implied zero. The full read-back set is on the networks page.

Reach the community, and prove you did.

Bloom runs on its own application and its own sign-in — an Autocloz account is not required. Connect dev.to, Mastodon and Bluesky, schedule your next release the way a community will welcome, and trace the signups it earns.