This will take place ~24 hours from now. Feel free to post and upvote questions beforehand in this post, as it will turn into the AMA tomorrow.
This is a chance for any users, admins, or developers to ask anything they’d like to myself, @nutomic@lemmy.ml , @SleeplessOne1917@lemmy.ml , or @phiresky@lemmy.ml about Lemmy, its future, and wider issues about the social media landscape today.
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 @nutomic@lemmy.ml 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.
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.
boost.lemy.lol?
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
I know lemmings.world has a bot that subscribes to the most popular communities to make sure those are federated
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.