1449
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Aug 2023
1449 points (99.0% liked)
Announcements
9 readers
1 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
Have you considered a feature like “sibling community”?
What I mean is, for example, car community on server 1 marks itself as a sibling community to a car community on server 2. Similarly server 2 marks itself as a sibling community to server 1, ie it is two-way.
When communities have been linked bi-directionally, any post and comment are shared between the two sibling communities.
This would allow bigger communities to form out of smaller communities, thereby preventing discussions from being fragmented and showing the true size of Lemmy, across servers.
We have an open issue for collections of communities, but not for any complicated trees of communities. Creating and linking community trees sounds really complicated, and I don't know how all that would work.
I don't know how the code is currently working, but I like this feature idea and would suggest to start very simple and proceed from there.
For example you could: a) Make a list of communities that are siblings with their id and instance b) add a toggle to view sister community posts yes /no c) query all communities, list the last x posts from each with time constraints, e.g. not older than 1 day or hour depending on the community post frequency d) list them sorted by time of x , depending on what was chosen
The biggest issue I see with this simple approach, besides others, is that different communities are different in terms of activity / post frequency. So ideally the better, but more effort, way would be to let each community instance communicate their posts themselves via a query with activity metric parameters. Basically the amount of returned posts would depend on common parameters set by the most active instance.
It's not yet thought out, but just getting an mvp started and test the waters would probably be better than having it perfect right away while working on it for months
pretty good idea, i figure moderators would be shared between communities?
I think the ama is over? But I like this idea! Not sure of the implementation headaches, but it seems a lot more feasible than the other proposals I've heard, most of which involve making community names globally unique