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!)
We’ve had Usenet, Forum, IIM, MySpace, Facebook, Reddit, etc. etc. They’ve all kind of started out fragmented but over time people naturally built up their communities and figured out what worked.
Kbin and Lemmy aren’t that much different from Usenet or Forums, its just the terminology that is messing people up.
On Usenet communities ended up getting split up because people just really liked to spin off sub groups so you start with comp.technology, then comp.technology.linux, comp.technology.linux.ubuntu etc etc etc.
Forums were always fragmented communities. I have ForumA with these threads and ForumB with these threads, ForumB will never see the posts from ForumA unless they go to that website to see them (and vice versa).
In the Fediverse, sure communities might end up fragmented because each instance has a @technology BUT the benefit is I am on InstanceA and you are on InstanceB and as long as we are federated you can see all of the content from my instance and i can see all the content from yours.
Now, that all being said… One feature I am pushing for to get added to kbin is something along the lines of a multi-subreddit. That way you can set up @technology_@_lemmy.world @technology_@_beehaw.org @technology_@_kbin.social etc to be in this multi-subreddit so as a user you will only see posts from @technology Users don’t want to mess with 50 different tech communities but if we had a multi-subreddit feature that blends them all together so it only appeared as @technology I think it would win a lot more people over.
I spun up my own kbin instance so I can hopefully start helping with the development of features (and to lessen the load for other instances). The two features I’m hankering for at the moment are API support so I can write some content aggregator bots and the multi-subbredit feature.
Anyways that is my rant? tedtalk™? Idk, hopefully all of that made sense to someone out there.
How would posting with multi-subreddit work? Would it post copies to everything? Or would you still just post to one of them?
Posting would work just as it works now, the difference is how easy you can view the different communities. The idea is that it’s just like if you were for example just subscribed to different tech communities from other instances. Now you can switch your view to subscribed to only see all those tech threads.
The problem is when you are subscribed to more than just those tech communities, you can’t filter your view so that you still only have those tech communities on your page.
Multi-subreddits would do just that. You could group different communities together and view them as you view your subscribed list, only now you can have multiple of those lists with different communities in them