Lemmy needs a middle logical layer to really take off. If a local server moderats it as such, the default view for say /c/technology shouldn’t be slit across a dozen instances. Instead it should be merged into one view.
Without it you have a bunch of largely stagnant communities.
It might be a good feature/option of a frontend to automatically aggregate same-name communities across federated servers. Bogus actors would either be downvoted or defederated off the feed.
Lemmy pretty much just needs tags. Like you can mark your different “technology” communities with the tag “technology” and a user can subscribe to this tag to view all posts from whatever communities have this tag (and they don’t have to call themselves strictly just “technology”)
Something like that I would imagine so no direct interaction between communities required.
Lemmy needs a middle logical layer to really take off. If a local server moderats it as such, the default view for say /c/technology shouldn’t be slit across a dozen instances. Instead it should be merged into one view.
Without it you have a bunch of largely stagnant communities.
deleted by creator
It might be a good feature/option of a frontend to automatically aggregate same-name communities across federated servers. Bogus actors would either be downvoted or defederated off the feed.
Lemmy pretty much just needs tags. Like you can mark your different “technology” communities with the tag “technology” and a user can subscribe to this tag to view all posts from whatever communities have this tag (and they don’t have to call themselves strictly just “technology”)
Something like that I would imagine so no direct interaction between communities required.
It’s this plus uptime. Both come down to usability. Nobody wants to use a product that is confusing or unreliable.
Only Lemmy.world really has issues with uptime
Yeah, Lemmy excels at both those things.