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.

  • zksmk@lemmy.mlEnglish
    2·
    1 year ago

    I think you’re getting hung up on the word “federations” (noun) instead of the adjective “federated”.

    Who decides who gets to email who? The email provider admins. Should everyone be in a single email network/bubble since otherwise there is no communication? Mostly, yes. Do I need a separate account per email bubble? Per email bubble? Yes. But how many email bubbles are there? One? Whats the practical limit on number of providers per the email world? None, mostly?

    Gmail does ban a lot of small email providers if they don’t seem “legit” enough. And that is where you’re onto something with the noun federations.

    If a bunch of instances really disliked a different bunch of instances they can indeed severe each other from each other. The admins would do that. They put the other instances on a block list. Most Mastodon instances block Trump’s Lie ehm Truth Social etc. But otherwise you can talk from gmail to hotmail to mcselfhost, with one account.

    Basically federation works based on a block-list, not a allow-list, unless the admins of the instance set it that way, just like email providers.