Would be great to be able to aggregate the similar pages in something like a multireddit.

They’re not really “duplicate”. Each instance has it’s own magazines/communites/whatever, and those can have different rules, moderators, etc.

If you want to follow all of them, then follow all of them. If you only want one of them, then do one of them. Reddit had various subreddits all on the same topic, for instance /r/technology and /r/tech, and they had their own nuances, users, rules, etc. One might end up being more popular than the other for whatever reason.

Also keep in mind that they’re subject to rules/moderation/control of the instance they’re on. I’m using kbin.social, but if beehaw decides to do some weird thing or decide they no longer want a technology group, it’s basically out of my control. Whereas a technology group here on kbin.social wouldn’t be effected by beehaw’s stance for their instance as a whole.

I imagine people interested in a topic will just follow all the related groups unless there’s an issue with one of them.

I wonder if it would be worth it to have an option to combine content of communities with the same name from different federations into one feed automatically.

Part of those options could be to exclude a community from a certain federation from that feed if their content in that community does not match the others (r/superbowl for instance, where the name does not match the expected content)

I thought it was kind of funky at first. But I do like the idea that if one of them turns into some reddit-like hellhole, there will most likely be something similar on another instance. It doesn’t take much to subscribe to multiple similar subs.

This is really no different than Reddit. There have always been multiple subreddits for the same topic, with slightly different names. Many were created because the “originals” were found lacking at some point.

There’s nothing wrong with people having multiple options. We may eventually end up in a situation like Reddit where certain magazines/communities of the same topic are more trafficked than others and the less trafficked ones “die”.

I think there’s going to be a kind of lifecycle thing that comes with these things. They’ll sort of naturally sort themselves out. To artificially guide it one way or the other would be to imitate the mistakes of Reddit or past aggregate sites.

Yeah, the defederation of Kbin exacerbated this, but it was inevitable anyway. Even reddit had a bunch of spinoff variants of subs like wallstreetbets. There’s no avoiding it.

Sub to the ones you like, unsub from the ones you don’t. If a community really pulls together then there will be a consolidation point and that’ll be it.

This is a feature, not a bug.

I hope they don’t get consolidated-that’s the entire point after all. One choice for everybody is what the corporate sites have been forcing on us for years. Let small communities develop organically. Who cares if there is some overlap? I belong to three ham radio clubs in Real Life and I value each for what it is. Combining them would kill all of what I like about them.

Can I subscribe to something on Lemmy and read it from kbin?

Things will eventually sort themselves and people will likely gravitate where the community forms. It’s best that it isn’t forced and just let it happen.

It can make sense to have duplicate communities on multiple instances in some situations. For example, if instance A and instance B both have Technology communities, but instance A is defederated from instance C, then that redundancy is valuable to instance C.

There are also ways to reduce redundancy — for example, different rulesets on instance A and B could result in different content in their respective Technology communities. And the questions that show up on each are bound to diverge in some ways.

Ultimately, though, my hope is that admins on the post ranking flank of the fediverse starting looking for more ways to distinguish their instances from one another. Self-hosting presents a number of opportunities that weren’t really available on a siloed corporate platform like Reddit. There’s no reason, for example, that an admin couldn’t start up a Medical instance, and subdivide it into much more topical communities/magazines than you’d find on a “generalistic” instance, e.g. Neurology, Cardiovascular, Podiatry, and so on.

(Just as an aside, Beehaw is a Lemmy instance, so it’s not really distinct from Lemmy in the same way that Kbin is distinct from Lemmy.)

Each community has different mods and different admins (with different rules superseeding the mod rules). Everyone will probably use one of them (or whoever moderates content best) until there’s mod/admin drama and switch over to another one.

go where you want to go. one may be bigger than another and steal the majority of the traffic, c’est la vie.
there is nothing wrong with multiple fediverse instances creating similar magazines/subs

Of course in a magical world all the different basically the same magazines on different instances would get merged seamlessly in the UI with posts all somehow connected.

In the real world I can’t even conceptualize how you could handle moderation (or a random collection of posts vanishing from a thread) with instances that have different rules unless each magazine for different topics was a separate silo.

The natural outcome, without much active effort, seems likely to be that niche stuff is consolidated on a single instance that members aren’t necessarily on in order to have enough participation while popular stuff truly just gets silo’d into different self-sustaining groups that talk about the same stuff but with different culture developed, different moderators, and a different instance.

Is there another way? We’re assuming each one is self-sustaining, it will be good enough or you’ll find one on a different instance…

I expect people will see there’s existing local magazines for a bunch of things, and then to search out magazines for niche interests.

deleted by creator