Unpopular Opinion
Welcome to the Unpopular Opinion community!
How voting works:
Vote the opposite of the norm.
If you agree that the opinion is unpopular give it an arrow up. If it's something that's widely accepted, give it an arrow down.
Guidelines:
Tag your post, if possible (not required)
- If your post is a "General" unpopular opinion, start the subject with [GENERAL].
- If it is a Lemmy-specific unpopular opinion, start it with [LEMMY].
Rules:
1. NO POLITICS
Politics is everywhere. Let's make this about [general] and [lemmy] - specific topics, and keep politics out of it.
2. Be civil.
Disagreements happen, but that doesn’t provide the right to personally attack others. No racism/sexism/bigotry. Please also refrain from gatekeeping others' opinions.
3. No bots, spam or self-promotion.
Only approved bots, which follow the guidelines for bots set by the instance, are allowed.
4. Shitposts and memes are allowed but...
Only until they prove to be a problem. They can and will be removed at moderator discretion.
5. No trolling.
This shouldn't need an explanation. If your post or comment is made just to get a rise with no real value, it will be removed. You do this too often, you will get a vacation to touch grass, away from this community for 1 or more days. Repeat offenses will result in a perma-ban.
Instance-wide rules always apply. https://legal.lemmy.world/tos/
view the rest of the comments
If one of them is down we see half the posts but they should be together and one. Hopefully the mods won't get a power trip and try to make separate
Make it like a collective: mods can remove their community from a federated collective if they want. Mods can only moderate stuff posted on their community, not in other communities in the collective. But unified rules or just some space for text in a collective will make it seem much nicer and coherent even if it is still a bunch of different communities behind the scenes.
I dislike that idea. It brings a lot of messyness if the only mod on one server is asleep, etc.
Im not sure if one god owner of a "federated community" is the right answer. But i do think nods across multiple servers is the right answer? Perhaps giving all individual server community owners equal powers is a good choice?
Edit: Maybe it's something server admins could do? "Hey, c/photography, is now an alias for [email protected]". Maybe if they decide to unalias it, the local photography becomes a mirror of the remote instance. Then local users could interact as normal, and the remote instance would see incoming users acting as normal remote users?
I think the balance between "sovereign communities", benevolent (?) dictatorships with one super-admin, or democratic collectives needs to be found. Ultimately this is something that needs to be hammered out, but any solution would be better than none.
Three possible solutions (just spitballing, not much thought put into them):
Of course, in all cases, an instance refusing to honour the powers of governance authorities would be interpreted as the instance admins withdrawing the community from the collective. Sort of like automatic defederation.
Ya'll are basically talking about how Lemmy works already. You have c/photography on Lemmy.ml. And while you're logged into Lemmy.world, it's c/[email protected].
You subscribe on Lemmy.world and comment on Lemmy.world and everything is synced. If Lemmy.ml is down, you can still see everything and comment from Lemmy.world and itll sync once Lemmy.ml is back online.
I mean, yea that makes sense but I see a ton of dup communities that don't seem even remotely synced up...I could be wrong but yea 🤔
If you’re talking about communities existing on each instance, ie lemmy.world/c/photography and lemmy.ml/c/photography then yeah, those won’t sync. But the users need to coalesce around once of those, say the lemmy.ml one, then when you go to lemmy.world/c/[email protected]. The duplicate communities is no different than Reddit having 2 similar subreddits.
That's not what they're talking about, though. What they're wanting is something that would, for example, combine the feeds for c/[email protected] and c/[email protected] into one collective c/photography.
That’s just unnecessary, though. The only effect of this is to have numerous separately moderated communities, which sounds like a nightmare to me.
That's... already the case? c/[email protected] and c/[email protected], again for example, are already separately moderated communities. The only thing this would change is that instead of subscribing to both individually and seeing their content separately, you could subscribe to a collective c/photography that would show you content from both communities.
I guess what you’re looking for is the equivalent of a multireddit.
That's why i changed my wording part way through to "Alias." Allowing someone to say, "this name actually refers to an offer server name."
This means that the shitty UX of searching for cool communities is marginally better.