The Problem That's Been Holding Mastodon Back
Let's be honest: Mastodon has always had an onboarding problem.
When you first sign up for Twitter or Instagram, you pick a username and you're done. The platform handles the rest. But Mastodon? You hit a wall immediately. Before you can even post anything, you're staring at hundreds of server options with obscure names like "fosstodon.org," "pixelfed.social," and "lemmy.ml." The decision paralysis is real.
New users don't know the difference between a general-purpose server and a niche community. They don't understand that picking the "wrong" server might mean missing out on certain communities or features. And most critically, they don't realize that this choice actually matters in a way it never has on centralized platforms.
This friction has been one of the biggest barriers to Mastodon's mainstream adoption. While the decentralized model is philosophically elegant and technically sound, it's also confusing for people coming from Twitter or Facebook. You can't just "join Mastodon." You have to join a specific server within Mastodon.
Now, after years of watching new users bounce off the platform out of pure confusion, Mastodon is finally taking action. The platform is rolling out a series of onboarding experiments designed to smooth that first experience. These changes might seem incremental, but they're addressing the exact friction points that have turned away hundreds of thousands of potential users.
Understanding the Fediverse Architecture and Why Server Choice Matters
Before we can understand why Mastodon's new onboarding features are such a big deal, we need to understand what makes Mastodon fundamentally different from every other social network you've ever used.
Mastodon isn't a single service. It's a federation. Imagine if instead of one Twitter owned by one company, there were thousands of Twitter-like services, all operated by different people and organizations, but all capable of talking to each other. That's the fediverse.
Each Mastodon server (or "instance") is independently operated. Some are tiny, run by hobbyists. Others are massive communities with thousands of active users. Some are general-purpose platforms welcoming all topics. Others are hyper-specialized around tech, art, gaming, or politics.
When you join a Mastodon server, you're creating an account with that specific server. Your username is actually @yourname@servername.social. This is fundamentally different from how Twitter works. Your Twitter handle is just @yourname because there's only one Twitter.
The beauty of this system is flexibility and resilience. If one server goes down, your entire network doesn't collapse. If a server's moderation policies don't align with your values, you can migrate to another server and keep your followers. No single company controls the entire platform.
But this design also creates friction. New users have to make an active choice about which server to join before they even understand what that choice entails. It's like asking someone to pick an ISP before they've ever used the internet.
For years, Mastodon's default recommendation was simple: join mastodon.social, the largest general-purpose server. This worked as a stopgap, but it created its own problems. Mastodon.social became overcrowded and slow. New users who landed there often experienced performance issues and missed out on discovering smaller, more welcoming communities that might have better suited their interests.


Mastodon's onboarding features are rated for their potential impact on user experience, with personalization estimated to have the highest impact. Estimated data.
The New Default Server Recommendation System
Mastodon's solution is elegantly simple on the surface: when you open the iOS or Android app to sign up, you'll now see a button recommending a specific server instead of just defaulting to mastodon.social.
Here's how the new system works. When you launch the Mastodon app for the first time, the system checks your location and language settings. It then recommends a server that matches both factors. If you're in Spain and have your phone set to Spanish, you might see a recommendation for a Spanish-language server rather than the English-language mastodon.social.
This addresses multiple problems simultaneously. First, it distributes new users across different servers rather than funneling everyone into one instance. This prevents any single server from becoming overwhelmed and keeps the network healthier overall.
Second, it helps users find communities closer to their geographic and linguistic region. A German speaker might feel more welcome on a German-language instance with local moderation and community norms.
Third, and perhaps most importantly, it reduces decision fatigue. Instead of choosing from hundreds of options with no guidance, new users get a curated recommendation that Mastodon has deemed appropriate for their location and language.
The recommendation algorithm isn't random. Mastodon is working with server operators to identify which instances should be featured in these recommendations based on stability, moderation quality, and community health. Servers have to meet certain criteria to be recommended: they need responsive admins, clear moderation policies, active communities, and reliable uptime.
This creates an incentive structure that improves the overall quality of the network. Smaller servers have a concrete reason to maintain good moderation and uptime. And new users have a reason to trust that a recommended server is actually worth joining.
However, Mastodon is being careful not to create a gatekeeping problem where only large, mainstream servers get recommended. The goal is diversity, not homogenization. The recommendation system will eventually support multiple dimensions beyond just geography and language.


