There is a list of federated and blocked instances on the bottom of the page. https://latte.isnot.coffee/instances

Also this script is to see which instances block or are blocked by the instance you choose.

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.

The proposal does not necessarily imply merging all small communities with others. The implementation can provide an optional choice to community moderators, allowing them to decide whether they want their community to be included in the multireddit. This approach respects the autonomy of individual communities and acknowledges the reasons why new but similar communities may emerge, such as issues with community mods or server admins. By offering this flexibility, the feature can cater to the diverse needs and preferences of different communities while still providing the benefits of consolidating posts from communities with similar topics.

We are at 5k monthly active users. I find that stat more interesting.

https://lemmy.fediverse.observer/stats

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.

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.

I would prefer something pre-made for convenience but that can be modified by each user to adjust to their preference. I'd rather have a generalist solution forced on me than have to spend countless hours grouping communities from hundreds of instances.

Yeah, couldn't agree more.

https://browse.feddit.de/

Yeah you are right! I'm sure you can do better.

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.

Every moderator would have control only over the content displayed on their instances, and not on everyone else, as it should be. The argument about having one or two large communities is a recurring one. There is no reason to have federation if we are going to centralize communities in a couple of instances. Then, if one of those instances shuts down, everyone in those communities would have to migrate. The main benefit of federation is decentralization.

TL;DR:

Beehaw is a politically neutral community that does not tolerate hate speech. They defederate with instances that promote hate speech. Online political discussions are often toxic due to anonymity, while real-life discussions require more awareness. Beehaw advises being skeptical of individuals who focus on politics but lack understanding. They encourage considering incentives and disengaging from those who use anonymity to vent. Forking from the Lemmy platform is debated in a political context, but Beehaw does not see it as necessary at the moment. They prioritize server management and other tasks and haven't received a serious proposal for a fork.

Here are some of the monthly active user statistics for various social media platforms, according to the search results:

1. Facebook - 2.96 billion monthly active users (MAUs) [1]
2. YouTube - 2.56 billion MAUs[2]
3. WhatsApp - 2 billion MAUs[3]
4. Instagram - 2 billion MAUs[3][4]
5. WeChat - 1.26 billion MAUs[2]
6. TikTok - 1 billion MAUs[2]
7. Facebook Messenger - 988 million MAUs[2]
8. Snapchat - 557 million MAUs[2]
9. Pinterest - 444 million MAUs[2]
10. Twitter - 368 million MAUs[5]

It's worth noting that these numbers are subject to change and may vary depending on the source. Additionally, there are many other social media platforms with significant user bases that are not listed here. When choosing which social media platforms to use for your brand, it's important to consider the relevance to your target audience and the quality of engagement on each platform, rather than just the number of users.

Citations:

[1] https://buffer.com/library/social-media-sites/

[2] https://www.semrush.com/blog/most-popular-social-media-platforms/

[3] https://datareportal.com/social-media-users

[4] https://statusbrew.com/insights/social-media-statistics/

[5] https://en.wikipedia.org/wiki/List_of_social_platforms_with_at_least_100_million_active_users

By Perplexity at https://www.perplexity.ai/search/98165c01-5be7-41be-ba6c-fd77454d3b5a

Not taking it personally.

I would also appreciate the ability to customize, but it would be helpful to begin with a curated list of instances for each topic.

https://lemmynsfw.com/post/543

I agree with what I just read. It should just be an instance setting and let admins choose. Mastodon can't outcompete Twitter without an algorithm to easily find things you find interesting, and Lemmy probably won't be able to outcompete Reddit without karma.

This is one of the features that made social media successful. Without the reward-dopamin loop, people have less incentive to generate quality content. Publicly showing karma is another thing. While it's nice to be able to hide it, it's one method of judging a user on reddit. In combination with other methods, it's easier to spot trolls.

What's wrong with "karma farming"? Disabling it, obviously doesn't prevent spam/propaganda/bad quality content. Also, reposting is important for people new to the platform. (Who didn't laugh at a joke on reddit which everybody seems to already know about?)

I think improving moderation methods would be way better to counter low quality content than radically concealing information that's already there for the one in control of the instance.

— heeplr

wrong place

I don't know why you are bitching about rules and frustration.

I believe the best approach would be to have these multireddits automatically created for convenience. However, users should have the option to choose whether they want to see only the content from their instance's community or from any number of communities, instead of being forced to view all of them.

Lol this is a very good point. I'll give it some thought.

Oh, I thought it was about tagging the communities and merging them based on those tags. Are you suggesting tagging the posts instead, and displaying all posts tagged the same from all communities across all federated instances in the same location?

But this can already be accomplished with the search feature. You only need to select 'Local' or 'All' and search for a word. People shouldn't be forced to hashtag every post, so the result would be the same as it is now.

I think conflicts can arise with hashtags just as easily as with community names, so it might be better to have an updatable and moderatable link instead.

There could be conflicts between hashtags, as a hashtag for one community may not have the same meaning for another community. This would result in mixing topics and potential confusion.

Why don't you read the issue? It's in lemmy-ui, so it's clearly client-side. So just because you want to waste your time going through hundreds of instances to find similar communities, do we have to force everyone else to do the same?