I’m sure there are some good reasons, but I don’t know what those reasons are.
I’ve noticed that sometimes the instance of the community doesn’t match the instance of the user who posted there, and I was wondering why they chose to post to that community instead of an equivalent one on the instance they joined. Are there pros and cons to doing this?
Your instance has nothing to do with the communities you engage with. There is no reason to try to duplicate communities on each instance. The entire point of federation is that we all get to talk to one another.
Your scenario would be like only emailing people with .Hotmail accounts.
I’m not trying to make any argument either way, I’m just curious why people made the choices they did. For example, I saw someone from
lemmy.worldposted onprogrammer_humor@programming.deveven thoughprogrammerhumor@lemmy.worldalso exists. I’m wondering how they chose the first option over the second.Usually, activity: https://lemmyverse.net/communities?query=programmer
The programming.dev has 3.6k weekly active users, the LW one has 84
Probably because the community in the other instance is more active or has more subscribers.
Does that affect interaction? Perhaps this is a difference between platforms? When I signed up to PieFed, I chose some interests and it automatically subscribed me to various communities, some of which had the same name but different instances (for example five different communities named “Games”). I don’t know much about how community discovery works on any of these platforms to be honest.
On Lemmy, it will definitely affect interaction.
Piefed has the consolidated comments view who can help with keeping all comments from a crosspost visible (for instance https://piefed.zip/post/181387 ), but Lemmy doesn’t have that, so posting on the most active community will usually get more answers.
It’s the beauty of federation. Under reddit etc. If a community you were interested in had shit admins, there wasn’t much you could do. Here you can create your own theme park with hookers and blackjack. Growing it to build something great.
Does it create duplication? Yes some. Though new backends like piefed are supposed to be addressing it a bit. But more importantly it creates competition.
Well, on Reddit people often do create new communities for the same topic because they don’t like the rules/culture/mods of the original one. So would you say that’s the same reason for choosing a different community on the Fediverse?
Yes, but they can’t make use of the name on Reddit. So if you didn’t like how r/movies was made, the odds are there’s no intuitive name for a subreddit to take left to try and compete with them.
Not that you even can effectively compete with them because subreddit promotion on reddit is total garbage.
That happens sometimes: https://feddit.org/post/7025680/4263481
Certainly to an extent. Though the fediverse model is much more elegant and clear. Plus it offers massive benefits to organizations. Seeking to have communities and comms that they can truly call their own. Maintaining as they see fit. The KDE and blender groups for instance have their own servers and their own communities on them. That they can manage and focus on just their projects. No missing on the servers with toxic political communities like leninists or fascists. Just their projects and only their projects or things related to it.
In short: The Fediverse is one universe and everyone is supposed to be able to interact with everyone. If you like the technology community on A better, use that. If you like the one on B more, you can engage there. It’s supposed to not matter a lot where exactly you are. But sure, you’re allowed to create yet another community about the same topic on C. Downside is, someone needs to upload content there and comment on things.
That’s the way the fediverse works.
Someone posts something to a community on one instance, then it’s mirrored to all of the federated instances, and people on all of those different instances see it and, if so inclined, reply to it. It doesn’t really matter which instance it’s posted to or which instance the response comes from - it’s all shared throughout all of the federated instances.