Estimated data suggests that sustainability and scale are the most significant challenges in implementing onboarding improvements, with cultural and fairness issues also posing substantial hurdles.
Expanding Beyond Geography: Demographics, Interests, and Niches
The initial rollout of server recommendations focuses on geography and language. But Mastodon has bigger plans.
The platform is planning to expand its server recommendation categories to include demographics, interests, and specific communities. Imagine launching the app and being asked, "Are you interested in tech, art, gaming, or something else?" Based on that answer, you'd get a recommendation tailored to communities that actually match your interests.
This is where Mastodon's new onboarding approach gets genuinely clever. Most social networks try to figure out what you care about after you've already signed up. They recommend accounts to follow, topics to explore, and communities to join once you're already invested in the platform.
Mastodon is flipping that script. It's trying to match you with the right community before you even create an account. This addresses the core issue that's held back Mastodon adoption: the sense that this is too complicated and too fragmented.
For someone interested in Linux development, being matched with a tech-focused instance like fosstodon.org might make all the difference. They'll land in a community where the most popular posts are about open-source software, not just general conversation. The culture, discussion quality, and available resources will all be aligned with what they actually care about.
The challenge with this approach is scale and accuracy. Mastodon would need to classify hundreds of servers across multiple dimensions. It would need to update these classifications as instances change character, grow or shrink, and evolve their communities.
It would also need to avoid the problem of pigeonholing. Just because you're interested in tech doesn't mean every post you make will be about technology. Mastodon needs to recommend servers that are welcoming to diverse interests while still having a strong community identity.
The platform is apparently learning from competitors in how to do this well. Bluesky introduced "Starter Packs," which are curated groups of accounts to follow. Mastodon recently launched "Packs," which serve a similar function for accounts. But the new server recommendation system takes this concept to a deeper level.

The Addition of Packs: Finding Accounts to Follow
At the same time Mastodon is overhauling server recommendations, it's also introducing another feature designed to reduce friction: Packs.
When you first join Mastodon, your feed is empty. You have no followers, no one to follow, and no content to see. This is a critical moment. If you see a blank feed, you might immediately assume the platform is dead and leave.
Blue Sky solved this problem with Starter Packs, which are curated collections of accounts recommended to follow. A Starter Pack for photographers, for example, might recommend accounts of renowned photographers, photography gear reviewers, and photo editing tutorials. When a new user joins Bluesky, they can subscribe to relevant Starter Packs and immediately have an interesting feed.
Mastodon's Packs feature works similarly. When you first join a server, you'll see recommendations for Packs relevant to your interests. Subscribe to a few, and your feed fills with relevant accounts from across the fediverse.
This is crucial for addressing the cold start problem. New users don't struggle because they don't understand the technology. They struggle because they don't know who to follow and they see no content. Packs solve that problem with zero additional complexity.
What makes this particularly powerful in Mastodon's context is that accounts in a Pack can come from any server across the fediverse. So even if you join a small, niche server, you can immediately discover high-quality accounts from the wider fediverse. The small server becomes your home base, but your social graph extends across the entire network.

