Right now there are similarely named communities across the fediverse.
“fediverse@xxx”, “Linux@xxx”, “asklemmy”, “askkbin”…etc…
I’m on kbin and I’m having a hard time figuring out how to use the fediverse more productively, by reaching the largest amount of people for asking questions, solving problems, simply put: to engage… like I used to do on Reddit?
As @flloxlbox said, it will either happen organically or users will decide to merge communities, like the Android community did. It’s the way federation works, it’s not something that can be forced on people.
I would like to see some kind of “canonicalization” feature in Lemmy to support this, similar to CNAME in DNS.
For example, !android@lemmy.world recently merged into !android@lemdro.id, where lemdro.id is the canonical server.
So it would be awesome if !android@lemmy.world was entirely equivalent to !android@lemdro.id. But as it stands, the lemmy.world community had to lock and everyone had to individually migrate themselves.
Essentially, in a case like this, I just want to call it !android (or c/android) and not need to care about which server it is hosted on. But as it is currently, I always have to reference the canonical domain since it is different than the one my account is on.
For example, !android@lemmy.world recently merged into !android@lemdro.id, where lemdro.id is the canonical server.
Off-topic and what follows doesn’t mean your CNAME idea is bad, but it’s important to highlight that this example is wrong because the “merger” was forced because current mods were victims of imposter syndrome and felt obligated to gift the community to Reddit mods on another instance and denied us 19k members a say in this, and we are right now requesting to cancel it because it was a one person move. See more context in my comment here: https://lemmy.world/comment/980033 . In short, there is no “merger”, it is a rogue mod move and if you liked !android@lemmy.world and never asked to move, I recommend you stay because I believe we can absolutely defeat this hostage-taking and reopen the community.
Yea. The mod unilaterally made the decision to lock the lemmy.world instance without input from the thousands of users. They then doubled down on at least one response saying basically they same shit spez shit Reddit’s changes. It’s ridiculous. Ideally, if someone wants to lock a community for nothing but selfish reasons, and should be able to take it and reopen for someone else to take over.
Ugh. I thought this whole thing seemed fishy. It was way too quick of a pivot from the lemmy.world Android mods being upset about the new /c barging in and trying to hoover away their members… to them happily handing everything over and closing the doors.
Just goes to show how insidious the behind-the-scenes of Reddit mod drama really is/was. And a shame that it’s just getting dragged over to Lemmy.
Forgive my ignorance, I’m not trying to argue, I just want to understand. What is the benefit of keeping the @lemmy.world one open? Why do people not want to hop over to the @lemdro.id one? I saw the post and just subscribed to the new one, and I thought it was easy enough. I don’t see what the difference is, or why it’s worth the drama, tbh.
You’ve made two threads about this already. It really doesn’t need to be spammed everywhere.
Aliasing is a thing on Mastodon user accounts. There’s no conceptual reason it couldn’t be extended groups on other platforms, too.
At the same time, if group aliasing became a thing, one should not expect that one group become an alias of another. Centralizing communities doesn’t always make sense, and our Love of Large Numbers is something we should actually actively push back against.
Aliasing makes sense when you have a dozen tiny communities, none of which are large enough to be self-sustaining. Once communities have crossed the critical limit and become viable all on their own, we really shouldn’t actually want them to merge with other viable communities. Smaller communities are easier to moderate, are generally friendlier spaces, and the promote a larger diversity of opinion and active, meaningful discussion.
Bigger ones devolve rapidly into jockeying for attention.
If you’re only going to read 10 or 15 posts in a community, be it one of 1000 users or one of 10,000,000, then you’re generally going to be better off with the 1000. Anything big enough to make it to the top of the big blog will probably be discussed in the small one, too. But the opposite is just not going to be true.
This is how Threads would take over the Fediverse and eventually win when they decide ActivityPub development is too slow and holds them back.
Boom all your communities are now empty.
Federation works because we’re spread out. Just subscribe to all the small communities.
Now, what might be a better idea is a cross post functionality where the crosspost has a single identifier of its own so it only will show up once in your feed (I guess as your local instance)
That way you can have the ability to reach everyone as if you had posted a bunch of times, but a big popular corporate instance can’t gather up all the communities and then defederate and wall them off.
Threads is a Mastodon analog.
Reddit is a Lemmy analog.
There are no Threads communities!
Or perhaps a reciprocity between communities, where instead of everyone subscribing to c/mushroomA and c/mushroomB, the community of mushroomA would decide to reciprocate w c/mushroomB so their posts would display alongside mushroomA posts. Kind of like a keyword association that generates a multi-Reddit like co-mingling.
Edited to remove all those pings.
It may just take a while for the go to communities to hit a critical mass. The same thing happened on reddit for smaller topics, one will eventually have the large majority and the others will die
It is no different than reddit. Eventually one community will have the momentum to dominate a space and everyone will gravitate to it over time.
The only feature I think we need is an admin curated keywords option for mods to add in search results for communities. Like people often search for bike when they mean bicycle. The old reddit community name for bike repair is called bike wrench. It is the same here. The main community for bikes in general is Bicycle. People may or may not find communities based on these keyword differences.
The easiest option ATM would be for an app to combine both communities into one synthetic feed
It would be neat if communities from different instances could federate with each other like the instances themselves do.
In my mind it would work like this:
If two communities have the same topic, and have compatible rules, then they could federate with each other. This would show the posts from both in a combined view in whichever instance you were logged in on.
For moderators there would be two types of posts.
Posts originating on their instance they would have full mod control over, and any actions taken on the posts would change the post for all other communities they are federated with.
Posts originating from federated communities I think mods should be able to hide in the local communities as well as a subset of other mod abilities, like sticky. However these would only affect the local copy, not the original or the other federated communities.
As far as I know neither Kbin nor Lemmy has anything like that, but I think it would be a great feature if either could make something like that work.
Honest question: If a federated community is conceptually acting as a single community, why should moderators be limited to the side corresponding to their instance? At that point, wouldn’t there be a unified ruleset for the federated community that is separate from the rules of the hosting instances?
I get that not all instances would abide by the same rules, but I reckon that if you want to keep a federated community, you also need to make sure to comply with all instances or risk some instance from removing their community from the federation.
I think there are a couple of reasons to not allow mods on one instance to moderate posts on another instance.
One example I can think of, if I wanted to grief a community I might go to another instance that doesn’t have that community, create it, making myself a mod in the process. Then I would request federation with the community I want to grief. Then I’d mod away all their posts, or do anything else I wanted. With some luck and okay timing I bet a person could do a lot of damage before federation was turned off. People in IRC chat rooms used to use a similar technique to steal OP from others in rooms. Making modding of federated content only effect the local instance would contain any of that damage. As a feature creep sort of feature, perhaps modding done on an instance could send a suggested mod response to the originating instance, and they could do what they wanted with the information.
Also, having it set up like I originally suggested could allow for other non standard federation arrangements. Like one instance that allows nsfw content in a community to be federated with one that auto blocks anything marked nsfw. Maybe even one way federation, where an instance shows posts from another in a community, but it isn’t reciprocated. I don’t think that would be usually the best idea, but it might work.
It might also help with the potential problem of entire communities being eradicated by rogue actions from an instance admin, or instance issues in general. If the community is spread out across multiple instances, it can weather problems on its “main” instance without being as easily dispersed.
