Fedibridge

1 readers
6 users here now

A community to organize and discuss the growth of the fediverse as a whole

Related communities

founded 3 weeks ago
MODERATORS
1
 
 

Everyone is welcome!

2
3
4
5
6
7
8
 
 

I'd like to add to suggest a couple of things regarding Mastodon and user onboarding/retention.

The Server Selection Problem^TM^

The single biggest problem with Mastodon adoption is the fact people see talk about a server and give up. As such, servers need to be removed from the conversation and onboarding process. A server still needs to be selected for a new user, however, which raises the question: How should we select a server for a new user?

The obvious solution is to simply direct users to mastodon.social, which is actually what Mastodon already does to a certain extent. The issue with this is that the Fediverse is meant to be decentralized. As such, it's counterproductive to funnel people towards a single server. This causes maintenance bottlenecks and privacy/data-protection concerns.

Mastodon's landing page.

As such, there needs to be some sort of method that ranks servers based on a few factors in order to select the optimal server for any given user, while keeping the decentralized nature of the Fediverse in mind.

Why any server?

First, it's important to answer the question of why would any given user pick any given server.

Generally speaking, the server isn't a big deal, as in, any server allows users to interact with the whole of the network in its full capacity.

All servers are Mastodon, after all.

However, there are differences. The most significant ones are, I'd say: location, uptime, and language.

A user benefits from being registered to a server that's geographically close to them, as that leads to a better connection. Additionally, servers with high uptime and stability are preferred, as users may have different times they use the server and nobody likes to try and access a server and see that it's down for any number of reasons. Finally, users need to be able to understand the language the server is in (obviously).

I believe these three factors should be at the forefront of the decision-making process for deciding what server to be suggested to any given user on sign-up.

Auto-selector

With that, comes the solution: a server auto-selector. A game I play, DCSS, actually does something similar for online play.

DCSS server selection (I have my location turned off and there are very few servers, as you can see, so listing them is trivial.)

This isn't exactly a novel scientific breakthrough, but I think it's a significant notion for helping the onboarding process for new Mastodon users.

A server auto-selector should filter servers to suggest by following these steps:

  • Detect the user's system language.
  • Detect the user's location.
  • Calculate the server's uptime score.
  • Pseudo-rank user-count.

I believe the first two points are self-explanatory. Being that Mastodon (and the Fediverse, in general) stands firmly against data-harvesting, location data should probably not be mandatorily collected. It should be easy to either ask the user for some vague information or simply allow them to skip this step entirely, even if it might affect the user experience. Additionally, there's the issue that many servers don't make it known where they're hosted. Ideally, this could change to facilitate server selection for the users, but there's always the point that, if a server doesn't say where it's hosted, it gets pulled down by the algorithm, which in turn encourages divulging that kind of information; this might a problem solved by the solution, if you get my meaning.

What I mean by uptime score is simply an evaluation of the server's uptime history. For example, it's not good policy to direct users towards servers that are often unavailable, it might be disadvantageous to direct users to servers with too-frequent downtime for maintenance, and so on. As such, the server auto-selector should calculate a sort of "score" for any server that fits the first two points. I can't say how this should be calculated, exactly, but I'm sure some computer-knowers out there can come up with a less-than-terrible methodology for this.

The last point is something that I think should be taken into account as well, regarding the user-count of the servers. As I mentioned, we can't funnel users towards a single server, but another issue is that we should actually encourage user dispersion over many servers. The outlined method might already do this to a sufficient extent, but I suggest doing some sort of randomization of filtered servers based on user-count. I think it's wrong to simply plug a new user into the least-populated server around, but I do think that over-populated servers, in a relative sense, should be discouraged by the server-selector.

Worst case scenario, a random server that passes the uptime score point can be selected for any new user.

The onboarding experience

Basically, this should be as simple as possible. The more questions need to be answered, the worse.

I think a simple "Join Mastodon" button is the best. Just a big blue button in the middle of the homepage.

Server selection should start as soon as the new user accesses the joinmastodon website, and clicking the button simply redirects the user to the sign-up process for that server.

I believe this approach would increase adoption of Mastodon by streamlining the server selection process, as well as help the continuous decentralization of the Fediverse.

The Feed Problem

