this post was submitted on 13 Jun 2023
562 points (96.8% liked)
Lemmy.World Announcements
29098 readers
30 users here now
This Community is intended for posts about the Lemmy.world server by the admins.
Follow us for server news ๐
Outages ๐ฅ
https://status.lemmy.world/
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
Support e-mail
Any support requests are best sent to info@lemmy.world e-mail.
Report contact
- DM https://lemmy.world/u/lwreport
- Email report@lemmy.world (PGP Supported)
Donations ๐
If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.
If you can, please use / switch to Ko-Fi, it has the lowest fees for us
Join the team
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
Cross-instance "multireddits", that are also automatic and topic-based. #1113
TL;DR: The suggestion is to implement an automatic multireddit feature in Lemmy that displays all posts from communities with the same name across federated instances. It aims to promote decentralization, avoid echo chambers, and ensure high availability. Community moderators would have the option to opt-in or opt-out their communities from being displayed. There are discussions about potential issues such as community name collisions, duplicates, abuse, and practical implementation. Some propose using a new link format, while others suggest providing users with a list of related communities.
I think what I'd prefer is a more supported version of Reddit crossposting... I'm brand new so stop me if Lemmy already does something like this. For example, if someone has a vegetarian recipe community, a more general vegetarian community might automate a feature to crosspost their content, with clear linkage to the source... But a new discussion thread as the default in the crossposting community.
This allows the different related communities to choose their own moderation and regulation, but can also allow communities to be content aggregators.
I can definitely see name-collisions being an issue, where communities on different instances have the same community "ID", but aren't actually about the same thing. I'm still overall in favor of the basic idea though.