18 networks. All 18 publish.
Every network, and exactly what it does.
Most schedulers publish a logo wall. This is the same information as data, because the answer that matters is rarely “is it supported” — it is “supported to do what”. Publishing is universal here. Reading is not, and pretending otherwise would turn every unmeasured post into a zero that looks like failure.
| Network | Publish | Connect | Engagement | Inbox | Char limit |
|---|---|---|---|---|---|
| Yes | OAuth | Yes | DMs + comments | 5,000 | |
| Facebook Pages | Yes | OAuth | Yes | DMs + comments | 5,000 |
| Threads | Yes | OAuth | Yes | Comments only | 500 |
| Yes | OAuth | Yes | Comments only | 5,000 | |
| YouTube Shorts | Yes | OAuth | Yes | No | 5,000 |
| X | Yes (metered) | OAuth | No | No | 280 |
| Yes | OAuth | No | No | 5,000 | |
| Yes | OAuth | No | No | 5,000 | |
| Tumblr | Yes | OAuth | No | No | 5,000 |
| Mastodon | Yes | Direct | Yes | DMs + comments | 500 |
| Bluesky | Yes | Direct | Yes | DMs + comments | 300 |
| Telegram | Yes | Direct | No | DMs + comments | 4,096 |
| dev.to | Yes | Direct | Yes | No | 5,000 |
| Lemmy | Yes | Direct | Yes | No | 5,000 |
| Misskey | Yes | Direct | Yes | No | 3,000 |
| Mbin | Yes | Direct | No | No | 5,000 |
| Nostr | Yes | Direct | No | No | 2,000 |
| Plurk | Yes | Direct | No | No | 360 |
Nine networks no mainstream scheduler supports.
Buffer, Hootsuite and Later support none of the fediverse. Bloom publishes to all of it, which means a brand posting to these networks is competing with almost no other scheduled content — the rarest condition in social distribution. How those posts are spaced and retried is covered in publishing and scheduling, and what comes back from them in the unified inbox.
Mastodon & Misskey
Full text publishing with native threads on Mastodon, plus engagement read-back on both. Mastodon is also one of only two networks Bloom can like from.
Bluesky
Threads, engagement, real DMs through the chat service, and the AT-protocol record CID stored per post so a published item stays addressable.
Nostr
NIP-01 events published over Bloom’s own WebSocket connection, signed in-house with BIP-340 Schnorr signatures verified three ways against the official test vectors. No third-party signer holds your key.
Lemmy & Mbin
Title-first link-aggregator posting, with image upload on Lemmy and engagement read-back so community reach is measurable rather than assumed.
dev.to
Long-form developer publishing that returns a canonical URL, so the post can be cross-referenced from your own site without creating a duplicate.
Tumblr & Plurk
OAuth 2.0 and OAuth 1.0a respectively — two older protocols most modern tools have dropped, kept working here because the audiences did not leave.
A page for each of the nine
Each one states that network’s own character limit, how its account is linked, whether it reports engagement, whether its conversations reach the inbox, and which post shapes it accepts — the five things that actually differ between them.
Mastodon
500 characters, native threads, engagement, DMs and comments — and one of only two networks Bloom can like from.
Bluesky
The tightest ceiling at 300 characters, with threads, chat DMs and the AT-protocol record CID kept per post.
Misskey
3,000 characters — the longest of the microblog-shaped networks — with engagement read back and no inbox.
Lemmy
Title-first community posting with image upload at 5,000 characters, and engagement that actually comes back.
dev.to
Long-form cross-posting that returns a canonical URL, so the copy you do not own credits the one you do.
Nostr
NIP-01 events over Bloom's own WebSocket, signed in-house with BIP-340 Schnorr. No third-party signer.
Mbin
Title-first posting at 5,000 characters. No engagement source and no inbox source — stated, not shown as zero.
Plurk
360 characters over OAuth 1.0a, the only one of the nine still on a signature-based handshake.
Tumblr
The only one of the nine that connects by one-click OAuth 2.0, at the top of the range with 5,000 characters.
It tells you what it cannot do, at compose time.
Bloom carries three declared capability matrices — what shapes publish, what each network will report, and when a reply will be accepted — each defended by its own test. The rule they enforce is written into the source: a false success is the worst failure mode available.
Video, honestly
Video publishing works on Instagram Reels and YouTube Shorts. Bloom cannot upload video to Facebook or LinkedIn, and says so rather than accepting the file and failing later.
Liking, honestly
Bloom can like from two networks — Mastodon and Bluesky. Every other platform carries a written reason: Facebook removed the permission in 2018, Instagram and Threads expose no like endpoint, and LinkedIn’s reactions API is ambiguous enough that Bloom declines rather than send a request that does nothing.
Carousels, threads and the limits that apply.
Character limits differ by an order of magnitude — 280 on X, 300 on Bluesky, 360 on Plurk, 4,096 on Telegram — so Bloom tailors one idea per network instead of posting the same string everywhere and letting the shortest platform cut it off mid-sentence. The per-account rate governor then decides when each tailored copy actually goes out, and the Bloom overview shows how the whole loop fits together.
Coverage questions, answered plainly.
How many social networks does Bloom publish to?
Which networks does Bloom read engagement from?
Can Bloom read DMs and comments?
Does Bloom support TikTok?
Why does Bloom support Mastodon and Bluesky when other schedulers do not?
Publish once. Reach all eighteen.
Bloom runs on its own application and its own sign-in — an Autocloz account is not required. Connect one network or all eighteen and see the coverage table fill in against your own accounts.