this post was submitted on 05 Jul 2023
1364 points (97.0% liked)
Asklemmy
43858 readers
1700 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy π
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't have plans to visit other instances, manage multiple credentials.
Either I get to see it all from one place. Or these other places will functionally but exist for me.
If I subscribe to /c/knitting I mean I want every /c/knitting on every single instance in existence.
And I don't want to maintain a list of instances either.
I'm going to go to /c/knitting on the random instance I chose when I created my account and whatever is not there, does not exist.
Communities should not get fragmented on a per server basis. That's just going to encourage users to migrate to the one big instance that hosts the one big community
Duplicate communities should have been prohibited, or at least regulated, from the start. To me the problem is Why TF are people making a 2nd knitting community when one already exists? Instance theme isn't appropriate for the original community? Migrate it.
You're missing the point of having a decentralized network. As long as people are allowed to spin up their own instance, duplicate communities are bound to exist. You can view both of them or choose which one you prefer.
No, your missing the difference between can and should. We're in the fledgling stages of this Federation and already there are duplicate communities. How are these anything but an aggravation and hassle to newcomers trying to figure out what is where? You see freedom, I see obfuscation and dilution possibly to the point of absurdity.
Honestly, users that can't be bothered to check and subscribe to all knitting communities (which is really easy) will be snatched away from the first corporate alternative with more polish.
Open source applications rarely beat corporate ones in polish and ease of use; these aren't the battles we have to fight. Lemmy is already near identical to reddit once you sign up and subscribe to the communities that interest you.
You don't have to manage multiple credentials. You can visit and subscribe to /c/knitting on another instance as long as your instance is not blocking it, or blocked by it.
Would you? The point of having multiple instances is that
/c/knitting@gaming.lemmywill be mostly about knits inspired by gaming,/c/knitting@memes.lemmywill be mostly about knits inspired by memes and so on. You may not want all of them. This is a bit of a stretched argument, but I want to showcase an example where fragmenting communities on a per server basis can be useful.I know that for generic communities or hobbies it can be annoying, but it isn't that hard to find the largest /c/knitting and subscribe to that, no matter the instance. Reddit's centralized approach is more convenient, but we've seen the price we have to pay for that convenience.