The continued growth of mastodon.social is putting the #Fediverse in danger (here's why: https://fedi.tips/its-a-really-bad-idea-to-join-a-big-server/).

The quickest, easiest and most effective way to solve this would be if the official apps & website stopped promoting mastodon.social, and instead promoted a rotating selection from a pool of reliable servers with solid track records.

If you're comfortable using Github, please give thumbs up to all these:
- https://github.com/mastodon/mastodon-android/issues/568
- https://github.com/mastodon/mastodon-ios/issues/1023
- https://github.com/mastodon/joinmastodon/issues/1052

Mastodon.social is not a good way to join Mastodon. If you’re already on it, you might want to move your account to a different Mastodon server. | Fedi.Tips – An Unofficial Guide to Mastodon and the Fediverse

An unofficial guide to using Mastodon and the Fediverse

@FediTips I feel like when people ask for randomly assigned servers, there's a strange forgetfulness about which specific problem the default server was meant to solve.

Among people who signed up in 2022, the biggest reason (by far!) why people involuntarily left – that is, wanted to keep using Mastodon but failed to – was that they changed phones or browsers or just wanted to sign in on another device, and couldn't because they didn't know what server they were on.

@FediTips We can't be telling people “don't worry too much about all that server stuff for now” and also “oh you don't know if your account was on mstdn.social or mas.to, then you're just outta luck sorry”.

We also know that asking fedi newcomers to pick their own server does not work. Your suggestion addresses this point.

My conclusion is that having a default server for all newbies (not invited by a friend) is the best practical approach. Somewhere people can get their bearings.

@julian @FediTips much of this could be solved if the “default server” for sign ups rotated….

@UlrikeHahn @julian

Exactly. The solution is obvious, there are many servers with similarly reliable track records, promote one of those.

This is something I continue to think about a lot. I thought changing the default was a bad decision at the time and haven't changed my mind! It's not just the centralization aspects of it; it's also that (based on retention rates) most people don't have a good experience on .social -- so they wind up leaving fedi.

Rotating the default doesn't seem to me like it would address the :"good experience" aspect of the problem. For most people who are looking for a Twitter-like experience, .social's as good an approximation as anywhere else in fedi -- not great, but other instances aren't any better. And for people who are looking for a local community that aligns with their interests or geography, they're not going to find it on other largeish open-registration instances (and it doesn't make sense to have anything but a largesish open-registration instance as the default).

@julian
@FediTips @UlrikeHahn

Approaches that might work better involve integrating a good instance picker into the signup process, or an onboarding flow that treats the initial instance as a "starter instance", a base for exploring that makes it easy to move to another instance. Realistically though it's not clearly how likely it is that Mastodon gGmbH will prioritize the work that's needed to support either of these -- which isn't an argument against pushing for them, just that we should be looking for other alternatives as well.

In general it seems to me that might be better to focus our efforts in terms of making it easier to join communities in fedi as a whole, not just Mastodon. For many people something other than a Mastodon-based instance may well be a better choice. Of course that still leaves the problem of people who search for "mastodon", or have read an article about Mastodon and followed the links to either the Mastodon app or joinmastodon ... but I don't know how to address those without Mastodon gGmbH's cooperation,

@julian @FediTips @UlrikeHahn

And actually I'd go farther and say it might be better to focus on community-led alternatives to commercial social networks in general -- not just fedi. For people looking for a US-focused, Black-centric microblogging experience, Blacksky might well be the best option today (and as Northsky becomes more real, that's likely to be a good option for a North American-focused 2SLGBTQIA+-centric microblogging experience). For people looking for a Palestinian-friendly photo/video-sharing app, Upscrolled might be a good option even though it's not decentralized.

@julian @FediTips @UlrikeHahn

@thenexusofprivacy

I feel that its worth pointing out in these conversations that nobody starts new servers anymore. Its hard (to measure kinda impossible now since fedidb removed the 'first seen' statistic, and server age does not show up in nodeinfo), but virtually no new servers have been started since 2024 that have gotten over 1k mau, I think it was like 4 total (this spring when the stat was still available)

@julian @FediTips @UlrikeHahn

imo a core problem is that perceptually, an app is usually tied software (the mastodon app) instead of network (the fediverse app) or server (the indiewebsocial app)

@thenexusofprivacy @julian @FediTips @UlrikeHahn

Mo-Me is leaning into this dynamic. For #MediaLiberationDay, it was very useful to be able to point people to Mo-Me to get started (as oppose to "start by picking an instance" or "start on .social"). And I wouldn't call it a "paddling pool" since it's got pretty rich functionality and is fully federated, but it's definitely an example of what I think of as a "starter instance".

One of the challenges with the app focus though is it's likely to reinforce the default tendency on flagship instances. If I want to use Piefed-the-app, it's natural to sign up on piefed.social; even though they're putting a lot of work into helping people choose an instance when they sign up (and kudos to them for doing it!), why not just sign up on piefed.social? It's hard to answer that without talking about instances and why they matter!

@laurenshof @julian @FediTips @UlrikeHahn

@thenexusofprivacy
Yeah MoMe is a great example

I get your point on how app focus also increases flagship importance. But I think that also partially points to that we keep trying to see the platform software as neutral with all expressions of community coming from servers, and I’m increasingly starting to feel that’s a dead end

@julian @FediTips @UlrikeHahn

@laurenshof @thenexusofprivacy @julian @FediTips Laurens, can you say more about this?

@UlrikeHahn @laurenshof @thenexusofprivacy @julian

Whatever you suggest, please say something that doesn't involve centralisation.

This isn't meant to be a thread about how to do onboarding, it's a thread about how to stop centralisation.

In this particular case it's a badly-conceived onboarding mechanism that is causing the problem, but the problem itself is the centralisation.

All discussion is pointless if the Fedi centralises, because it would no longer have a reason to exist.

@UlrikeHahn
Basically the premise of bonfire, taken one step further. Bonfire lets the server software be opinionated and customised to the needs of the community. Think that’s good, but a truly individual server for a specific community needs to have a customised app as well that’s specific for that community I feel

Sidesteps the issue of signups for mastodon apps needing to have default servers, which is how this whole thread started
@thenexusofprivacy @julian @FediTips