Estimated data showing the distribution of different types of Mastodon servers, highlighting the diversity in server focus and community engagement.
The Help Center: Reducing Friction with Better Documentation
Alongside server recommendations and Packs, Mastodon has launched a new help center specifically designed for new users.
The problem Mastodon has historically faced is that much of its existing documentation assumes familiarity with decentralized networks or technical jargon. Guides talk about "instances," "federation," and "Activity Pub" without always explaining what these terms mean for a typical user.
The new help center addresses this by starting from absolute zero. It explains what Mastodon is, how to sign up, how to find people to follow, how to post and interact, and how to use more advanced features like hashtags and content warnings.
Crucially, it doesn't assume you know what a server is or why it matters. It explains this in plain language: you pick a server (with help from recommendations), create an account on that server, and then you can follow and interact with people on any server.
The help center also addresses common confusion points. What happens if my server shuts down? Can I move to a different server? How is moderation different on different servers? What does it mean to boost something? These are questions new users have, and having answers readily available removes a major source of friction.
This might sound like a small thing, but documentation quality is historically one of the biggest barriers to adoption for decentralized platforms. When everything is new and unfamiliar, having clear guidance can be the difference between someone exploring further and someone giving up.
Why This Matters: The Adoption Gap That Mastodon Has Faced
To understand why these onboarding improvements are so significant, we need to look at the bigger picture of Mastodon's adoption.
Mastodon has been around since 2016. It's technically mature, robust, and proven. Yet it still has far fewer users than Twitter, even post-Elon-Musk, when there's been unprecedented pressure on new social network adoption.
Threads, Meta's Twitter competitor, reached 100 million users in two months. Bluesky, which launched with similar ambitions and a similar decentralized philosophy, has millions of active users. Mastodon, despite being older and having a deeper community, still struggles to break through to mainstream audiences.
The barrier isn't the technology. It's the onboarding experience. Mastodon is the hardest social network to join, period. And in an era where friction matters enormously for adoption, this is a significant competitive disadvantage.
Every potential user who hits the server selection screen and bounces is a lost opportunity. Every person who doesn't understand why instance choice matters and picks the wrong server, then has a suboptimal experience, is less likely to recommend Mastodon to others.
Mastodon's growth has been steady but slow. The platform has dedicated users who genuinely love it. But it's never achieved the hockey-stick growth curve that characterizes successful social networks.
These onboarding improvements are designed to change that trajectory. By reducing friction and decision fatigue, Mastodon is trying to move from "a technical platform for nerds" to "a social network for people."


Estimated data showing Mastodon's shift from Discord to Zulip, reflecting its commitment to open-source tools.
The Infrastructure Evolution: Moving to Open Source
While Mastodon is improving its user-facing onboarding, the organization is also making significant changes to its underlying infrastructure.
Mastodon recently announced that it's leaving Discord and migrating its entire communication platform to Zulip, an open-source chat application. This might seem like a small internal decision, but it reflects Mastodon's broader philosophy.
Mastodon is a decentralized, open-source social network. Yet for years, it relied on Discord, a proprietary tool owned by a venture-backed company, for internal team communication. This created a philosophical tension and a practical vulnerability. If Discord changed its policies or pricing, Mastodon would be affected.
By moving to Zulip, Mastodon is practicing what it preaches. It's using open-source software where possible and reducing dependency on proprietary platforms.
This decision came in response to Discord's announcement that it would be rolling out age verification measures globally. Mastodon's team decided this was a good time to diversify its infrastructure.
For users, this is less immediately relevant than the onboarding improvements. But it reflects Mastodon's long-term commitment to decentralization and user freedom. The platform isn't just trying to be a good Twitter alternative. It's trying to build a fundamentally different model for social networking where users have more control and organizations have less ability to impose restrictions.

Comparing Mastodon's Approach to Competitors
How does Mastodon's new onboarding strategy compare to what other platforms are doing?
Threads, Meta's social network, has onboarding that's trivial: if you have an Instagram account, you're already signed up for Threads. This is frictionless, but it's also lock-in. You're essentially forced onto Threads if you want to use Instagram.
Bluesky has more friction than Threads but less than old Mastodon. You create an account on bluesky.social (though third-party servers are coming). Then you follow starter packs to build your feed. The experience is smoother than pre-2025 Mastodon but still requires understanding concepts like "invite codes" (for access during the waitlist phase).
Mastodon's new approach is actually closer to what web browsers do with default search engines. Firefox recommends certain search providers based on your region. Mastodon is applying the same principle to servers.
The difference is that Mastodon's default is more consequential. You can change your search engine anytime. Changing your Mastodon server requires more work. So Mastodon needs to be more careful about recommendations.
But in principle, the approach is sound. Don't overwhelm users with choices. Make a good default recommendation that they can override if needed.


