this post was submitted on 16 Jun 2023
130 points (100.0% liked)

Technology

37747 readers
690 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

Perhaps I've misunderstood how Lemmy works, but from what I can tell Lemmy is resulting in fragmentation between communities. If I've got this wrong, or browsing Lemmy wrong, please correct me!

I'll try and explain this with an example comparison to Reddit.

As a reddit user I can go to /r/technology and see all posts from any user to the technology subreddit. I can interact with any posts and communicate with anyone on that subreddit.

In Lemmy, I understand that I can browse posts from other instances from Beehaw, for example I could check out /c/technology@slrpnk.net, /c/tech@lemmy.fmhy.ml, or many of the other technology communities from other instances, but I can't just open up /c/technology in Beehaw and have a single view across the technology community. There could be posts I'm interested in on the technology@slrpnk instance but I wouldn't know about it unless I specifically look at it, which adds up to a horrible experience of trying to see the latest tech news and conversation.

This adds up to a huge fragmentation across what was previously a single community.

Have I got this completely wrong?

Do you think this will change over time where one community on a specific instance will gain the market share and all others will evaporate away? And if it does, doesn't that just place us back in the reddit situation?

EDIT: commented a reply here: https://beehaw.org/comment/288898. Thanks for the discussion helping me understand what this is (and isnt!)

(page 4) 50 comments
sorted by: hot top controversial new old
[–] poudlardo@terefere.eu 1 points 1 year ago* (last edited 1 year ago)

You're right on that part. Federations works great with mastodon and its instances made of individuals directly interacting with each other's accounts.

But when it comes to interacting though communities already spread through instances, not only it makes it hard for people to follow all these duplicates, but it threatens the very principle of federation in a certain way. Because most people will eventually subscribe to the biggest community for each subject (tech, nature, photo), which often turns out to be hosted on the biggest instances...and that is centralization once again.

A solution could be for users to gather all the communities they subscribed to around topics. Then your feed would be a mix of these topics' groups and singles /c. Twitter does that similarly with its List feature.

[–] prorester@kbin.social 1 points 1 year ago

Once "multi-reddits" have been defined and implemented in kbin that shouldn't be an issue. I don't know what'll happen with lemmy, but it would probably be in its interest to implement it too.

[–] Kushan@beehaw.org 1 points 1 year ago (1 children)

The main goal of these sites is link aggregation. It wouldn't be overly difficult for a federated server with its own /c/Technology community to see other posts from other communities linking to the same thing and combining the discussions into a single view.

The tricky part there is moderation, but even that's manageable by allowing moderators to remove content from a federated view within their own instance, it'll just be difficult when a small instance is dwarfed by a larger one.

[–] sudoreboot@mander.xyz 2 points 1 year ago* (last edited 1 year ago)

I don't think of the threadiverse as a link aggregation platform but as a network of communities engaging in threaded discussion. The federated model is an answer to the problem of platform lock-in, the network effect, and the lack of autonomy communities have on proprietary/commercial/centralised platforms.

Each instance separately may fill the role of link aggregator but mainly for that community (instance), with that community's values and moderation policies. The ability for an instance to federate with other instances with compatible policies is the benefit here.

It may actually help if you view an instance as the community, with its "communities" as its topics.

[–] PascalSausage@beehaw.org 1 points 1 year ago* (last edited 1 year ago)

Fragmentation is certainly a problem if you’re looking for Reddit-style cohesive communities, how much of a problem it is remains to be seen in my opinion. The risk with trying to do things the Reddit way is that one or two large instances become dominant and you’ve just got Reddit all over again.

One potential solution that I’ve been turning over in my mind is the concept of “meta communities” - collections of smaller related communities across the fediverse that can be subscribed to and interacted with as if they were one, sort of like multi-Reddits. Users could potentially vote on a smaller community being admitted into the meta community, or there could be some other requirement. It could even be done locally/on a per user basis through a browser extension or their account on their home instance. It’s not perfect but it’s maybe something to explore.

Alternatively we just get used to more compact communities again. Let’s be honest - do we really have to know everything, all of the time?

load more comments
view more: ‹ prev next ›