Otherwise, if we have a lot of medium sized instances but the most popular communities are hosted on just a few huge instances, doesn’t that defeat the purpose of distributing load across many instances?
If that’s the case, how do we solve the cumbersome user experience of having to subscribe to the same community over and over again across a ton of medium instances?
I mostly agree, but look at the Technology community. [email protected], [email protected], [email protected], [email protected]. They are all about the same thing and subscribing them all gets a lot of dupes.
Then, don’t? Just subscribe to one of them.
It’s not all duplicates.
Obviously. But that’s not an issue, just find one community you like, ignore the others.
Just read all the other comments in this post asking for a technical way to merge similar communities. I’m just asking for the same thing.
While the name may be the same, different articles get posted to each… just that often the same article gets posted to all.
Furthermore, discussions within each /c/ involve a different set of people.
Yes, of course. But you don’t need to be part of every discussion to a subject. Just subscribe to one tech community you like (or as many as you want) and ignore the others.