i’ve seen the sentiment that most of the growth being on lemmy with .world taking on the large share of users isn’t necessarily positive. other than the fact that the point of federation is decentralizing, what kind of issues arise from congregating heavily in a single instance?

i know even in just .world there a few redundant communities and i imagine that this is compounded in other instances. i don’t suppose i should expect or even want monolithic communities at the whim of just a few moderators or admins, but i don’t want to miss out on discussion and content for communities i’m interested in.

i guess i’m just curious what the development of communities and their interaction should look like with federation, and how browsing and engaging with these disparate but related spaces is going to work for the average user.

apologies if my questions about federation are basic or these questions are well known and understood for those who have been a part of communities like this for longer than i have.

  • @[email protected]
    9•1 year ago

    Your post is a bit confusing. You seem to be using Lemmy to refer to lemmy.ml? and just .world to refer to lemmy.world? Or do you mean Lemmy as in all instances? Or Lemmy the software? Or the threadiverse in general?

    • @caephiOP
      6•1 year ago

      maybe i mean .ml. i was under the impression that .world and .ml were closely related but distinct instances, as opposed to kbin which is federated but not as closely related as lemmy instances. like i said, this is new to me so i’m still getting a handle on how everything exists and interacts.

      i think the core of what i’m curious about is if there is an issue if a singular instance in the ‘threadiverse’ gets large enough and if that has negative implications for other federated instances. if users largely centralizing in this decentralized platform detracts from the goals of federation?

    • ShittyKopper [they/them]English
      3•1 year ago

      Not sure on lemmy.ml but the “dot tld” (.world) is an already established convention from Mastodon & co that refers to instances named after the software they use, with that TLD (for example, mastodon.social is frequently abbreviated to just .social, same with .online)