/kbin meta

2 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 1 year ago

Is there a way to deal with crap like this yet? (media.kbin.social)

submitted 1 year ago by Eggyhead@kbin.social to c/kbinMeta@kbin.social

60 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] 0xtero@kbin.social 14 points 1 year ago (4 children)

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.

[–] Ferk@kbin.social 5 points 1 year ago* (last edited 1 year ago)

would the client know which one of those three communities is the "main" and which other two should be filtered away.

Imho, it should not "filter away" any of the entries. But rather merge all in the same "meta-post" (or whichever term is chosen). Show those posts a bit differently by aggregating the authors (with a clickable "..." ellipsis if the list is too long but that allows to show them if wanted), and when viewing the content either aggregate the comment threads or maybe add tabs to alternate between instances.

[–] Eggyhead@kbin.social 5 points 1 year ago (1 children)

The easiest would be to unsubscribe from two of them.

I think this is kind of unfair.

how would the client know which one of those three communities is the "main" and which other two should be filtered away.

Probably the local-most iteration followed by the time of posting/federating.

[–] density@kbin.social 1 points 1 year ago

OP asked a question:

Is there a way to deal with crap like this yet?

Answer: unsubscribe from 2 of the >3 substantially similar communities.

OP is that every bakery is selling bread.

[–] Lodespawn@kbin.social 5 points 1 year ago

Maybe instead of filtering the client could do a merge and list the comment trees under one header grouped by the community/magazine they are posted to?

[–] trynn@kbin.social 5 points 1 year ago

The easiest would be to unsubscribe from two of them. Or even better, if people could stop cross-posting.

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.