Estimated data shows a diverse range of Mastodon servers, with general-purpose servers being the most common, followed by various specialized communities.
The Server Ecosystem and What Makes Certain Instances Recommended
For the new recommendation system to work, Mastodon needs high-quality servers to recommend.
Not every server qualifies. The platform has specific criteria: administrators must be responsive and community-focused, moderation policies must be clear and consistently enforced, the community must be active and welcoming, and uptime must be reliable.
A server that's slow, poorly moderated, or frequently down won't get recommended, regardless of size. This creates an incentive structure where smaller server operators have a concrete reason to maintain quality. They want to be recommended.
Conversely, a large but poorly-managed server might find itself losing new users to recommendations, pushing them toward better-operated alternatives. This is a feature, not a bug. Mastodon's health depends on distributed users across many well-run instances, not concentration on a few massive ones.
The problem this creates is that server operators need to know what criteria Mastodon is using. Transparency here is critical. If server admins don't understand why they're being or not being recommended, they can't improve.
Mastodon appears to be aware of this. The platform is working directly with server operators to set expectations and provide feedback. This is collaborative infrastructure building rather than top-down control.
The long-term vision seems to be a tiered ecosystem. A few flagship instances recommended to all new users as defaults. Themed instances (tech, art, gaming, etc.) recommended based on user interests. And countless smaller communities for people seeking more niche spaces.
This would create a stronger onboarding funnel while preserving the diversity that makes the fediverse valuable.

Geographic and Linguistic Personalization in Recommendations
The first implementation of recommendations focuses on geography and language. This is a smart starting point for several reasons.
First, it's technically straightforward. The app already knows your phone's language and approximate location (through the app store or explicit user settings). Using this data to recommend servers is privacy-respecting and doesn't require collecting additional information.
Second, geography and language matter for social networking in ways that aren't immediately obvious. A Spanish speaker might technically be able to use an English-language server, but they'll have a better experience on a Spanish server. The moderation policies will make sense in their language. The local context and inside jokes will be relevant. The community norms will feel natural.
Third, geographic distribution helps with the network effects problem. If all new users get funneled to mastodon.social, that server becomes a single point of failure. If recommendations distribute users across geographic servers, the network becomes more resilient. A server going down affects fewer people and has less impact on the overall platform.
As Mastodon expands recommendations to include interests and demographics, the complexity will increase. But geographic and linguistic recommendations are a solid foundation.
The platform is being smart about data here. It's not tracking individual user interests in Mastodon to make recommendations. It's using metadata the user has already opted into providing (language, region). This respects privacy while still personalizing the experience.


Effective moderation and active administration are crucial for server quality in Mastodon's decentralized network. Estimated data.
The Role of Server Operators in Network Health
Mastodon's decentralized model only works if individual server operators do their job well.
This is both a strength and a vulnerability. It's a strength because it prevents any single point of control. No company can decide to change Mastodon's terms of service overnight. If you disagree with a server's policies, you can leave and join another, or even start your own.
But it's a vulnerability because the quality of the network depends on distributed human judgment. A server with a bad admin is a bad server. A server with no moderation is a nightmare. A server that's abandoned gets deleted, and users on that server lose their community.
Mastodon's new recommendations give the organization a tool to incentivize good behavior at the server level. Servers that are well-run get promoted. Servers that are poorly-run don't. This isn't coercive. Bad servers can still exist. But new users will tend to land on good servers.
Over time, this should improve the average quality of the Mastodon experience for new users. Instead of randomly landing on a struggling instance with an inactive admin, new users get recommended instances that are stable, well-moderated, and active.
This also creates a feedback loop. As more new users land on well-run servers, those communities grow and attract more attention. The growth reinforces the quality. Bad servers lose users to better alternatives.
For long-term adoption, Mastodon needs this approach. Decentralization is philosophically sound, but users want to join communities, not just infrastructure. Recommendations help users find healthy communities within the decentralized ecosystem.

The Competitive Landscape and Timing of These Changes
Why now? Why is Mastodon overhauling its onboarding in 2025?
The most obvious answer is that competitive pressure has increased dramatically. Threads launched with Meta's massive resources. Bluesky is growing rapidly and getting mainstream attention. The window for Mastodon to capture mainstream users is closing.
Elon Musk's takeover of Twitter in 2022 created an opportunity. Millions of people looked for alternatives. Mastodon benefited from this, but not as much as it could have. Many of those users came, found the onboarding confusing, and left.
Mastodon's leadership clearly realized they couldn't rely on external crises to drive adoption. They needed to make the platform inherently easier to use.
The second reason is technical maturity. Mastodon has been around for nine years. The platform is stable. Server infrastructure is mature. The fediverse is proven to work at scale. Now the priority has shifted from building the technology to making it accessible.
The third reason might be funding. Mastodon went through a significant fundraising round in 2024, raising millions from investors and organizations. This gave the project resources to invest in product and user experience improvements, not just maintenance and infrastructure.
From a competitive standpoint, these changes put Mastodon on more equal footing with Threads and Bluesky. None of these platforms are as easy to use as Twitter (which had years to perfect its onboarding), but Mastodon is closing the gap.
If these changes work as intended, we should expect to see higher conversion rates for new users. More people will complete onboarding. More of those users will stick around. More will invite friends.
This is how networks achieve escape velocity.

