- cross-posted to:
- fediverse@kbin.social
- mastodon@lemmy.ml
- cross-posted to:
- fediverse@kbin.social
- mastodon@lemmy.ml
TL;DR: The current Mastodon-signup is only removing the confusion of users on first glance, because it either hides the server-choice altogether, or leaves them with a choice that is impossible to make at this point of their Mastodon-journey. Instead, it should introduce them to decentrality on a lower scale, with a handful of handpicked servers to choose from, such that the decision makes sense to them and shows them the merits and fun of the concept instead of scaring them away. Ideal would be to give them a sense of agency. Then, chances are higher that they consider migrating again in the future and eventually internalize it as a permanent option of the digital world.
If you signup to social media it will pester you for your email contacts, location and hobbies/interests.
Building a signup wizard to use that information to select a instance would seemto be the best approach.
The contacts would let you know what instance most of your friends are located (e.g. look up email addresses).
Topic specific instance, can provide a hobby/interests selection section.
Lastly the location would let you choose a country specific general instance.
It would help push decentralisation but instead of providing choice your asking questions the user is used to being asked.
Giving social media platforms access to my contacts? Ew. Never. However for those that want it it might be a good idea, except what if I don’t want whoever has put me in their contacts to find me that way?
That’s actually not a bad idea. I’m not on board with mining contacts, but I think there’s a simple, transparent way to do this that can actually be fun: a personality quiz. Sure, if someone knows what instance to join already, they can override this. But if they don’t, they get like five questions, and then they are matched to an instance.
To be honest, as an instance owner I would not want to even have that data touch my instance - that would be a nightmare waiting to happen whether some instance operator does so with or without malice intent (such as a server compromise).
I don’t think that’s possible without creating a privacy nightmare, at least not with an identifier like the email address.