Fediverse

... Are you guys for real? Since when is Reddit this centralized heaven you describe? You have r/news and r/worldnews. You have r/funny, r/memes and r/funnymemes and probably dozens of others I don't even know about. NSFW subreddits are like on another level where every single NSFW category has like at very least 5 subreddits and people who post there crosspost constantly.

And every single other platform for commuities has the same situation - on Facebook you could have found groups NHL, NHL fans, NHL 4 life and like ten other NHL communities with duplicated names.

And yet when we come to Fediverse, the BIGGEST F*CKIN ISSUE of the entire platform is that there is [email protected] and [email protected]

I don't necessarily agree that competing communities is something bad, especially once a "lists" and "sharing lists" feature is implemented. It's only a matter of time.

I think I've mentioned this elsewhere, but a lot of these issues of structure I don't think need to be solved on content creator/admin side, but rather on the end user UI side. The fragmentation is good for the network as a whole, but as an end user, I want to group similar communities together into one. Let me bulk subscribe to cats, toebeans, kittens, etc. I'll do that action once. Then if one of those goes defunct, I won't really care. I also won't really care which community I'm posting to (except to ensure I'm following the rules), because ultimately most of the savvy users will be mass subscribed to topics as well.

This preserves control (I can opt out of toebeans if I don't like that community for some reason), while keeping the distributed nature. No one would truly 'own' the cat pics community as it would span across multiple instances and communities.

"The ideal format for a fediverse reddit-like would be a cross between twitter and reddit: a website where if you want to post about a cat, you make your post and tag it with the appropriate tags."

You just described Mastodon. Many instances stick to the default character limit which is still bigger than twitter but some instances don't have the limit or the limit is much much larger.

The issue with tags is who's going to moderate them.

The reddit model has an owner responsible for each community. Tags don't, and as such the moderation responsibility over everything falls on server administrators.

So I get the concern, but honestly I think in practice fragmented communities are fine. If anyone's old enough to remember Fidonet and WWIVNet, they worked great -- you had some "local" communities with a lot of duplication and fragmentation, but smaller so you could start to recognize people and have some semblance of a community, and then you had bigger networked communities that were more akin to Reddit forums. They were both good things to have; I don't think it's automatically bad to have many smaller forums that cover more or less the same topics on individual instances.

The tags thing sounds great too, of course -- it could be a good way to discover new communities or browse everything related to some topic if you decided you wanted to.

Reddit also had competing communities though like r/tech and r/technology or r/games and r/gaming

I think that we should try to not create the same community in different instances, instead of that we should look for that community in existing instances and join it. So far I've realized the short time I've been in Lemmy, you can cross post between different instances and the local instance will show you if a post is also published in another known instance.

For some reason I suck at long comments, they keep getting destroyed when I try to post.

I had a long written out response about how when you have multiple communities on one subject, moderation responsibilities get dispersed and become easier for everyone. They don't have to set up any division of responsibility on a single board, they don't even have to agree on the EXACT same rules. They simply have to federate and link each other so that the community members know to watch for threads from each, comment where they like, and post on the one that is closest to their instance.

If we throw away the idea of "Redundant" or "competing" boards and just accept that we can have all these spaces coexisting, things could work out pretty nice.

I mean, instead of ONE Sherlock Holmes board that might discourage sexuality discussions and ban BBC Sherlock, you can have 3 that have slightly different rules, different mods but still federate with each other and give you 3 spaces to discuss Sherlock Holmes that are all reachable from your homepage on your home instance.

I think what we are seeing now is the effect of being in the "land rush" phase of lemmy build out, and won't be the norm once things settle down. Really the biggest thing to improve things would be for admins to pre-federate common communities so that when new users search for them they are found, instead of getting "not found" then creating yet another duplicate of the same content.

Eventually people will coalesce around certain communities and bail from others, and that will likely morph over time. I've dropped my subs to all the beehaw communities due to their isolationism, and I suspect others will do the same. Some will like their walled garden, and that's fine - that's what makes the fediverse strong.

ex: [email protected] vs [email protected]

Isn't the point of federation that those communities would federate and then have merged comments sections? Or am I misunderstanding how it works?

I think a link-aggregator format is perfectly okay for the fediverse, I think redditors wanting to interact with it just like they do reddit is the problem. Communities don't have to compete, we don't all have to talk in the same place if we want to talk about a topic, and probably shouldn't. It's the reason splinter subreddits exist, and those actually aren't bad, they are just inherent to the natural course of communities. It's less convenient, but if everyone isn't happy and keeps fighting, they should go off and do their own thing. Having something in one big mega community means centralization, and the fediverse is decentralized. Aggregating all instance's tags into one community automatically, and then appointing a moderator of that mega-community means them having a say over how other instances run their own moderation. That's not how the fediverse does, or should, work. Fediverse gives you ultimate control over how things are run and which sites you want to talk to, should you run your own instance, and that's kinda it's whole thing.

You've been conditioned into thinking that centralized hubs are ideal. They have upsides, but also have major downsides. In the same way cities can be hellholes, frustrating, and expensive to live in. They're very convenient, and pretty necessary for business. But people don't have to be a part of a business ploy to have value, not everyone wants to or should live in a city. Different people have different needs, even if they like and want the same things.

aside: following tags on lemmy could be a perfectly fine feature, but no one person from fedi should moderate it, what's shown should follow all federation rules in place for your home instance. It's just like how you can search tags on mastodon and it populates from all federated instance of your home.

I've been brainstorming things like this, too, and have come up with some similar thoughts. I think we can have both tags and communities. Suppose there's a trust model. A community on an instance will entrust certain members to whitelist posts that are in an approved list of tags. Anything on any instance that gets tagged with one of the approved tags would go into a queue. You could employ a bot to work the queue to eliminate low hanging fruit, and then trusted community members would work it to approve posts.

Likewise, an instance community could have a trust relationship with a community on a different instance. They could say, "Any posts approved by the cats community over there are automatically approved here." This could help distribute the load on the queue. As a side note, there would need to be logging of metadata so an audit trail could be analyzed in case problems arose in the trust circle.

So, that addresses a way to handle submissions. There's another ball of wax with comments. Ideally, a comment section would be a way for users to discover new communities. You might be reading comments on a #cat submission and see a comment from someone in #toebeans and go, "Oh hey, that looks interesting," and you can jump to the community and/or subscribe to it. It's not immediately obvious to me how an app could aggregate comments across multiple communities or if ActivityPub could facilitate it. Seems plausible.

I really hope we eventually get a richer platform out of all this. It's a great opportunity for people to put their heads together and think of new improvements.

Partly in jest, but partly not:

Webrings, fam.

The old, glorious webrings of the 80s and 90s should return. That's what'd connect your various "cats" instances, without the need for any of them becoming the Official And Only "Cats" Community.

Other than that, I don't really like the idea that you describe that a generalist principle like "cats" should be "owned" by an automatic system. That's kinda yet another problem that we're trying to escape from (evenmore now with AIs). And made it worse when in order to participate in a "smaller" community which is still about cats, you have to "steal" another noun that describes a different community, such as "toebeans" (which could also be for eg.: furries).

The solution is to somehow merge all the communities into one list for the user based on keyword or something. That way it foesnt actually matter.

That doesn’t seem practical to me — for instance, who would make the rules and appoint moderators for auto-created communities?