Looking Forward: What's Next for Mastodon Onboarding
These onboarding improvements are just the beginning. Mastodon has signaled that this is an ongoing focus area.
In the immediate term, we should expect to see more experimentation with the server recommendation algorithm. The platform will test different recommendation criteria and measure which approaches actually result in higher retention and engagement.
We'll also probably see Packs evolve. More curation. Better categorization. Maybe algorithmic recommendations for accounts to follow based on what others in your pack are following.
The help center will expand. As new users encounter problems, Mastodon will document solutions. Over time, the platform will have answered every common question and resolved every common source of confusion.
Beyond onboarding, Mastodon is working on other friction points. The mobile app experience continues to improve. The web interface is becoming more intuitive. Integration with other fediverse platforms is getting better.
But the biggest opportunity is still onboarding. Every user who makes it past that first day is a potential long-term community member. Every user who gets stuck on the server selection screen is a loss.
Mastodon seems to finally understand that friction early in the journey compounds. Better onboarding isn't just a nice-to-have. It's essential for platform growth.

The Philosophy Behind Decentralization and Why It's Worth the Complexity
It's worth pausing here to ask a harder question: why is Mastodon pursuing decentralization in the first place if it creates so much friction?
The answer comes down to values and control. On Twitter or Meta or Threads, you don't actually control your account. The company does. They can change the algorithm, remove content, ban you, or shut the platform down entirely. You're using their product on their terms.
On Mastodon, you actually own your data. You control your content. You can move to a different server if you disagree with one server's policies. You can run your own server if you want complete autonomy. No single company or person controls Mastodon.
This isn't just theoretical. We've seen Twitter and Reddit make decisions that billions of users disagreed with. We've seen platforms reverse their policies under pressure or whim. We've seen networks shut down or dramatically change character.
Decentralization prevents this. It pushes power away from a central authority and distributes it across many servers and communities. This is harder to use, but it's more resilient and more respectful of user autonomy.
Mastodon's job is to make that decentralized structure as frictionless as possible while preserving its benefits. Recommendations do exactly that. They simplify the first experience without centralizing control. They help users find communities without forcing them to one specific server.
If these onboarding improvements work, Mastodon might finally prove that decentralized social networks can compete with centralized ones on ease of use. That would be a significant shift in how people think about social media.

Implementation Challenges and Potential Issues
Despite the promise of these onboarding improvements, implementation will be challenging.
The first challenge is scale. Testing recommendations on 1% of new users is one thing. Rolling it out globally is another. Edge cases will emerge. Some recommendations will perform poorly. Some servers will be recommended inappropriately. Mastodon will need to rapidly iterate based on data.
The second challenge is fairness. How does Mastodon decide which servers get recommended? What criteria are transparent? What happens to servers that aren't recommended? If server recommendations concentrate new users on a small set of instances, is that actually better than the old system where everyone went to mastodon.social?
The third challenge is cultural. Different servers have different vibes. A Spanish-language server might be perfect for Spanish speakers, but what if someone from Mexico joins a Spain-focused server? What if a server's culture shifts over time? Recommendations need to be fluid and responsive to changes.
The fourth challenge is sustainability. Building and maintaining a good recommendation system is ongoing work. It requires data collection, analysis, and continuous improvement. Mastodon needs to commit resources to this indefinitely, not just as an experiment.
Mastodon seems aware of these challenges. The platform is intentionally rolling this out as experiments, not permanent features. This allows for iteration and learning before full deployment.
But ultimately, the success of these features depends on execution. A poorly-designed recommendation system could actually make the onboarding experience worse.

