Please don’t take this the wrong way, just a friendly tip:
with kbin finally with Lemmy again
If you are talking about instances, use the entire name. Try to avoid mixing your references between software and instances, otherwise it will be confusing and can cause misunderstandings. _
Kbin has always been “with” Lemmy.
-
Kbin: https://fedia.io
-
Kbin: https://readit.buzz
-
Kbin: https://karab.in (oldest Kbin)
-
Kbin: https://u.fail
-
Kbin: https://fediverse.boo
-
Kbin: https://kilioa.org (SOLO instance)
-
Kbin: https://forum.fail
-
Lemmy: https://sopuli.xyz
-
Lemmy: https://lemmy.blahaj.zone
-
Lemmy: https://lemmy.world
-
Lemmy: https://lemmy.ml
-
Lemmy: https://beehaw.org
The one which was being hammered by registrations and bots was/is https://kbin.social and it is just one of many.
_
Hopefully that doesn’t happen.
For some topics, there are already existing, very active, communities before the subreddits with the same topic migrated over. Who should merge with whom? The existing large communities with subreddit migrators? Or, the subreddit migrators merging with th existing large communities … and conforming to the rules and culture in those existing large communities?
As mentioned, there are different cultures and rules that develops per community. There is no such thing as one-size-fits-all.
Even if communities “consolidate over time”, it will still split up no matter what. That’s how it has always been sincee the beginning of online communities.
IF communities indeed consolidate over time, if that server/instance goes down, the entire consolidated communities will be gone overnight, and all the content they collected together. We’ve already seen this happen just this year, forget about the previous years.
In short, don’t expect it. In fact, it should be supported to ensure that:
a. we don’t return to a centralise system
b. we don’t put all our eggs in one basket
c. we build redundancy, continuation, and resiliency.
_