I see this suggestion as problematic and recreating a problem reddit had. One group could lay claim to territory and everyone was stuck with however good or bad the culture was in the sub and however good or bad the mods were. There were some places with mods on a powertrip creating an exclusionary or outright toxic environment.

There are better solutions to the problem. For example, letting communities follow other communities. It's simple and flexible.

Take a look at the discussion here https://github.com/LemmyNet/lemmy/issues/3071#issuecomment-1595303910 or my diagram of one proposed solution.

Unless I've misunderstood something, community names are already globally unique and multiple identically named communities cannot exist, you're just not looking at the full name.

Memes@lemmy.ml and Memes@sopuli.xyz are different names, for example.

Sometimes we ignore the part of the name after the @ if it's unambiguous, but it's still there.

As it’s currently implemented, the Fediverse allows for multiple identically named communities to exist. I believe this is a mistake. The fediverse should have one uniquely named community instance, and part of the atomic data exchanged through the federation should include the instance that “owns” the community and a list of moderators. Each member server of the Fediverse should maintain an identical list of communities, based on server federation. Just like USENET of yore.

Hard disagree. This allows abuse by moderator abuse similar to how reddit does it. Ideally the UI would allow you to create collections of communities based on your own groupings. And search could be expanded to find more similar communities (ie: based on keywords).

The way loading/finding and joining a totally new community into a new external instance is kinda buggy.

I'm one of those USENET greybeards and I think this would probably be a mistake. If you let a name be uniquely claimed by an instance, how do you decide which instance gets to be "in charge" of that?

Better IMO would be to update the various interfaces to be much more explicit about including the instance name along with the user/community name. So that it's always clear that a user or community is at a particular instance.

We do still need better migration tools for moving users and communities around, though.

I think that would defeat a piece of the point of a decentralized system. In the current design, what will naturally happen is that if one instance has all the good content on a particular topic, most users will gravitate toward it anyway. We can read across federated instances anyway so I, a kbin user, have no problem reading something on lemmy like this.

Then let's say one day lemmyworld@lemmy.world gets taken over by people who want to post stuff I don't want to see. If I miss how it used to be here, I could go make lemmyworld@kbin.social and it would be fine.

As I've said elsewhere the communities sharing the same name is just a temporary problem. As the system grows one of the identically named communities will become dominant. Because of that small new communities that want to have the same topic will be incentivised to have unique name just to be able to be found.

I think it's a feature, not a problem. If you have multiple communities for popular topics, if one or two of them turn toxic or have unpopular moderation policies you have other places to go. Think of it like forums, popular topics had many forums to choose from - but each had slightly different cultures. Also since forums could individually be quite small, they were often a lot friendlier.

Federation makes it easy to explore different communities, but we don't need to import the bad parts of centralisation.

They may have the same name, but they have suffixes that don't actually appear, such as @lemmy.world @lemmy.lm. I oppose this idea. Because when the servers do the defedere people don't have access to that community. We have recently seen an example of this. It's okay to have more than one community with the same name, but a lemmy grouping feature can bring. In this way, we can eliminate clutter by grouping communities with the same name. At the same time, the fact that different communities with the same name have different moderation understandings provides people with an alternative in community selection. Reduces moderation pressure

I'm not understanding how this would work with instances who wish to defederate and segregate their community? It seems like an "all or nothing" approach that instances who have defederated already wouldn't be on board with... For instance what happens if beehaw owns the "gaming" community, and then defederates from lemmyworld. Lemmyworld users just no longer have a "gaming" community?

The way I see it everyone naturally assumes we're trying to recreate Reddit but with distributed computing.

I think instead we should be trying trying to create something that gives us the community and communication that Reddit gave us, but democratically and without reliance on or control from any one organisation.

This is going to result in some things that work differently from Reddit. We should work to make the experience smooth and intuitive, but it can end up with a different way of working.

Ether that or allow formeta-communities so that the 500 duplicate copies of "Technology" can self aggregate.

I disagree respectfully, as I think this is a feature and not a bug of a federated structure. It's well known that reddit suffers from the "20K Law", which is that "The quality of any subreddit drops off a cliff after it gets more than 20K subscribers". Which is likely because that is the limit of effective manual moderation.

So, having multiple communities on the same topic would be a fundamental fix to that issue, as instead of one giant community, instead you get different, smaller communities with different culture on the same topic, whose users can still talk to each other.

I think the current system is fine as is, we're not trying to remake a better reddit, we are trying to be better than the limits of reddit.

Having sibling communities would be another approach.

Each one is still homed on their instance, but if the instances are federated the posts from the other instances automatically flow into the community. They would still show the originating instance, but content would be comingled.

This could also be the gateway into instance transference. If the instances are more in-sync, it will be easier to transfer either a user account or a community.

I think this is perhaps the most compelling part of your thinking here, but at the same time, I'm more drawn by the idea of improved portability of instance information than the synchronization.