The Bigger Picture: Open Source and User Sovereignty
Mastodon's decisions about infrastructure and onboarding reflect a broader philosophy about technology and user power.
Moving from Discord to Zulip is one example. Mastodon could easily stay on Discord. Most tech communities do. But Mastodon is choosing open-source alternatives where possible because it aligns with the platform's values.
This same philosophy underlies the entire Mastodon project. Instead of building a proprietary social network and selling it to users, Mastodon built an open protocol that anyone can use. The code is open. The design is collaborative. The platform belongs to its users, not to a company.
But open source and decentralization only work if regular people can actually use them. That's where better onboarding comes in. If Mastodon is so complicated that normal people can't figure it out, then it doesn't matter that it's open source. It's only accessible to technical experts.
Mastodon's new onboarding features are an attempt to bridge this gap. They preserve the benefits of decentralization while removing the friction that keeps casual users away.
If successful, these changes could influence how other decentralized platforms approach onboarding. They could prove that decentralized systems don't have to be harder to use than centralized ones. The difficulty is often a product of poor design, not inherent limitations of the technology.

Conclusion: The Start of Something Important
Mastodon's new onboarding features are significant, but not for the reasons you might initially think.
Yes, server recommendations and Packs will help new users get started more quickly. Yes, the help center will answer common questions. These changes will reduce friction and improve the first-time experience.
But the deeper significance is that Mastodon is finally prioritizing the most important part of the user journey: the beginning. For years, the platform's growth was limited by its assumption that people would push through complexity because they understood the values behind decentralization.
That assumption was wrong. People don't join social networks for philosophy. They join for community. They stay for connection. If the first experience is confusing and frustrating, none of the philosophical benefits matter.
Mastodon is learning this lesson, a bit late maybe, but decisively. The platform is investing seriously in onboarding because it understands that this is where growth happens.
The experiment-based approach is smart. Mastodon isn't rolling out permanent changes. It's testing and learning. This allows the platform to iterate quickly and improve recommendations based on real-world data.
The geographic and linguistic recommendations are a solid foundation, but the real opportunity is broader personalization based on interests. That's harder to implement well, but it's also more valuable. A new user matched with a tech-focused server or community is more likely to find their people.
For Mastodon's long-term success, these changes matter enormously. The platform has a limited window to capture mainstream users before the zeitgeist moves on to the next new thing. These onboarding improvements help Mastodon compete on ease of use, which is essential for adoption.
But success isn't guaranteed. Execution matters. The recommendations have to be good. The servers have to be worth joining. The community has to be welcoming. Poor implementation could actually harm the onboarding experience.
Mastodon also faces the challenge that decentralization will always have some inherent complexity. You can reduce friction, but you can't eliminate the fact that users are choosing between different communities with different rules and cultures. This is actually a feature, not a bug, but it requires education.
The platform's move to open-source infrastructure and away from proprietary services reflects the right values. But it also creates ongoing complexity. Zulip is great, but it's also less polished than Discord in some ways. Open standards are valuable, but they're sometimes slower to improve than proprietary alternatives.
Ultimately, Mastodon is betting that people care about user sovereignty and decentralization more than they care about pure convenience. These onboarding changes are designed to prove that bet. They're attempting to show that you can have both: a platform that's easy to use and a platform that respects your autonomy.
If these experiments succeed, we should expect to see higher growth rates for Mastodon in 2025 and 2026. More new users will convert. More will stick around. More will become advocates.
The social web is changing. Centralized platforms are facing backlash. Users are increasingly concerned about privacy, content moderation, and algorithmic control. Decentralized platforms like Mastodon are positioned to benefit from these trends.
But only if they can clear the adoption hurdle. These onboarding improvements are a serious attempt to clear that hurdle. The next year or two will show whether it's working.