Another significant issue with Mastodon is the feed and community/discovery aspects.

Creating a new Mastodon account yields... Nothing. An empty feed!

New account, empty feed.

This is absolutely terrible and ruins user retention. I've had several people tell me that this first-experience emptiness completely turned them off from Mastodon. It's not intuitive, and it needs to be corrected.

A simple solution

Mastodon does have feeds, but they're all tucked away in the Explore and Live Feeds tabs.

I think the single biggest change that Mastodon can make, as far as this goes, is to shift the Explore->Posts feed to the Home tab. Just do it like Twitter or Bluesky, make the discovery feed the first thing a new user encounters.

That, by itself, should make a difference in terms of user retention.


Maybe I'm delusional and severely underestimating how doable this is, but I really believe Mastodon needs to change the way it deals with new users if we want it to actually grow into a strong social media, keyword social (it needs people).

Thoughts?

9
 
 

I like what Isopod did, linking them directly to a instance.

The only way to catch the average joe is to hold their hand and get them to content as quickly as possible. While linking them to the largest instances may not be the healthiest for decentralization, it's going to give newcomers the best experience.

A lot of redditors, I'd even say the majority now-a-days, use the app. While a lot of the Lemmy apps are great. I wish there was one that guided you through the entire signup process.

10
 
 

Let's tell them about Lemmy!

11
12
 
 

I found a super simple way to refer people to Lemmy.

One simple message:

Try out the Reddit alternative called Lemmy https://vger.app/

It also has a mobile app: https://vger.app/settings/install

This way a user can just click, start seeing content and what Lemmy is about, and if they want to comment etc. they will be asked to create an account with lemm.ee selected as a default.

This should fix most of the onboarding UX issues, and eliminate the decision fatigue of trying to figure out which instance is best.

13
 
 

EDIT: @mindbleach@sh.itjust.works shared something that might help to circumvent this shit:

Contained in these parentheses is a zero-width joiner: (​)

Basically, add those to whatever you feel that might be filtered out, then remove the parentheses. The content inside the parentheses is invisible, but it screws with regex rules.

14
 
 

As someone else mentioned here, these other centralized platforms often advertise heavily on subreddits like /r/RedditAlternatives, and they do seem to have some people on there. Does anyone know if they are attracting a lot of people or why people prefer to join other centralized sites before joining e.g. Lemmy? Are they a "threat" to the growth of fediverse platforms like Lemmy, Mbin or just experiments that'll fail sooner or later?

15
16
32
submitted 2 weeks ago* (last edited 2 weeks ago) by Zedstrian@lemmy.dbzer0.com to c/fedibridge@lemmy.dbzer0.com
 
 

Was replying to a now-deleted post in which the poster asked for feedback on the contents and phrasing of a message they had used to promote Lemmy on Reddit. As the crux of my reply was recommending an instance other than lemmy.world to send new users to, I thought I'd rework it as a post of my own.

While @Blaze@feddit.org came up with good criterion for determining which instances should be recommended to newcomers, it seems that neither sopuli.xyz nor discuss.online has native third-party frontend support, something that may increase the likelihood that new users stick around. Although I don't think Mlmym should be recommended—despite being an easy switch for users of the old Reddit interface—due to it lacking recent updates, thus likely to break if not updated for Lemmy 1.0, other third-party frontends such as Alexandrite, Voyager, Tesseract, and Photon may serve new users better than Lemmy's default user interface.

Although country-specific, lemmy.ca is arguably the best option in this regard, supporting all five third-party frontends listed above. It's also one of the longest-running instances, dating to June 2021, and is defederated from lemmygrad, hexbear, and other instances on the Fediseer censure list.

If a non-country specific instance is preferred, I also went through the instance list further to find another general purpose instance with a neutral name, sufficient defederation list, and support for multiple third-party instances. Endlesstalk.org is the next most active instance to meet those criteria, with support for Mlmym, Alexandrite, and Voyager.

17
18
19
20
21
22
23
 
 

cross-posted from: https://lemm.ee/post/55413416

This reddit post likely has tens if not hundreds of thousands of views, look at the top comment.

Lemmy is losing so many potential new users because the UX sucks for the vast majority of people.

What can we do?

24
25
view more: next ›