I may be mistaken, but I think a fundamental aspect of the federation model is the independent operations of each community while enabling their intercommunication, and the sort of synchronization you suggest would be a violation of each instance's autonomy to a degree. Not to say it's a bad idea, just that I think it would better fit a different networking model than what I think the federated model seems to be pursuing.

What if there was a way for communities to self opt-in to an aggregate name. The magazine settings could have an aggregate name that makes them show up under the aggregate tag. Kinda like a hashtag, but controlled at the mod lvl, and completely separate from hashtags.

I understand your idea, but I think it would defeat the purpose of the fediverse. It would create single points of failure that are un-correctable.

I also think many people forget that Reddit never functioned any differently. Everyone seems to have forgotten (and I’m not saying you have!) that there are and were always multiple subreddits for any given topic. With slightly differing names. The only reason people are forgetting this is because eventually one or a handful became pre-eminent and the others died or became transformed into something more niche.

I think it’s a problem that will ultimately correct itself, but I think a tags based system, like hashtags in Mastodon, would be a better solution for tying communities/magazines together through metadata.

USENET was a mess too, though... The entire Alt.* hierarchy was an attempt to route around censorship and I'm pretty sure I recall lots of duplication of groups. /derail

Communities should have categories/hashtags that users can optionally sub to, like the 'metacommunities' like plz1 said but optional and multiple. Mastodon does hashtagging and can be done on a post by post basis. The forum software Flarum has a 'tag'/category system and an additional hashtag system, so what I'm thinking of is more like the Flarum system since it would be awkward to hashtag every single post in a community/magazine/whatever.

So if I wanted to just get solarpunk tech I'd sub to that, but if I wanted that and even moar I'd sub to a generalized Tech tag. Make sense?

Solution is hashtags + community name, not a "fedicommrc".
I was in FidoNet with a BBS in 1988 and on the Internet since 1990 first through a dialup vt100 connection to a Unix login access point for usenet and email before the Internet was available to the public. Communities are a special interest of mine. I started a particularly good one for Permaculture using a mailing list with email. I still run it. Noone should, for example, OWN the only permaculture community in the Fediverse. What are others who want their own going to do to gain users and generate traffic? call it permaculture2 or thatotherpermaculturecommunity or permaculture-general or permaculture-westernworld. Letting one group control any particular Fediverse named community is a really bad idea. Have you ever started and run a community (newsgroup, mailing list, subforum, fb group, google group, webforum, whatever)? Having one group control any named community is bad enough but everyone with an instance having to deal with a fixed list of communities for the entire Fediverse is absurd. You could easily have a multiplicity of communities with the same name but identified with hashtags for subjects they specialize it. This should solve your problem with community naming and with this no distributed list of communities for instances to carry would be needed. You could carry 6 different permaculture communities and each would be uniquely identified with hashtags alone. Make sure to code the software to feature those hashtags prominently along with the community name for ease of finding and subscribing to them.
Are you talking about a Fediverse version of a Usenet newsrc? Those who install an instance and want their own communities named as they choose would just do that and ignore any network-wide policy. Other instances can block them for doing that but they can simply connect with other like minded instances and form their own network and forget Federation. This is especially true when some gang of control freaks own a named community, i.e. permaculture. That is not going to fly. Disunity but independence within the Fediverse will rule.

Yeah I think tags or some other way to congregate similar content from different instances would improve my experience a lot. I got like 3 same subs now on 3 instances and all their content is small, if those three were linked somehow say through a tag, they could interact with each other a lot easier and it would seem like one bigger community.

The fediverse should have one uniquely named community instance […]

So, you know, domain name? Kinda stopped there.

I understand what you’re saying but i have a different idea.

First, user accounts should probably be federated. Or federated accounts should be easily identifiable versus non-federated. Federation is pretty easy if you tie it to google, Facebook, Microsoft saml/openid. I’m fine with those options but I understand how others may not.

2nd, I think magazines should be collapsed until they are not.

For instance, pics.kbin, pics.lemmyworld, and pics.reddit2 should show up as the “pics” magazine. If kbin decides to defed, their content now appears to everyone as pics.kbin.

This adds a layer of abstraction that only appears when it’s relevant. Users could of course decide to display this info if they wanted, but by default it wouldn’t show up.

Moderation is more difficult, but I think federation has a place here too. A magazine could decide to federate, and the mods, with federated identities, would then be able to do the needful across instances. If things don’t work out they could defed their magazine.

It's interesting how this issue is new (in my experience) to the Fediverse with Lemmy. With Mastodon you essentially have this uniqueness functionality built in. Because a person isn't likely to post content to multiple accounts under the same persona. Instead someone will choose their instance and username and that's where you can find them. Sure a user might have multiple accounts but I think usually it's to separate multiple online personas.

I think there is use in having same named communities in Lemmy on different servers because they could be for different purposes.

But I can see multiple duplicate communities with the same purpose being on different servers causing fragmentation. Maybe we'll end up with popularity wars and eventually one duplicate community will give way to the other?