this post was submitted on 13 Jul 2023
23 points (100.0% liked)
/kbin meta
25 readers
1 users here now
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
founded 2 years ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Take it easy. Kbin is only a few months old, and the developer works on this in their spare time.
There are lots of optimizations to make.
It's a hard problem though - those are three different communities on tree different instances after all. The topic is "valid" for each of them and the local population of the instance, so it's not like the servers can refuse the submission.
Doing filtering on the client would maybe be an option, but how would the client know which one of those three communities is the "main" and which other two should be filtered away.
The easiest would be to unsubscribe from two of them. Or even better, if people could stop cross-posting.
But we know people aren't going to stop.
Except cross-posting has a purpose. In that example, one of the posts was to beehaw while another was to lemmy.world. Beehaw defederated from lemmy.world so users on beehaw are only going to potentially see two of the three cross-posted posts. If they also defederate from lemmy.ml, those users would only see one.
So yeah, the solution is to unsubscribe from two of those communities because they're essentially 3 completely different groups that just happen to have the same name and general focus. Either that or just get used to it.