this post was submitted on 03 Aug 2023
1867 points (97.9% liked)
Fediverse
28499 readers
305 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think community consolidation/aggregation is something that might want to be looked at. It's possible to have a gardening community on multiple servers with different content. This will confuse people. So having a way to merge posts from two communities into a bigger community per server may be a good idea. So if you set up gardening communities on two servers you can choose to have posts show for each of them in your community. And making this a server or community setting still gives the ability to either have this or not have this if the communities are truly supposed to be separate. This would also give some kind of redundancy where the original community server can go offline but multiple different servers can still exchange messages that eventually make it back to the main community. Truly decentralized.
I have to disagree. Consolidation seems almost never to improved anything. Take Reddit, for example. I once found a sub called HikingAndCamping. Since I'm a hiker, I looked it over. The top mod only allowed discussions of hiking and camping on Mt Everest (or some equally nonsensical narrow topic). Since I actually wanted to discuss hiking and camping generally, I tried to create CampingAndHiking as a more accessible community. But that same top mod had already claimed that name as well under an alt. Reddit refused to do anything, but when they notified him that I had requested the dead sub (no posts and the alt hadn't logged in for years), he jumped in and created a single "Go away" post. Then he sent me a private message to the effect of "I'm squatting to keep traffic flowing to my other sub. You want to talk about hiking and camping in general? Sucks to be you."
Here, I'd just go to another instance and create the c/ that we wanted and move along. That's part of the beauty of federation. Users can then join the one(s) that appeal to them and everyone gets to have their community.
The way I was thinking you could still go to the original community and skip the aggregated one. So you could have c/gardening and c/flowers, but also c/backyard which could combine the two. You could still go to either one, but for easier discoverability you could create aggregators or include an aggregator in your community, and do this cross server. So if you have two very popular and overlapping communities you could combine them easier. Could also be a client feature I suppose. But right now you'd have to manually hunt for the possibly dispersed communities yourself. Alternatively I guess there is an argument for smaller communities being better which I do agree with. It was just a not very thought through idea :) Or you could have community redirects. So c/technology on lemmy.world could decide to seamlessly redirect to c/technology on Lemmy.ml if wanted. Edit: although the more I think about this the more it sounds like more trouble than it's worth.
Now I get the idea. It's not a bad one, but it may very well be a lot of trouble to implement. Maybe the cross-instance community lists could help. It seems like, most of the time, related communities pop up fairly quickly or show up in the initial search.