Mastodon will never send you the traffic that a viral TikTok does. It is not that kind of network. What it does send is a slow, steady trickle of senior engineers, infrastructure people, open source maintainers and security folks who read carefully, try things properly, and tell their team when something is good. If you sell a developer tool, that trickle can be worth more per visitor than anything else you post to.
The catch is that Mastodon culture is openly hostile to marketing. Not indifferent. Hostile. People moved there partly to get away from engagement farming and brand accounts. Post like a marketer and the outcome is not low reach, it is a mute, a block, or a report to your server admin. This guide is about the difference between being welcome and being invisible.
Mastodon is a network of servers, not a single site
Mastodon runs on ActivityPub, an open protocol. Anyone can run a server, and those servers federate with each other, which means a post on one server can appear in the timelines of people on thousands of others. There is no company in the middle deciding what gets shown. There is no central account database. Your handle carries the server in it, like name@hachyderm.io.
That architecture has one consequence that matters more than all the others: rules are local. Each server sets its own code of conduct, and admins enforce it. Some tech-oriented servers explicitly ban commercial promotion. Some allow it if you disclose your affiliation. Some do not care. Server admins can also defederate, which blocks an entire other server from ever reaching their users. If you sign up on a server with a reputation for spam, you inherit that reputation, and a large chunk of the network may never see you regardless of what you post.
So the first decision is not what to post. It is where to have an account. Read the server rules page before you sign up, the same way you would read a licence before shipping a dependency. Developer-leaning servers exist and are well moderated. Picking one puts you next to your audience and signals that you understand where you are.
There is no algorithm, so boosts and hashtags are your distribution
The home timeline is strictly chronological. Nothing is promoted, nothing is throttled, and no engagement trick moves you up. This is liberating and brutal at the same time. Liberating because you never have to guess what the feed wants. Brutal because if nobody boosts you, your post reaches your followers who happened to be looking, and stops.
Boosts, Mastodon’s reblogs, are the only real amplification mechanism. A post that one respected maintainer boosts can travel across dozens of servers in an hour. That means you are not writing for an algorithm, you are writing something a specific person would be willing to put their name behind by boosting it. Those are different jobs, and the second one is harder and more honest.
Hashtags do most of the discovery work that the algorithm does elsewhere. Search on Mastodon has historically been deliberately limited, with full-text search of other people’s posts either off or opt-in depending on the server and version. Hashtags are always searchable and followable, so people follow tags like #rustlang or #selfhosted the way they would follow an account. One or two accurate tags at the end of a post is normal practice. Ten tags reads as spam and gets you muted.
The unwritten rules that decide whether you are welcome
Mastodon has strong, widely shared norms that are not written in any terms of service. Breaking them is not a ban, it is worse. People quietly mute you and you never learn why your reach went to zero.
- Put alt text on every image. This is the single strongest norm on the platform. Posting an image without a description will get you corrected in public.
- Use content warnings for anything long, political, or off your usual topic. A CW is not censorship there, it is a courtesy that lets people choose.
- Write in full sentences and skip the engagement bait. No “agree?”, no thread hooks, no “drop a comment and I will send you the guide”.
- Be a named human with a filled-in profile and a pinned intro post. Faceless brand accounts get ignored.
- Disclose your affiliation when you mention your own product. Saying “I built this, so take it with salt” buys you enormous goodwill.
- Link sparingly. A timeline of nothing but links to your own site reads as a bot even if you wrote every word.
What actually works for a developer-facing product
The pattern that works is embarrassingly simple: publish the technical detail you would normally cut. Developers on Mastodon reward specifics. The bug you spent two days on, the API that returns a 200 with an error body, the migration that locked a table in production, the benchmark that surprised you. Post the thing itself, with the code or the error text, and let the fact that you built a product be background information rather than the point.
Concretely, that means a post about how a platform’s rate limits actually behave under burst load will do far better than a post announcing your changelog. Both can mention your product. Only one of them earns a boost. If your engineering blog has genuinely useful posts, Mastodon is one of the few places where a link to a deep technical writeup is welcomed rather than penalised.
Replies matter as much as posts. Because the network is small, answering a question in someone’s replies is a realistic way to be seen, and it is where trust is actually built. A useful answer from a real person with a history of useful answers is worth more than any campaign you could run.
Cross-posting to Mastodon without sounding like a bot
Automated cross-posting has a bad reputation on Mastodon, and it earned it. Most of it is a firehose of unedited tweets, complete with @-handles that point at nothing, hashtag stacks, and threads that arrive out of order. Some servers explicitly ban unattended crossposting bots.
You can automate the mechanics without automating the voice. Schedule the post, but write the Mastodon version deliberately: strip the X-style hashtags, expand the shortened link, add the alt text, and put the CW on if it needs one. The default character limit is 500, which is more room than X gives most people, so a post that felt cramped elsewhere can breathe here. This is exactly the kind of per-platform adjustment a scheduler should make easy rather than paper over. seenpaid publishes to Mastodon alongside 22 other networks, and treats it as its own destination rather than a mirror of your X feed.
Measure it, because the numbers are small and the value is not
Mastodon will show you the worst-looking numbers in your dashboard. A dozen boosts, a handful of replies, no follower spike. Judged on volume it looks like a waste of time, and plenty of people quit on exactly that evidence.
That judgement is usually wrong, and you can prove it either way in a month. Put a tracked link on the Mastodon version of your posts, keep it running for four weeks, and compare not traffic but conversion. It is common for a channel like this to send a hundred visitors and convert several of them, while a channel sending ten thousand converts one. Reach is a bad proxy for intent, and Mastodon is the clearest example of the gap.
The honest version of this advice is that Mastodon might not work for you. If you sell to marketers or consumers, it probably will not. If you sell to engineers, it deserves a real trial with real measurement rather than a guess. seenpaid connects read-only to your Stripe account and attributes revenue to individual posts, so a small channel gets judged on the money it brings in instead of the likes it fails to.