this was suggested quite a few times already, both here and in Github issues.
question is, how do we get interested people to start implementing it
Developers said in the latest news post that they are aware of community wanting this, but they are way too busy working on some core Lemmy issues, so someone else will have to step up in order to get this to be implemented sooner

the easiest solution to this is to take reddit’s multireddit feature

Yeah, I think that’s the best way forward.

I commented on this else where; perhaps this can be done via two folds:

1. !technology@ (note the distinct lack of instance domain), which is just a UI aggregation of all the !technology communities followed by the user, and:

2. #list$user@instance.domain (not fixated on the hash and dollar sign, just using different symbols than what we currently have to make picking out what kind of list we’re looking at easier) as a back-end driven, user managed multi where they could put !apple@instance.domain, !banana@instance.domain, !orange@instance.domain together into one aggregated list appearing on #fruits$user@instance.domain .

The first type being front-end only shouldn’t require a lot of configuration or changes; the second type being back-end driven could offer a lot of flexibility (i.e.: privacy settings, if other users could see it/pull contents from it, etc.).

Is it actually a problem? One of them will naturally “win” - they’ll get the first chunk of people, then people will join that one because the people are there.

If we do get two vibrant competing communities it will be because they provide something different to each other in some way and then we probably don’t want to lump them together.

I think multi-lemmys would be useful but I don’t think we need them as a solution to the competing communities situation.