When you look at https://beehaw.org/communities, you can see that there are only a few communities, but they are diverse enough to cover most of the topics you would have to discuss on the Internet.
I sometimes think that could be a model we could try to replicate across several instances:
- technology: [email protected]
- gaming: [email protected]
- chat: [email protected]
- etc.
It would allow to aggregate people around a few core communities and avoid dispersion and fragmentation. Of course, it would need some agreements in the community, and some people would probably want to keep their community as “the main one” opposed to the other, but that could still be valuable.
What do you think?
You must log in or register to comment.
Hmm, not sure I fully understand. Are you suggesting that each instance should limit the number of communities to a few general ones, or that the Lemmy network as a whole should limit the number of duplicate general communities?
That’s more or less the idea. Fragmentation doesn’t really benefit us except when the topic is that popular that conversations can happen in parallel (technology or news for instance)
Isn’t Beehaw approach the opposite of what Fediverse stands for? Many fragmented communities, but still interconnected. Lemmy specifically needs a way for individual users to group all these similar communities (and there are many proposals for that) as opposed to more centralization.
I shared my thoughts on Beehaw approach in more detail here: https://lemmy.zip/comment/2570691
I wouldn’t say they are the opposite, they are still federated with a lots of instance, just not LW and SJW.
About the grouping of communities, that would be an improvement, but at the same time, wouldn’t that be strange for new joiners to have to group a few communities on the same topic while they only want to follow it?
I know it’s a balance between centralization and decentralization, but sometimes I feel we went a step too far in the latter.
For instance, if [email protected] became the one reference community on data breaches, that would be nice, we probably don’t need a community on this topic on 4 other instances
Success of grouping entirely depends on the technical implementation. And new user experience is something that Fediverse sucks at as a whole. On Lemmy, introducing new users to groups could be as simple as suggesting pre-created groups on identically named communities, they can follow with a single click. Which would cover 95% of people coming from Reddit. And for the rest 5% that want more tailored experience could create custom groups.
If [email protected] became the reference community, then it’s subject to all the federation/defederation of
lemmy.zip, rules oflemmy.zipand laws oflemmy.ziphost server and applying it to the whole Fediverse.Agree with your first paragraph.
If [email protected] became the reference community, then it’s subject to all the federation/defederation of lemmy.zip, rules of lemmy.zip and laws of lemmy.zip host server and applying it to the whole Fediverse.
Indeed. I found Lemmy.zip governance to be very transparent and responsible, so I wouldn’t mind.
But not every instance has the same governance as
lemmy.zip. Would you also be fine with some community becoming de facto reference onbeehaworhexbear.netorlemmy.world? Each of them have the rules that contradict each other, which prevents certain communities from being able to be created on those instances. If we make any community of theirs reference one, their rules, federation/defederation and governing laws become effectively global instead of only applying to that instance.But not every instance has the same governance as lemmy.zip.
Agreed
Would you also be fine with some community becoming de facto reference on beehaw.org or hexbear.net or lemmy.world?
No, and that’s why I listed SJW and lemm.ee in my OP (to be honest, I should probably change LW to lemmy.zip)
Beehaw is too deferated indeed.
Hexbear comes with their own specific stance.
LW, I feel like they are okay for now. The major issue I see with them is the federation with Threads, but that can always change (and probably will if we get millions of trolls at once)
I guess my idea would be to have a subset of instances that are compatible, rules and federation wise (lemmy.zip, lemm.ee, SJW, Reddthat.com), and spread communities among them, with one reference community on one single instance.
LW centralization is an issue on its own, but that’s the subject of another thread already.
My issue generally boils down to it being optional and something instance admins and mods would have to opt in and maintain, because if it were a technical solution, it wouldn’t be able to exclude instances someone has an issue with. It would also negatively impact the content variety due to different instance rules AND community approach.
E.g. there are several gaming related communities, but they all differ. Some allow bots, others doesn’t. Some allow memes, others’ doesn’t. Some limit posts, others doesn’t. And all of them are on different instances that have different rules and moderators.
I think it also depends how popular the topic is.
Gaming, as you said, exists on several platforms, with different mods and teams because it’s a quite popular topic.
On the other hand, I also regularly browse [email protected] and [email protected], and they seem pretty similar to me (be it rules or content wise), they are also lacking some activity, so they would probably benefit from being merged, and having one as the reference.