FAQ
What exactly is Mastodon and how is it different from Twitter?
Mastodon is a decentralized social network that works similarly to Twitter but isn't controlled by any single company. Instead of one Twitter owned by one organization, Mastodon consists of thousands of independent servers that all communicate with each other. When you join Mastodon, you create an account on a specific server (like mastodon.social or fosstodon.org), but you can still follow and interact with users on any other server in the Mastodon network.
What is a Mastodon server (instance) and why do I have to choose one?
A Mastodon server, called an instance, is an independent installation of the Mastodon software operated by different people or organizations. Each server has its own moderation policies, community culture, and rules. You create an account on a specific server, so your username includes the server name (like @yourname@mastodon.social). Choosing a server matters because it affects what moderation policies you're subject to, what communities you're part of, and what content is visible on your local feed.
How do the new server recommendations work?
When you sign up for Mastodon using the mobile app, the system checks your phone's language setting and approximate location (from the app store metadata). Based on this information, it recommends a server that matches your language and region. For example, a Spanish speaker in Barcelona might see a recommendation for a Spanish-language instance. You can still choose a different server manually, but the recommendation provides guidance for new users.
What are Mastodon Packs and how do they help?
Mastodon Packs are curated collections of accounts recommended to follow, similar to Bluesky's Starter Packs. When you first join Mastodon, your feed is empty. Packs let you subscribe to themed collections of accounts (tech accounts, art accounts, gaming accounts, etc.) and immediately see interesting content. This solves the "cold start" problem where new users would see blank feeds and leave.
Why is Mastodon moving away from Discord and switching to Zulip?
Mastodon is transitioning from Discord to Zulip, an open-source chat application, as part of its broader commitment to using free and open-source software. Discord is proprietary and owned by a venture-backed company, which creates philosophical tension with Mastodon's decentralized values. The switch was accelerated by Discord's recent announcement of mandatory age verification globally, which Mastodon's team determined was a good moment to diversify infrastructure.
Can I change my Mastodon server if I pick the wrong one?
Yes, you can migrate your Mastodon account to a different server using the account migration feature. When you migrate, followers on your original server will be notified and automatically updated. You won't lose your social graph or followers, though the migration process does take some time to complete across the federation.
How does Mastodon's recommendation system ensure quality of servers?
Mastodon uses specific criteria to decide which servers are recommended: administrators must be responsive and community-focused, moderation policies must be clear and consistently enforced, the community must be active and welcoming, and uptime must be reliable. This incentivizes server operators to maintain high standards, since recommended servers attract more new users. Poor servers—those with inactive admins, bad moderation, or frequent downtime—won't get recommended even if they're large.
What is the Activity Pub protocol and why does it matter?
Activity Pub is an open standard that Mastodon and other social networks use to communicate with each other. It's what makes the fediverse possible. Because Mastodon uses Activity Pub, it can theoretically interact with other decentralized platforms like Pixelfed (for photos), Peer Tube (for video), and others. This means the fediverse isn't just Mastodon—it's an entire ecosystem of interconnected, independent platforms.
Is Mastodon better than Twitter now?
Mastodon and Twitter serve different philosophies. Mastodon prioritizes user autonomy and decentralization, with no algorithmic feed and no corporate control. Twitter/X offers better discoverability and a larger user base. Whether Mastodon is "better" depends on what you value: if you prioritize user sovereignty and control over content, Mastodon is better. If you want the biggest network and easiest discovery, Twitter/X still has advantages. The new onboarding features make Mastodon more accessible to mainstream users, but the philosophical differences remain.
Why would I use Mastodon if it's more complicated than Twitter?
Mastodon offers several advantages worth the additional complexity: you own your content and account completely, there's no algorithm choosing what you see, moderation is transparent and community-based rather than corporate black boxes, and you can move to a different server if you disagree with current moderation. These aren't small benefits. For users frustrated with corporate social networks, the added complexity is worth it. The new onboarding features are specifically designed to reduce that complexity while preserving these advantages.

Key Takeaways
- Mastodon is testing default server recommendations based on geography and language to reduce onboarding friction for new users
- The platform recently launched Packs, curated account collections similar to Bluesky's Starter Packs, to solve the cold-start feed problem
- A new help center provides plain-language explanations of Mastodon concepts for users unfamiliar with decentralized networks
- Mastodon is moving infrastructure to open-source alternatives like Zulip to align with its decentralization philosophy
- These onboarding improvements could significantly impact Mastodon's adoption rates by making the platform competitive on ease of use with centralized alternatives
Related Articles
- Freedom.gov: Trump's Plan to Help Europeans Bypass Content Bans [2025]
- How Bill Gates Predicted Adaptive AI in 1983 [2025]
- ChatGPT-4o Shutdown: Why Users Are Grieving the Model Switch to GPT-5 [2025]
- WhatsApp Blocked in Russia: How Internet Censorship Works [2025]
- TikTok's New Local Feed: Redefining Community Engagement in the U.S. [2025]
- Facebook's Meta AI Profile Photo Animations: A Deep Dive [2025]
![Mastodon's New Onboarding Features: Making the Fediverse Accessible [2025]](https://tryrunable.com/blog/mastodon-s-new-onboarding-features-making-the-fediverse-acce/image-1-1771519200314.jpg)


