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!)

  • InfiniteLoop@lemm.eeEnglish
    2·
    2 years ago

    This is the best solution I’ve come up with, but it’s going to result in a lot of duplicate posts (and the comments will still be fragmented). I’m following several technology communities and a lot of the posts are posted to each of these communities individually. This has always been my concern with federation (along with server health/durability)

    It’s not the worst result, but I don’t know how well it will be received by more mainstream users. You also then have to solve discoverability of these “groups/metas”, and THAT has to be hosted on a federated instance so you could still end up with users confused on whether they should follow beehaws tech group or someone else’s….and round and round we go lol

    (Just to be clear - I’m not against federation, it’s just such a starkly different model than the normal web that we really have to adjust our mindset and find truly novel solutions or adjust our expectations)