[Discussion] I don't think this format makes a lot of sense for the fediverse

DudePluto@lemmy.world to Fediverse@lemmy.world – 15 points –

A lot of us come from reddit, so we're naturally inclined to want a reddit-like platform. However, it occurred to me that the reddit format makes little sense for the fediverse.

Centralized, reddit-like communities where users seek out communities and post directly to them made sense for a centralized service like reddit. But when we apply that model to lemmy or kbin, we end up with an unnecessary number of competing communities. (ex: fediverse@lemmy.world vs fediverse@lemmy.ml) Aside from the issues of federation (what happens when one instance defederates and the community has to start over?) this means that if one wants to post across communities on instances, they have to crosspost multiple times.

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. This could include "cats," "aww," and "cute." This post is automatically aggregated into instantly-generated "cats," "aww," and "cute" communities. Edit: And if you want to participate in a small community you can use smaller, less popular tags such as "toebeans" or something like that. This wouldn't lead to any more or less small communities than the current system. /EndEdit. But, unlike twitter, you can interact with each post just like reddit: upvotes, downvotes, nested comments - and appointed community moderators can untag a post if it's off-topic or doesn't follow the rules of the tag-communities.

The reason this would work better is that instead of relying on users to create centralized communities that they then have to post into, working against the federated format, this works with it. It aggregates every instance into one community automatically. Also, when an instance decides to defederate, the tag-community remains. The existing posts simply disappear while the others remain.

Thoughts? Does this already exist? lol

Edit: Seeing a lot of comments about how having multiple communities for one topic isn't necessarily bad, and I agree, it's not. But, the real issue is not that, it's that the current format is working against the medium. We're formatting this part of the fediverse like reddit, which is centralized, when we shouldn't. And the goal of this federation (in my understanding) is to 1. decentralize, and 2. aggregate. The current format will eventually work against #1, and it's relying on users to do #2.

70

You are viewing a single comment

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.

Communities with similar goals across the fediverse need to be grouped somehow. Any community called "cats@what.any" should be linked to allow for subscribing en masse. Perhaps "topic buckets" could work, where you can either subscribe to an individual community or a "topic bucket" that includes all communities across the fediverse that are called "cats@" or "technology@" or whatever.

While groups (meta-communities) could be useful, it shouldn't be based on named.

Python@programming.dev and Python@Zoologists.social are likely unrelated communities. Similarly LaTeX@programming.dev and latex@example.nsfw

But, also, hopefully there is a reason for the various similarly-named communities. Different moderation philosophies and rules would be expected. Cats@Midwest.local might be focusing on local cats and Cats@WorldFederation.zoo might be focusing on feral populations while Cats@Lemmy.world is about cute cat pics and memes.

This feels like a feature, not a bug, so I actually think we just need good "sidebar" descriptions that help direct traffic as things grow. Just like r/Trees and r/MarijuanaEnthusiasts helped folks find their place.

Someone else kinda brought up the idea of just adding topic tags to posts, that way the good parts of the current system will remain in place, but users can also browse by topics. Maybe that's a solution?