• 0xtero@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    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
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      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.