Lemmy federates with Kbin, so yeah, it can access the same content for sure. I just mean that, given the length of time Lemmy has been around, there was an existing community of regulars who were already posting heavily on Lemmy servers by the time Kbin started taking off. But yeah, thanks to federation, it doesn’t really matter where the content is originally shared as long as Lemmy and Kbin can both access it.
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).
Right but Kbin doesn’t defederate with many if anyone right now. You can also block entire instances as an individual user so defederation is less important in Kbin.
Are you talking about Lemmy for that testing? On Kbin I regularly see communities with no Kbin users subbed, just a large amount of upvotes. The algorithm for “hot” content on the all feed works much better on Kbin right now. Subbing to an any community is easy on Kbin. You just open it via a link and tap the menu to bring up controls for the magazine/community.
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?
Lemmy federates with Kbin, so yeah, it can access the same content for sure. I just mean that, given the length of time Lemmy has been around, there was an existing community of regulars who were already posting heavily on Lemmy servers by the time Kbin started taking off. But yeah, thanks to federation, it doesn’t really matter where the content is originally shared as long as Lemmy and Kbin can both access it.
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).
Right but Kbin doesn’t defederate with many if anyone right now. You can also block entire instances as an individual user so defederation is less important in Kbin.
Are you talking about Lemmy for that testing? On Kbin I regularly see communities with no Kbin users subbed, just a large amount of upvotes. The algorithm for “hot” content on the all feed works much better on Kbin right now. Subbing to an any community is easy on Kbin. You just open it via a link and tap the menu to bring up controls for the magazine/community.