this post was submitted on 25 Jan 2024
12 points (100.0% liked)
Announcements
23277 readers
14 users here now
Official announcements from the Lemmy project. Subscribe to this community or add it to your RSS reader in order to be notified about new releases and important updates.
You can also find major news on join-lemmy.org
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Its definitely a concern. IMO the lemmyverse is far too centralized at the moment. The big questions are:
(1) I'm honestly unsure, and I'd def appreciate if anyone has done a study of it. We've seen a big growth in single person / smaller topic-focused instances, which is a great thing, but if their communities aren't growing, we need to figure out how to reverse that trend. I'd have no problem with the current large instances, including this one, as long as the long-term-trend is away from them.
(2) Is mostly word-of-mouth, join-lemmy.org, and apps / web-ui's which show an instance by default.
We've made the sort for the join-lemmy.org instances page be by random active users, and tried to emphasize on that page that it doesn't matter which instance you join, since most federate, and can subscribe / connect to any community. I hope that helps, and we need to replicate that wherever we can.
Apps and webUI's mostly just show lemmy.world rn, where they should show random instances. I'm guilty of this in Jerboa as well (showing lemmy.ml by default), and I've just opened up an issue that it should be showing a random server for anonymous users.
But I think we need to do more, and I'd def appreciate yours and anyone else's ideas on how we can combat centralization. We need to get ahead of this problem before it gets worse.
I am admin of the biggest Brazilian instance, but I am welcoming more local instances and talking to the admins we should spread the load. But what I notice is the users are concerned they will miss out if they are not in an instance that already have everything.
Could we have an easier way to auto-federate every new communities from a given instance? Even an "auto-federate everything possible" option. as @[email protected] said lemmy DB isn't too big, most instance owners could have it on their servers. And making it opt-in won't hurt the small instances.
Maybe not auto-federate / auto-subscribe, but we do have an issue to federate a lightweight list of communities among servers, that could help with this.
Its true that the disk space required isn't too big a deal, but it would unecessarily increase the CPU and network requests by auto-federating the entire lemmyverse, rather than using explicit subscribes.
It would be relatively easy to write a script/bot which fetches the list of communities from a given instance, and then subscribes to all of them from another instance. In fact I heard something like this already exists, but dont know the name.
I think it's worth bringing a solution in house. A recommended migration route. If you want people to feel confident to pick any instance, you have to give them the confidence to move easily and not fear picking a small instance that might die when their owner gets bored. A simple setting option to migrate from, then you select the account and either (through communities accessible, or through automated request, pull that data and subscribe to communities. Maybe blocks etc also.
Lemmy Community Feeder? https://github.com/Fmstrat/lcs
boost.lemy.lol?
Maybe hide the big instances behind a few clicks? Like you could sort/filter for them, but you'd have to navigate a bit? The average user isn't going to bother. Like have a default sort that hides the big ones, and a default filter that filters out the top five or whatever.