Get involved with Mastodon

From mastodon wiki

How to get involved with Mastodon, the project? How to contribute? Who are the nodes / people of contact? What could I do to help?

Temporary home for this effort was a Google doc (content now available and improved here, thus view only) started by maloki.

There also was a first Proto-#MastoWiki located at (must still be imported).


Add your mastodon handle here if you’ve contributed to this list:

List of ways to get involved

  • Outreach - talking about Mastodon
    • Other social media, facebook, twitter, tumblr, instagram etc.
    • Blog
  • Community Knowledge Production and Incorporation (mediating information internal to mastodon, in ways that demonstrate how mastodon can be used)
    • Trending toot archive / Recommended toot conversations (e.g., #mastodev #introduction #faq etc)
    • Wiki project
    • Archivable virtual conferencing on topics related to Mastodon infrastructure (social/programmatic)
    • Welcome Wagon: Keeping a lookout for new users in Local/Federated timeline. They tend to be easy to spot. “Hello World” “What do I do here” “what am I doing here” etc.
    • Introduction to Mastodon for non-tech people: quite a lot of good material has been published ca. Easter 2017 (I’ve collected some links in French: and English: - feel free to use). These are good references, as they were written by people also discovering Mastodon
    • A family of #s that aggregate conversations for people learning to code for the first time (e.g., #practicecoding, but working in tandem with a Wiki page or IM backchannel, perhaps)
  • Translations
    • We don’t have a home for this yet, but we can list different types of translations in the meanwhile.
      • 500c toots by Gargron or other “important” accounts)
      • blog posts (gargron’s medium posts etc)
      • Change log
      • Mail-list (we have one soon)
  • Focus Groups
    • Probably could have a better name than this, but a lot of the needs we see bubbled-up from users are very ad-hoc (e.g. "I'm a PoC and I'm having this bad experience", "I'm colorblind, could you fix these UI elements") and I'm wondering if there is a way we could formalize the process of getting input from folks who might otherwise be overlooked or have to rely on boosts to get their concerns heard. This could also help build a base of folks for (good, diverse) UX testing of new ideas, and possibly end up as good community outreach too.
    • Could this be facilitated with a #? Or should users be able to contribute anonymously in some fashion?
  • Wiki
    • Goals:
      • Each area should have a wiki area presenting information.
      • Each instance could contribute to a wiki project with a page characterizing itself with information about its history and/or ethos, directions to development leadership, FAQ, support/donation links, etc
      • Particular topics or meta discursive moments related to development, user appropriation, etc (e.g., forks, bots for particular purposes, temporary server instances for particular events) could also warrant their own page to document a history or living history of that particular thing. This could also mediate information dissemination in a way that doesn’t rely on assumed community leaders to arbitrate ‘relevant’ topics for discussion
    • Where we are:
      • #MastoWiki is the hashtag on Mastodon to follow the conversation
      • Early efforts for prototyping this project after Maloki’s first call started on this DokuWiki, thanks to We are now migrating this content to…
      • The new home in English for our wiki efforts: (hosted thanks to NeetShin aka
      • We started talking with NeetShin (who hosts too, a Japanese effort) about linking several languages and hope e.g. will be deployed soon. Say hello via email and create an account on to contribute and make it happen faster please (in particular, if you are a veteran Mediaki admin knowing perfectly how to handle deployments and links between several languages in the same entity, à la Wikipedia. We need help :))