In Reddit, users can create lists of subs, called “multireddits”. And you can browse the content of all those subs in a multireddit as if it was a single community. You can also share your multireddits with other people.
Reddit itself implemented the idea and never touched it again, but it be amazing in the federation. For example, someone who’s interested in cooking could create the following multireddit multicomm:
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
That increases discoverability of the communities across the Lemmyverse (as people share their multicomms), and also makes it easier to handle redundant communities across instances. Because of that, I feel like the concept would be right at home in Lemmy.
This is possibly in the works I believe. They are currently discussing about the implementation and what additional things it could bring to the table that would make it work even better (for example somehow integrate the idea with Mastodon hashtags).
The link I provided is old, but there is still active discussion and many more contributors, so we could see this happening soon!
That’s great - if more people consider the idea worthwhile, it increases the chances that it gets implemented.
From the discussion in the Github thread: perhaps implement Mastodon timelines as if they were a community, for the sake of multis?
Yup! I’m pretty excited for what’s going to happen in the next 2 months! As for the timelines: Could be, there are two threads discussing this. Here is the second one.
Personally I’m up for anything, I’d just like to stop constantly switching between 5 communities that are all the same but on different instances.
How come those community links don’t work on kbin?
If I recall correctly, it’s because Kbin uses a different software, even if the underlying technology is the same.
kbin also has a discussion about this.
From the discussion in your link: I personally don’t like the idea of making them automatic, I think this is better handled by the users themselves. That also helps with the URL: for example, if you (in Readit.Buzz) created a public multi called “mymulti01” and I (in Lemmy) wanted to access it, I could either check your profile and click on it, or perhaps access it through https://lemmy.ml/[email protected]/m/mymulti01. Then I could copy it if I so desire.
Sometimes simpler “let them do” is the best approach.
