@julian@fietkau.social
"I would expect them to move after learning what servers mean and which ones could fit them. How long this takes will differ per person."
It has been two years since this was suggested and it just has not happened, the percentage on mastodon.social has gone from 15ish to 30ish.
The process of moving could be simplified but it will ALWAYS be more complex than the process of remembering whether you signed up on mastodon.social or mas.to. It is not realistic to rely on this path.
@FediTips@social.growyourown.services Moving accounts will always be a nontrivial process, but after some weeks or months on fedi, people will be more equipped to pick a server they can identify with than they are to remember a random server during initial signup.
And I'm not saying to cross our fingers and hope they'll move on their own. We could do in-app reminders for m.s users, server recommendations like yours, maybe even gradual throttling of overly long-lived m.s accounts. There is room for more ideas.
@julian@fietkau.social
Telling people to sign up on mastodon.social and then punishing them for signing up on mastodon.social is (with all due respect) not a good idea. It will make people feel gaslighted by Mastodon and put them off the network completely.
Encouraging people to choose a different server to begin with and helping them to do this is innately the most effective way to spread growth out. We know this because it worked when they did this.
@FediTips@social.growyourown.services It isn't a punishment if m.s can be conceptualized as a transitionary tutorial server. Kind of a “Great Plateau” of Mastodon, if you've played Zelda BOTW.
I think there can be a design where it feels natural to have an area that people are expected to leave once they get their training wheels off, especially if the migration process is improved to include posts, update conversation threads, contain fewer UI steps, etc.
@FediTips@social.growyourown.services @julian@fietkau.social any fedi app have any kind of wizard for picking an instance?
sorry for crashing the middle of your debate but that's how I'd handle it: with the client-side database. and then immediately export settings, maybe with a file including the name of the instance.
@travisfw@fosstodon.org
I run a website at https://fedi.garden to help people discover good well-run servers. All of them are human-curated and comply with seven points listed at https://fedi.garden/about-this-site/
There are also wizard sites but I wouldn't recommend them as AFAIK none of them curate the servers they list, so they may be directing people to unreliable or unsafe servers.
@travisfw@fosstodon.org
I run a website at https://fedi.garden to help people discover good well-run servers. All of them are human-curated and comply with seven points listed at https://fedi.garden/about-this-site/
There are also wizard sites but I wouldn't recommend them as AFAIK none of them curate the servers they list, so they may be directing people to unreliable or unsafe servers.
@FediTips@social.growyourown.services you do, I know, and you are awesome, and I haven't checked it in a while but thank you.
are any client apps funneling people to your site?
@FediTips@social.growyourown.services you do, I know, and you are awesome, and I haven't checked it in a while but thank you.
are any client apps funneling people to your site?
Fedi.Tips
Julian Fietkau