With previous Rexit’s like the API debarcle etc. many users were left looking for an alternative, but with decision fatigue and bad UX etc. most did not find the Fediverse a viable option.
What needs to still improve, how can we be ready this time?
With previous Rexit’s like the API debarcle etc. many users were left looking for an alternative, but with decision fatigue and bad UX etc. most did not find the Fediverse a viable option.
What needs to still improve, how can we be ready this time?
As a new user (I started using PieFed 2 months ago), the UX can surely be improved, but I feel like the main issue is relative to how users are supposed to use the fediverse: I still don’t have a clue on how the fediverse works and how to use it properly.
And I’m motivated in learning to use it.
But for someone who isn’t motivated, it’s a huge “no thanks, goodbye”
I think we should just hide all of that complexity and just set defaults for everything that the user can decide to change if they want. You don’t have to understand how the Fediverse works to be able to use it. Most people don’t understand how email works, they just use it.
BlueSky has 40+ million users, and it’s also technically decentralized like the Fediverse.
aka. you can use the eurosky.social or bluesky.social server etc.
Can BlueSky really be called decentralized when 99% of it is bluesky.social?
It’s not decentralized although it tried really hard to be.
I don’t want to google/remember the exact details but IIRC basically they run a centralized identity server that is impossible to avoid. At best, you can set up an island instance that doesn’t federate with BlueSky proper (like Truth Social vs Mastodon).
No, that’s why I said it’s technically decentralized.
They have 40 million users though, they focused on UX first, and will now hopefully not be dicks and actually become decentralized
Not a chance unfortunately, bluesky doesn’t work without an all-seeing-eye that brings people the content they want. At best there will be some satellites running on atproto, fully decentralized, but the core will still be bluesky and it will still be completely centralized
I’m not sure what can really be done about that; the fediverse is, by its very nature, pretty complicated. It’s at least as complicated as http or email, and those things are widely used but probably not that well understood by the average person.
I think people are accustomed to using things that they barely understand the inner workings of (car, microwave, computer, etc.) during their daily life. So, I guess my question is, to what degree do people need to know “how the fediverse works” in order to use it?
If anything, we probably have to change the way we talk about the fediverse to make it more streamlined for people. For example, instead of suggesting that people “join lemmy”, it would be better to send them directly to a specific instance that we would like to see grow.
Then there’s the friction of actually joining an instance. Some instances won’t let users view content without registering, and some require you to “apply” for registration, pending approval. Both of those things are reasonable and justifiable, but at the same time I think they do create a barrier of entry that we may not want if we are going to try to attract more users.
It reminds me of this:
But yeah making the process of signing up and using the fediverse easier for users will go a long way. As much as I dont like bluesky, one thing they did right over Mastodon is making the sign up process dead easy for end users.
Sure, but Bluesky did that by not really being federated at all, especially during the early rush.
Bluesky is certainly a step or two better than Twitter, but I would imagine it’s still de facto centralized around the main bsky.social server, as that’s what the vast majority of users are probably using.Nowadays it’s getting more federated, but it seems to still be very far behind where ActivityPub is.
So they avoided the challenges of federation by not really being federated in the first place. Mastodon doesn’t have that luxury, since it was fully federated and self-hostable from the start. There was no half step and nobody else to copy.
it’s weird that, because once you’re in it’s basically seamless. it’s just that first step of picking a server based on your interests that trips people up, because aren’t you supposed to pick interests after you get in? more national instances would probably solve that, i think, so you can just go to your local one.
That’s roughly how I chose my instance… I thought I’d choose an instance geographically close to me for latency reasons and such. I didn’t know anything about different Lemmy instances at the time and didn’t (for example) know that my instance actually hosts very few popular communities, so I’d be participating mostly in remote ones. :D
I have never understood the importance of choosing an instance, especially at the beginning. Sign up for any one, try it for a while and if you need to change later, you can do so without problems.
On sites like mastodon where followers are essential it can be a problem, in lemmy where karma is not even accumulated, changing servers does not make you lose more than the 5 minutes it takes you to do it
For new users the local feed is the recommendation algorithm. If you are on a instance that caters to your interests you will discover stuff that interests you there automatically. If you’re not, then you might conclude, that Lemmy has nothing for you and bounce off the platform entirely. This is especially true if you are looking for non-English content.
The paradoxical situation with federation and instances is that those least likely to understand it are among the more likely to profit from it if they did.
Why would you use local as a source of recommendation instead of all? I find using the local tab very limiting, it will never be as complete as all my tastes and hobbies
It’s a bit of a faff to export and import your followed community list
I have changed instances several times and it seems to me to be the simplest mechanism humanly imaginable.
I’d explain it like this. I hope that that works.
An easy analogy
View the fediverse like a few forests, linked by many wild bridges. PieFed might be one forest, Peertube and Mastodon yet other ones. These forests have a lot of different trees.
An instance is like a single tree. And a community a branch. Users are leaves. You can help keep the tree alive, by giving donations as nutrition.
Some parts of the fediverse allow leaves to move and join another tree.
Traditional social media, on the other hand, are comparable to a single, isolated and big tree, far away from other trees. You cannot jump to other trees, and cannot easily go to a forest.
More technical explanation
Social media are built on ‘protocols’. Protocols tell for example social media what they can do and how to ‘talk’ to each other.
The Fediverse is a group of social media that use ActivityPub, Diaspora, or AT Protocol. These three protocols allow something special that ‘traditional’ social media like Facebook and Instagram don’t: they can communicate across each other, without using a centralised server for hosting content.
It’s comparable to email; you can mail to someone not using your mail provider, and vice versa.
On one of these fediverse social media, people self-host or join a self-hosted group. Such a group is called an ‘instance’. Each instance functions independently and can have its own policies.
Instances (and users) can decide with which other instances they allow their own content to be seen. They can also decide what instances their users can see content from. An instance that is connected to another instance is said to be ‘federated’ with the latter. If that is not the case, they are ‘defederated’. Instances are supported through donations.
Within each instances, there are many communities. There’s a community for Linux, a community for cat pictures, a community for nature, and so on. Users can subscribe to many of them, receiving their content.