When the API changes came in on Reddit it appeared to cause quite a few people to shift to Lemmy, but not that many. I’ve said this before in other posts but the onboarding experience for Lemmy is awful for your average joe. From what I’ve read it was the same situation for Mastodon and that is why Bluesky took off instead.
There needs to be a clear concise point of entry for new users to the Fediverse that empowers users to quickly customise what they want to see. Most people don’t care about how the Fediverse works and its benefits, they just want to consume content.
If I were technically capable and had the drive to do so I’d create a single onboarding site that would ask the user a few preference defining questions, chuck them on an instance that is relevant and apply some filters so they don’t get spammed with anime posts if that isn’t their thing. Oh and maybe show a couple of mobile apps.
I largely agree - the fediverse needs less friction if it wants widespread adoption. That’s part of the reason why I wound up on .world. It was easy. I suspect I’m not alone here.
The other bit challenge is that each instance can have identically named communities, which drives fragmentation and makes each community seem less active. I dabble in photography, so I’ll use some examples from that.
Reddit has this problem too, but there can only be one /r/photography. There are derivative communities like /r/streetphotography and /r/askphotography, but the original sub is unlikely to move/change.
By design the fediverse can have many /c/photography communities. In the case of photography there are three or four “big” ones and a bunch of smaller ones. There are also all the derivative communities, some of which are doing better than the ‘root’ community. One example of this is !superbowl@lemmy.world.
I’m not sure what a good solution is, especially when you start talking about “the same” community on multi-inatance. One of the design goals of the fediverse was to enable that should some instance go off the rails.
When the API changes came in on Reddit it appeared to cause quite a few people to shift to Lemmy, but not that many. I’ve said this before in other posts but the onboarding experience for Lemmy is awful for your average joe. From what I’ve read it was the same situation for Mastodon and that is why Bluesky took off instead.
There needs to be a clear concise point of entry for new users to the Fediverse that empowers users to quickly customise what they want to see. Most people don’t care about how the Fediverse works and its benefits, they just want to consume content.
If I were technically capable and had the drive to do so I’d create a single onboarding site that would ask the user a few preference defining questions, chuck them on an instance that is relevant and apply some filters so they don’t get spammed with anime posts if that isn’t their thing. Oh and maybe show a couple of mobile apps.
I largely agree - the fediverse needs less friction if it wants widespread adoption. That’s part of the reason why I wound up on .world. It was easy. I suspect I’m not alone here.
The other bit challenge is that each instance can have identically named communities, which drives fragmentation and makes each community seem less active. I dabble in photography, so I’ll use some examples from that.
Reddit has this problem too, but there can only be one /r/photography. There are derivative communities like /r/streetphotography and /r/askphotography, but the original sub is unlikely to move/change.
By design the fediverse can have many /c/photography communities. In the case of photography there are three or four “big” ones and a bunch of smaller ones. There are also all the derivative communities, some of which are doing better than the ‘root’ community. One example of this is !superbowl@lemmy.world.
I’m not sure what a good solution is, especially when you start talking about “the same” community on multi-inatance. One of the design goals of the fediverse was to enable that should some instance go off the rails.