Hi everyone,
I just joined and am now exploring this place. I noticed there already are similar communities on different instances. For example there is a vexillology@lemmy.world and a vexillology@kbin.social. Is there a way to “join” or “sync” these different spaces? Or will they just be separate?
I think It would be nice to connect places like these. As far as I understand it if one instance goes down all their communities disappear. With “synced” communities across instances this could be avoided since they act like a backup for each other.
So far I like it here and am looking forward to how this all works out.
Thanks everyone for contributing and running this place.
They’re different communities, just like /r/tech and /r/technology, /r/DnD and /r/dndnext, or the million different aita subs that popped up last month.
There is a GitHub issue for the Lemmy equivalent of a multireddit which would allow you to create a compound feed of several communities. Others have gone further and requested some kind of automatic merging, which strikes me as a pretty terrible idea… they’re different communities with different rules and different mods and maybe different cultures. Sometimes they exist separately because the mods don’t like each other or have very different ideas about what the culture should be. Transparent merging in such cases is awkward and creates confusion.
My advice is to consider the server name as if it were part of the sub/community name so that !this@that.com is just a different thing from !this@there.com. Dupe subs have always been a thing on Reddit, they’re a thing here too. They will get better with time as community discovery improves and people aggregate in the active/well-moderated ones and the abandoned ones die off.
This issue on GitHub seems to have an interesting idea.
Instead of automatic grouping, what they’re suggesting is a sort of “request” from one community to another to sync their content. So two similar communities that have two very different cultures could decline syncing.
Yeah, I’ve seen that proposal. It’s not all that much more compelling to me. If mods were willing to be grouped together, why would they not also be willing to merge their communities entirely and retire one of them? What compelling capability does three but kind of one communities give you that one community with three mods doesn’t?
And more importantly, are those capabilities more valuable than the simplicity of people not having to understand these compound communities. Federated designs are generally significantly more complicated to use than “normal” designs. A sprinkle of federation in a system design is a very powerful hedge against individuals coopting the ecosystem, and that make the extra complexity worthwhile (to me, there are smart folks who say that federation is DOA because it’s inherently too complex). But almost all people with experience designing federated systems agree that a heaping shovelful of federated system design makes a system an unusable mess of conceptual complexity that no one will bother to learn. It seems pretty clear to me that compound communities fall into this heaping shovelful category, and do no “pull their weight” in complexity. Reasonable people can disagree, but I both would not use such a feature unless I had to… and I think the lemmyverse would be better off without it.
Instead, it’s my belief that devs should focus on improving community discovery so people naturally find the most active communities, low-traffic ones die off, and we eventually reach a mature state where… like reddit… even though community duplication is allowed… no one cares about it because the better run communities naturally grow and are easy to find. Improving community discovery has more powerful beneficial side-effects in other ways as well, and if done properly could reduce complexity rather than increase it as this proposal does. But to each their own, maybe other people see something I don’t.
Thanks for the input. Maybe thinking about instances as “different things” is something that we just have to remove from our brains. Instead one could think of them more like “apps” (like RIF vs Apollo for reddit) since they all access the same platform, but influence which data from the platform you see and the way you see that platform.
Maybe thinking about instances as “different things” is something that we just have to remove from our brains. Instead one could think of them more like “apps” (like RIF vs Apollo for reddit) since they all access the same platform…
Instances definitely are different things, they just happen to communicate with each other most of the time. I’m wary of too many analogies, but if you need one I think email is a better one than reddit apps.
- Like email, you have accounts with a provider (gmail/yahoo vs lemmy.world/lemmy.ml).
- Like email, accounts can generally communicate across providers (beehaw defederation shenanigans aside).
- Like email, you can’t use an account from provider-a to log into the website for provider-b. You can’t use your google account to log into yahoo.com, and you can’t use your lemmy.world account to log into lemmy.ml. But as previously noted, you CAN communicate with users from that provider… you just log into your own provider to do it.
- Like email, different Lemmy providers might have slightly different rules for their users. Most of the time this doesn’t matter, but sometimes it does. If you want to run a mailing list for 100k subscribers, you do that from mailgun and not a personal gmail account. If you want to run a sexysexsex community, you do it from an instance that allows that.
So that’s a better metaphor, but mostly I think we need to move past metaphors and just learn what things are and what they do. When people taught your grandma how email worked, they used metaphors about the pony express, now people just know how email works. With federation, you’re the grandma and people are using lousy metaphors to help get you started. But learn how it works and you’ll be better off.
