This Community is intended for posts about the Lemmy.world server by the admins.
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
Any support requests are best sent to info@lemmy.world e-mail.
If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.
If you can, please use / switch to Ko-Fi, it has the lowest fees for us
The underlying problem here is the lemmy community being spread out across many instances, and this solution doesn't really fix the underlying problem.
This is just speculation, but I think eventually 1-4 instances will grow much bigger than the rest. I think when this happens, communities will become much less fragmented and the problem will solve itself.
tl;dr while this is a good idea, I think if we just leave everything the way it is the problem will solve itself.
Isn't a few large communities eating up the others like the opposite of what Lemmy is trying to do?
i keep hearing people call for this like its going to happen and be the only way things will be. Look at reddit, look at the history of some of these subs.
there will always be multiple copies of various communities. what software gives us the ability to do is sort and filter and tag (we need to add this) to our hearts content so instance admins and users have control over what comes across thier feeds.
Joined communities will have many of the same centralization problems reddit has now. I've seen this call mostly from users who were on reddit long after it was large. It seems many have no idea that almost every topic on reddit has 4-6 subs around it usually.
If people are satisfied with them, I think that's OK, and more efficient than having a zillion.
Problems will happen if we go too low, and bigger instances start de-federating. Some might be tempted to start monetizing like Reddit.
see I'm not sure I see that as a problem. There are lots of reasons to spawn a new but similar community (bad community mods, bad server admins). There are lots of subreddits I avoided because they were just too big to get into any real info or discussion, just the same beginner questions asked over and over again.
The goal of implementing this feature is to leverage the benefits of federation. If we wait until there is only a few big communities, the purpose of having federation becomes irrelevant. When an instance hosting one of those large communities shuts down, the community would have to migrate to the next major community.
By proactively implementing this feature, Lemmy can harness the advantages of federation while actively mitigating the challenges posed by community fragmentation and echo chambers. It provides a centralized hub that encourages cross-pollination of ideas, fosters community engagement, and ensures that valuable content is accessible to all users, regardless of the size or popularity of individual communities.
I honestly wouldn't want that, a feature like multi-reddit would be much better IMO.
I personally don't want to be "automatically" subscribed to all tech communities for example just because I joined one, nor I want to be flood by an immense feed because all communities of the same type are put all together, that takes away individual choices IMO.
We had exactly the same problem on reddit, but multi-reddit solved that very well by leaving the choice to individuals instead of being forced by admins.
EDIT: for those who don't know, multi-reddit is a reddit feature that allows you to create different "labels" into which you can combine different subreddits, which label to create and which subs to combine is totally a user choice, those labels become "tabs" into your UI that you can use as they were individual subs.
So for example, I can create a label/tab called "linux" and use it to combine r/linux + r/linuxmx + r/xfce, etc., than I can create another label called "games" and combine r/MMORPG + r/wow + r/guildwars2, etc., and so on.
multi-reddits can be private, that is only the user who created them can see them, or they can be made public, so if some user doesn't want to create their own, they can use multis created by other people.
join a meme sub
get joined to 15 meme subs
every meme is posted 15 times
surprised pikachu face
15 surprised pikachu faces
ftfy
I like this idea, however it would need to be intuitive to use and clearly advertised as a feature with a plain explanation up front. I say this because I'd never heard of this feature before and I used reddit for over 15 years (had to Google how it worked after seeing your comment).
I tend to agree with your take on this. I'm getting serious FOMO over here and over-subscribing because I don't know which sub will be the one to "take off."
How about a mod option to voluntarity merge another community into their community?
This would be great
I think you perfectly described my issues with comment sections on Reddit for the last few years. That attempt to appeal to an audience rather than further the discussion.
I used to love comment sections as much as, if not more than, the actual post on Reddit. It felt more like a conversation that had insight and humor. It got too big for it's britches and became that soulless monolith.
I get an almost nostalgic vibe from this place. It's nice.
Well, it's the nature of almost any online community. Say the 'popular' thing and you're lauded, even if a slightly less popular point is more valid / has better evidence.
There really is no good way to discourage this other than fostering a community which values the discourse over 'popular' thing. That's difficult to do even offline.
Why not make this purely client-side? Give me the option to merge what I see as like-minded feeds into one feed. Label it and be able to scroll it as one feed. All without the need for admins or instances to do more work?
I donβt think Iβm understanding this right cause it sounds like youβre trying to make it more fun by adding more rules. If there are 20 groups that are all about pickles thatβs fine they each like running things their own way. Eventually one group gets popular and thatβs where the majority goes. I think your frustration could better be solved with something like tags where groups could choose to associate certain tags words that makes search easier like tag: pickles-fermenting-homemade-cucumbers and that could clear up search from people just wanting to share pickle Rick memes.
Yes the fragmentation is a feature not a bug. There are dozens of reasons why people might want to leave a community and create their own alternative version. With blackjack and hookers.
Combining communities should be a front end feature... Allow users to merge their views if they want. But it should not be enforced at the backend or federation level.
Eventually there will be third party apps which can do this merging in their interface if someone wants it.
Combining communities should be a front end feature⦠Allow users to merge their views if they want. But it should not be enforced at the backend or federation level.
Eventually there will be third party apps which can do this merging in their interface if someone wants it.
I agree with this. The grouping should be a front-end feature based on hashtags, as someone else mentioned, instead of the community names. Alternatively, there could be lists that you can simply copy and paste to create your own multireddit, eliminating the need for hashtags. However, considering that the original issue was already on the lemmy-ui, I'm not sure why you brought up the backend.
reddit also had that a bunch of places, for example /r/gaming /r/games /r/truegaming etc. etc.
I feel as others had suggested that client side multi~~reddits~~ communities would be ideal so you could set up what groups you like to peruse yourself.
I see very little discussion about the implications of this for moderation, and it feels to me like they get very sticky. With traditional human-curated multi-reddits, you as a subscriber must engage with the idea that you are choosing to aggregate multiple communities into a single feed, which is intuitive enough, the subscribed feed already works that way.
But by making it automatic, the software hides the fact that it's pulling together discrete feeds from communities with different rules and different moderators. This feels very awkward to me. I'm all in favor of traditional multi-reddits, which can be used to create this sort of feed for yourself. I'm still on the train of "duplicate communities will sort themselves out if community discovery is made much easier and popular communities reliably show up at the top community searches, mostly irrespective of what instance the search was performed on" (obviously defederation takes precedence here).
I think a community needs to add the option of a topic hashtag, so communities can group together in that way if they want to, and people can subscribe to these hashtags if they want to (with the ability to remove single instances of they want to)
The theme here is "if they want to" giving choice to both the communities and the subscribers
I think this would be the best, but it will probably be a choice of each community moderator not the users.
For what itβs worth, Iβm VERY much for this.
One of the pain points for those coming into this to fill the Reddit void is fragmentation. Beyond being a huge improvement in usability, information would be shared much more easily this way. For someone who spends a lot of time in IT/tech related subs, thatβs very important to me.
I am working on a multi lemmy manager that Id love to get some alpha testers to.
I like the general idea of merging communities, but I'm not sure if I like the idea of it being automatic. What if instead communities could apply "hashtags" for their community, and then you could efficiently browse multiple communities at once. For example, I'm subscribed to a few different TTRPG communities across a few different instances, but what if each of those communities was tagged "#ttrpg" and then I could browse #ttrpg instead of browsing any of those individual communities.
Cross-instance "multireddits", that are also automatic and topic-based. #1113
TL;DR: The suggestion is to implement an automatic multireddit feature in Lemmy that displays all posts from communities with the same name across federated instances. It aims to promote decentralization, avoid echo chambers, and ensure high availability. Community moderators would have the option to opt-in or opt-out their communities from being displayed. There are discussions about potential issues such as community name collisions, duplicates, abuse, and practical implementation. Some propose using a new link format, while others suggest providing users with a list of related communities.
We need both options. Some systems like USENET use a global groups list (rec.radio.amateur.misc is the same group everywhere). Federated communities need a similar option.
Sure, let me create my own c/gaming if I want, but also give the option to⦠merge? combine? cross-federate? Not sure what term fits here.
!gaming@me, !gaming@you, and !gaming@them can be 3 separate, distinct, and independent communities (like it is today).
!gaming@me, !gaming@you, and !gaming@them could also be the same !gaming community, replicated and synced across all 3 servers.
Hereβs an idea. Add another name to the community designation. So you could have !gaming#context@instance. (Or whatever separator makes sense. You could even just use a subdomain like !gaming@context.instance, but that might be harder).
In this model, #context refers to a shared view of the world that instances can choose to participate in. As the instance admin (or maybe a mod??), I choose to join #context1 but not #context2. When I do, All the !communities under #context1 become available for me. I still choose the ones that are appropriate for my instance. This would mean that when a new instance joins the federation, it acquires the shared set of #contexts that the federation publishes. A different federation of instances could still have different contexts.
(All of this still feels clunky. USENTβs simple hierarchy still makes so much sense, but it unfortunately places all the control at the group level, not the instance/user level.)
I recently suggested @global for consolidated communities. There would have to be some kind of consensus on who and how communities would consolidate. I agree that having that does not get rid of all the other permutations.
Damn, this is a lot of discussion and I don't see a single person actually volunteering to actually go code the feature. It's open source, you know? If anyone cares about the feature, go learn rust (like I'm trying to do now) and code it up.
EDIT: In case anyone reads this, please look at entitlement in open source. It's an eye-opening read for those not familiar with the headaches involved.
I'm honestly more confused than I was before. With so many opinions, I don't know how this could ever be implemented in a way that satisfies people.
It'll be solved the same way anything gets solved in open source: those that can code make the final decisions.
I would kill to just have some help/pointers figuring out how to navigate this... Fediverse?
I've made a couple posts, on one, maybe two, um, Instances? In the communities there?
I don't know. All this change is coming at like, the WORST time in my personal/professional life and learning a whole new world is just... Daunting. (waahhhhhh π)
I'm new too, but here's what I've learned in the last week:
You're a user of and logged into @beehaw.org. This post (and the community it was posted to) exists on the @lemmy.world instance. You can see and post to it from your beehaw.org instance, because @lemmy.world also exists in the Fediverse.
My instance is @lemmy.world, so this community/post is "local" to my instance, but in practice that's not super important. All that tells you is where I enter the fediverse, from there we're able to see and post in communities from across instances. For example, I can see communities/posts from @beehaw.org, where you are. I am subbed to a few communities there.
It's possible that a community like /c/games exists on @beehaw.org and on @lemmy.world. You would see them as games@beehaw.org and games@lemmy.world, and they are separate communities (despite having the same community name) so you can sub to one or both. OP is basically suggesting a feature to group (for example) games@beehaw.org and games@lemmy.world so that it just looks like one big community.
More experienced Lemmy and Fediversers, please correct any errors I may have made it this post!
Whatever y'all decide, please just remember what McLuhan said: "The medium is the message." What's the message implicit in your decision? Be deliberate.
Why not for local communities, you still display / require the local @instance name after the community name.
So /c/foo on Lemmy.world even when I am on that instance is still displayed as
Whereas if I search for or subscribe to βfooβ by itself it displays content from the βfooβ communities from all federated instances?
Some way to search other instances without knowing their name like that would be great.
Cross-Instance Automatic Multireddit feature within Lemmy.
Sounds great. It would be nice to see similar communities under a single heading.
I like multis and I think discoveribility is a bottleneck, but I'm very wary of this idea. If you merge communities together like this, you essentially multiply the users in that community. Moderation isn't 4 small instances anymore - it's one large one with 4 separate mod teams each handling a quarter of the posts
I think this is more likely to lead to polarization and eventually echo chambers than if you kept them separate - outrage drives engagement more than anything else, and explosive growth is a great way for a fraction of the group to dominate the first few pages of comments, which turns off moderate voices, which works like confirmation bias to make the outraged believe they're the prevailing voice of the community, which again drives them to post more incendiary comments, and the whole thing spirals
If you want to avoid echo chambers, the best way is to throw a small group together and make them get along through mods that are involved in the community
But then you'd probably end up with most members of one community slowly joining the rest, which is a healthier growth model, but still not great
My intuition is that the ideal solution involves encouraging users to join a single smaller group, but being exposed to top posts from sister groups to avoid fomo. Possibly through something like the way Reddit handled crossposts, where you get the post but not the comments, and a small link to the discussion in other communities. It could be automated if the post crossed a certain threshold of votes, keyed to a certain deviation above the daily average of the original group and optionally with a minimum up/down vote ratio.
This would help keep moderation ahead of participation, and hopefully build a tighter knit community - people are less willing to be jerks to people they recognize than strangers you get in a larger population. By encouraging users into one small random group instead of shopping around for the one that best fits their view, I think we could resist natural grouping by beliefs.
To go further, if this works we could consider a mechanism for "mitosis", a splitting of a group when the mod team feels the culture of the group is getting past their ability to manage in a nuanced way
The goal is decentralization after all, not distributed centralized groups
Make it user specific. Feeds are combined solely from the individual user's perspective. Consumption would be easier but submissions are still federated.
I don't see any problem. If the problem is the server admin is not able to moderate the communities, he can disable automatic community creation and define an approval process. He can also close dead communities, apoint moderators, merge proposals...
should understand lemmy.world is just a backwater refugee camp. fediverse is much more https://fediverse.observer/map this map needs an update https://fediverse.party/
How will this help the posters reach the fragmented communities? Will they just pray that everyone is using the the aggregator?
