I feel like Lemmy has more content, probably because it’s been around longer, so it’s a good base to build from.
I’m also giving an answer to the other thread on Kbin, since I think there are good reasons to use that one as well. They’re both solid, and I’m using both regularly–often viewing posts from one service on the other. For me, it’s “yes AND,” not “no BUT.”
It should be pretty similar, with the notable exception of defederation. Eg, beehaw users will see a lot less content because they blocked a very large number of instances, including some of the biggest ones.
I think that bigger instances will also see more on /all, which I think is a massive flaw and usability issue. I’ve been experimenting today and it seems that you need someone on your instance subbed to a community for it to… Well, basically be usable to any degree whatsoever. Both kbin and Lemmy have absolutely horrible UX for communities on other instances that nobody on your instance have subbed to yet. I can’t stress enough how truly terrible the UX is. The community won’t show up in /all until subbed to, yet figuring out how to sub to it is hilariously difficult (seriously, go try it).
So basically, you want the biggest instance you can find. Small instances should be avoided until this is improved (unless you don’t care about /all or ease of subscribing to new communities, I guess).
I feel like Lemmy has more content, probably because it’s been around longer, so it’s a good base to build from.
I’m also giving an answer to the other thread on Kbin, since I think there are good reasons to use that one as well. They’re both solid, and I’m using both regularly–often viewing posts from one service on the other. For me, it’s “yes AND,” not “no BUT.”
Genuine question here, how can Lemmy have more content if it’s all federated? Wouldn’t Kbin, despite being much younger, have all the same content?
It should be pretty similar, with the notable exception of defederation. Eg, beehaw users will see a lot less content because they blocked a very large number of instances, including some of the biggest ones.
I think that bigger instances will also see more on /all, which I think is a massive flaw and usability issue. I’ve been experimenting today and it seems that you need someone on your instance subbed to a community for it to… Well, basically be usable to any degree whatsoever. Both kbin and Lemmy have absolutely horrible UX for communities on other instances that nobody on your instance have subbed to yet. I can’t stress enough how truly terrible the UX is. The community won’t show up in /all until subbed to, yet figuring out how to sub to it is hilariously difficult (seriously, go try it).
So basically, you want the biggest instance you can find. Small instances should be avoided until this is improved (unless you don’t care about /all or ease of subscribing to new communities, I guess).