this post was submitted on 24 Jun 2023
70 points (98.6% liked)
Fediverse
28534 readers
326 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's the idea, but the reality is turning out to be very different with defederation. The result is two users looking at the same post see different content, which is not a great look for an aspiring reddit replacement, frankly.
I think the multiple communities of the same topic across different instances is a mistake honestly. Information/discussion should be concentrated, not spread about a bunch of places.
I read on here they are working on a method that would allow communities across instances to merge. I hope that happens.
Imo, federation should mean the same communities are replicated across all instances. If an instance wants to house its own content, they can maybe make a community that isn’t replicated to all the others but accessible nonetheless by everyone (ie Piracy community, maybe not every instance owner wants to replicate that to their instance).
I dunno, the bifurcation of communities just seems like a mistake and less efficient than everyone in the same place sharing knowledge and ideas.
Having multiple communities in different instances for the same topic is a controversial topic that I haven't yet settled on an opinion about. However, what I'm talking about here is that the content for the same community shows different across various instances. That seems very broken to me
There are two things in play here. One is that beehaw has lemmy.world defederated due to high moderation volume, so that connection is broken. This is part of how federation works and is to some extent inevitable. Because it's splitting community userbases, however, I do think that defederation decisions can be more fraught on lemmy than they are on Mastodon in some ways. The only solutions here are, either the moderation load is reduced to the point beehaw refederates, or moderation tools improve to make it easier for them to manage the load, or you migrate to an instance that isn't defederated.
I do think it strongly incentivizes mainstream community creators to set up shop on instances that are both large and well-moderated, to make it the most likely that the most users will be able to access that community. (Because other instances won't want to defederate.)
The other thing is that some servers that are federated still have issues with comments getting lost. This is a technical issue that is supposed to be improved with the new version of Lemmy. How I see it manifest on blahaj is that with some of the busier servers, especially lemmy.world and lemmy.ml, some comments never make it over to blahaj.
There is a workaround, sort of, which is that if I search for a specific comment by URL, that alerts blahaj to its existence, and then it appears. But I have to know the comment exists and care enough to go the trouble.
We need a lemmy client that has the option to "merge" communities of different instances on the app level.
There's already a Lemmy issue for that. Presumably one for Kbin too, though I'm not aware of it specifically at this point.
Ive been thinking about how to do this but the issue I see related names don't necessarily mean the same type of community.
/c/latex on one community and /c/latex on another can be VERY different things, so you need to let people create their own groupings, but that seems like too much work.
But going by name is perhaps a good start.
You could give the user the option to do it manually
Can't disagree more.
There's a very toxic dynamic on Reddit that many people don't want to acknowledge. Once a space hits a certain threshold of users, discussions die, and everything switches to bids for attention. These bids don't further anything but further bids for attention.
I dunno about this. I REALLY like the idea of fragmenting the whole user base. When a community gets too big it ceases to be a community.
Why does the whole internet need to see then same content, and be a collective hivemind?
Whats wrong with the current user size we have on this current community? Id even argue its too big already. If it blows up by 100x we run back to having posts with 10k replies, 20 or so which everyone will read. Its a really dumb system
I like both, in their own time and place. For memes, news, etc? I don't usually need to comment on those posts, but I do like there to be a steady stream of new content from a bunch of people. In that case, I'd love there to just be a bigger community, even if I don't feel like my comments (if I made them) would be read.
However, if I'm trying to have discussions about Magic, Zelda, teaching, or cooking, then I would rather have the smaller community to actually have discussions. Even it that case though, having one place as a "news aggregator" for that hobby would be nice.
I understand how instances that don't federate with another instance won't show content, but I've checked a bunch of instances. Could it be that beehaw, lemmy.one, reddthat, lemm.ee, and feddit.de have all defederated from lemmy.world? They all have a different mix of content
Your confusion is warranted and I don't have a good answer.
That's kind of the issue. Everyone's vision of content in the fediverse is being filtered by their isntance, and most critically, it's being done in a non-transparent way. Looking at post from beehaw, if you didn't know any better, you'd have no idea perfectly decent comments are being hidden for no reason. Extrapolate that accross multiple instances each with different other instances defederated, and its just creating endless confusion and fracturing the social aspect of a social network.
Ah it didn't occur to me that mods at various instances may be removing individual comments. Can an instance moderate the individual thread comments of a community from another instance? I was thinking that federating with another instance meant all that instance's threads and comments would be available to your users in turn. If that's not the case, then the only way for a user to be sure to get all of a community's content is view it from that community's home server
I agree. Unfortunately this is a do or die problem I think. Either they find a way to bring these communities together or the fediverse remains fractured and will never pick up steam. I'm over reddit, but I long term there's no way I'm checking 5 identically named communities from 5 different points of view to try to put comment chains together...
You're talking about different issues I think. What OP mentioned is inconsistency with one community being seen across different instances.
Right, so if I can see A and C from my vantage, but from A I can see ABC, and from C I can see ACD, then I have to view the same chain of replies from several different vantage points to get the whole conversation.
The inconsistency is that you can't see ABCD in a comment chain from every vantage point.
Imagine if Discord was like that... it'd have folded a day after it released lol.
I think the solution is for federation to be bilateral. If A defederates from B then A cannot see a B article and B cannot see an A article. No more fragmented comments, all comments are sent to the server the post was made on, and read from there as well. This half-copy sometimes-delayed fragmentation is just insanity even at this small of a scale, and I don't see a way to scale it without the house of cards falling.
That sounds honestly like something that the Zuckaverga would propose. It only benefits the largest instances, and basically kills the smallest ones and ones that are intended to function as safe spaces.
High volumes of posts, low server bandwidth, or an instance with too few worker processes can just slow down the syncing process.