A new onboarding experience on Mastodon
blog.joinmastodon.org
Today we’re making signing up on Mastodon easier than ever before. We understand that deciding which Mastodon service provider to kick off your experience with can be confusing. We know this is a completely new concept for many people, since traditionally the platform and the service provider are one and the same. This choice is what makes Mastodon different from existing social networks, but it also presents a unique onboarding challenge.

I’ve seen lots of discussion on reddit of users trying to get others to join Lemmy and the prevailing reply is that it is too difficult to navigate and comprehend. Having to answer multiple questions and wait for manual verification is combersome and is limiting growth at a time when nothing should be standing in Lemmy’s way. Combine this with server/instance selection analysis paralysis, and you get my point.

The linked mastodon blog post sums up my thoughts, but the TLDR is essentially this:

Don’t let the perfect be the enemy of the good. Don’t let dreams of decentralization interfere with the greater goal of achieving the network effect.

We should all be telling people to go to lemmy.ml and sign up. The devs should be too, and they should rethink/remove the questions and waiting period. Hell, just put a captcha. Discussions about servers and analogies to email as an example of federated service we all already use is a waste of breath. We shouldn’t have barriers to entry.

Thoughts?

EDIT: I’ve just found kbin.social and find it has superior signup options. It’s just: make an account (email/password), or sign up with Google or Apple. No server talk. Upside is the layout is nice and it acts as a Lemmy instance (threads) as well as a mastodon instance (microblogging). Only downside currently is that their android/iOS app is in development and isn’t ready yet, so desktop only.

https://github.com/ernestwisniewski/kbin

https://kbin.social/

I think this might be the better recommendation for newbies at the moment.

  • alienBlues@lemmy.mlEnglish
    0·
    1 year ago

    I’m a new user, so my opinion counts as such. My first concern upon signing up was understanding which communities I was allowed to see from which instance. Maybe a page where people can search by communities first and then show them where they are hosted/federated could solve this issue. Also, improving federations between servers could ease the signup process too. If any server allows communities from most other servers to be viewed, choosing what instance to join will be more a matter of personal beliefs and tastes than else.

    I’m afraid that setting a default instance could cause it to experience explosive growth and monopolization of the communities. As someone pointed out in a comment in another post, while users on Lemmy are growing, donations are not, so the bill for a single instance with all the people on it will probably be huge. Also, if all the largest communities are going to be on a single instance, how difficult will be to create new original ones to bring some people to the small servers?

    Captchas are bad for privacy. They allow the provider to track users between websites, and they are also bad for people because they are generally hard to solve for people with impairments. Also, automated solutions to bypass captchas exist on the market.

    Also, I believe a network with high-quality content is better than a bigger generalist one. A little barrier of entry and manual screening of people may serve well for this purpose, so I’m favorable to keeping it.

    • vxnxnt@feddit.deEnglish
      0·
      1 year ago

      Well said. This is pretty much what it comes down to imo. A decentralized platform should avoid all centralization at any cost. Monopolization just hurts other instances and communities while severely limiting diversity.