Running a Mastodon account for a project or community

Posting as an organisation on a network built for people. What works, what gets you muted, and how to handle it when more than one person posts.

Mastodon is built around individual people, and it shows. An account representing a project, a community or a company is a slightly awkward fit — not unwelcome, but subject to expectations that are rarely written down anywhere.

Here is what those expectations actually are, from watching plenty of project accounts do well and plenty do badly.

Where to host it

Three options, in descending order of effort: run your own single-user server, join a server for your field, or join a general-purpose one.

Running your own gives you a handle at your own domain, which reads well and is genuinely more durable. It also makes you a server admin, with the moderation and maintenance that implies. Worth it if the account matters; overkill if you post monthly.

Joining a topical server puts you among the people you want to reach — but check its rules first. Some explicitly restrict organisational accounts, and finding that out after you have built followers is expensive.

What gets a project account muted

• Broadcasting only. An account that posts and never replies reads as a feed, not a participant. Replies are where the goodwill is.
• Announcement voice. "We are thrilled to announce" is the register of a press release, and it lands badly here.
• No alt text. On Mastodon this is close to a social requirement rather than a nicety, and a project account without it looks careless.
• Ignoring content warnings. If you post something people would reasonably want to opt out of, use one. The convention is stronger than elsewhere.
• Cross-posting visibly. A stream that obviously originated on another network reads exactly like that. Syndicate the durable things; write the conversational ones here.

When more than one person posts

Mastodon has no built-in concept of a team account — one login, one account. Which leaves you sharing a password, or using a tool with real seats.

A convention worth adopting either way: sign posts with initials when a specific person is speaking. It is a small thing that makes an organisational account feel like the people behind it, which is the whole game on this network.

A rhythm that works

Most successful project accounts settle somewhere around: a few substantive posts a week, replies whenever someone engages, and boosts of things the community made. The ratio matters more than the volume — an account that boosts and replies more than it broadcasts is read as a participant. Planning that rhythm is most of what keeps it going.

Alt text is not optional here

Worth its own section because it is the single most common way a project account signals it has not read the room. On Mastodon, describing your images is a normal expectation rather than an accessibility extra, and accounts that skip it get told — politely the first time.

It is also genuinely easy to systematise: write the alt text when you write the post, not at publishing time. Any tool worth using will let you attach it as part of the draft.

What to do about the algorithm you do not have

Coming from a ranked network, the instinct is to post more and hope something catches. Nothing catches here — there is no mechanism for it. What travels is boosts, and boosts come from people, which means the growth loop is entirely social.

In practice that means the highest-leverage thing a project account does is not posting at all. It is replying to people in your field, boosting their work, and being visibly a participant. The posts land better afterwards because people know who you are.

"On a network with no algorithm, reach is a social relationship rather than a distribution channel."

Handing it over

Project accounts outlive the person who set them up more often than personal ones do, so decide early where the credentials live and who has them. A shared password manager entry, not a Slack message.

If you run your own single-user server, this includes the server itself — which is the strongest argument for joining an existing one unless someone is genuinely committed to maintaining it.

Scheduling handles the substantive posts. It cannot handle the replies, and an account that only does the scheduled half is the one people mute. If you are setting that up, the practical guide is here.