• Cowbee [he/they]@lemmy.ml
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    7 hours ago

    It helps to see communities as categories for an instance, each instance will have a different response to the same post based on the general instance vibe and culture. That’s also why picking a good instance to browse locally can be pretty useful.

    • Kane@femboys.biz
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 hours ago

      I like that view, and it made me think of a possible “implementation”/“fix” as well:

      1. Combine the post somehow (Based on attachment/title/something else?)
      2. Filter/categorize the comments by instance that the comment was originally posted towards (Not by user, as that would be awful)

      The largest issue here that I can see, how do we treat “new” comments to a post?

      My annoyance is primarily with the fact that I see the same image 3x in a row, on a fairly regular basis. I might unsub from a few communities that share the same content.

      • Cowbee [he/they]@lemmy.ml
        link
        fedilink
        English
        arrow-up
        3
        ·
        7 hours ago

        There are many different workarounds, I personally don’t put much stock into sorting by “all” generally, sorting locally tends to be a better experience and has less repetition.

        • Kane@femboys.biz
          link
          fedilink
          English
          arrow-up
          2
          ·
          7 hours ago

          Sounds like a good solution for people who are on larger instances, my instance does not host any communities sadly.

          • Cowbee [he/they]@lemmy.ml
            link
            fedilink
            English
            arrow-up
            2
            ·
            7 hours ago

            You can pseudo-curate by only subscribing to your most prefered instance of comm, but you won’t be able to see instances with allow-lists as the basis, rather than block-lists.