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.

  • @[email protected]English
    7•11 months ago

    I’d like to see singular communities rather than community-per-server in the federation. If /c/NHL exists, it simply exists. Right now, each server has their own communities that other servers can also join in but you always know they’re separated.

    • ඞmirEnglish
      14•11 months ago

      Yes, this. We need a way to link communities on different servers together. I want a unified feed with tech discussion from beehaw and from lemmy.ml, but right now these are two separate feeds. I also want to sub to “tech on every federated instance” but I can’t tell lemmy.ml that “hey, I want all tech news you know about”. I have to manually scrape communities and sub to all of them. And that doesn’t even help if new ones are created every day.

      • @[email protected]English
        4•11 months ago

        Right now one of the problems is that, at least on lemmy.ml and beehaw.org, the default view for the front page as well as the community list is Local. You have to switch to All to see everything. The main Lemmy page touts the federation but it’s less prominent once you’re actually looking at content.

        I’d like to treat it like usenet. rec.roller-coasters is the same across usenet servers. Right now, each server might have its own. I can access all of them all, sure, but it feels fractured and splintered with, potentially, most users simply accessing their servers local community.