I think you've correctly identified a problem, but misidentified the solution.
It's true that there are many redundant communities of which everyone would be better served if there were an easy way to group them together. The solution, however, is not to reduce the number of instances, but rather to provide more tools for instances to group communities together. You want communities to be spread across many instances because this maximizes user control - it's kind of the entire point? But of course, the lack of grouping makes it very difficult to try to centralize discussion, which is important for the community to grow. This service is still a work in progress, so these kinds of things - I hope - will come in time, as both the technology and culture develops.
tl;dr: centralized control bad, centralized discussion good, the current system does a bad job of reconciling these two positions
Seems like what a lot of people want is a hybrid of Usenet and Reddit, but what we have is more like a bunch of reddits that are willing to talk to each other. Certainly better for governance and redundancy and as a kind of organic load balancing in a cash-poor ecosystem, but the "killer app" would be (optional?) persistence of communities outside of instances.
The solution, however, is not to reduce the number of instances, but rather to provide more tools for instances to group communities together.
kbin collections are grouping together communities, but unfortunately, collections themselves do not federate
@gicagaf805
I agree and basically, it's not a bug, it's a feature
There is no monopoly if you have a dozen big instances. But if you have 1000 instances? What is the point. Can't start a community there without it going poof the next week.
That is always a risk for small instances.
It is the same for small businesses or libraries/museums funded by donations.
Imo just because there is a risk does not mean they shouldn't do it.
The core issue here is instances disappearing, and That goes into the discussion of the structure of the fediverse right now vs. the fediverse in the future
A dozen big instances feel better now, and I personally wouldn't make a community on a smaller instance unless I know it is likely to stay up. If it was run by an existing organization for example.
Long term though, I trust existing organizations to set up stable instances that won't be shut down easily. If a government, school, game company etc. makes an instance it's not likely to go down. Having lots of instances will look more normal then.
Ultimately we don't need to do anything differently, I recommend new people join a big instance and then make a new account once they know what instance they like.
note to everyone: please don't downvote good faith questions
OP asked a pretty reasonable open ended question. There are other people who may be thinking the same, and reading the discussions here might change their minds. Save downvoting for rule breaking / content that's bad for the community
Thank you for this
Would be nice to be able to backup your magazine/community, so if for example random.lemmy goes down, you can still migrate your /mini4wd elsewhere. Don't know how it could be implemented though, I'm still in the "i get it but not really" phase with the Fediverse.