• threelonmusketeers@sh.itjust.worksM
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 day ago

    That was addressed in the article under Proposal 2:

    it’s a feature not many people made use of, and it sounds like a pain to have to constantly create and manage new multi-communities to group together duplicate communities. This shouldn’t be a task that users have to manually do.

    • GorGor@startrek.website
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 day ago

      Personally I think proposal 2 and 3 should happen concurrently. Using the example in the post I would setup a custom feed (that can hopefully consolidate cross posts) for breakfast. I would put [email protected] which subscribes to [email protected] I can also add [email protected] and [email protected]. so when someone posts about the best homemade peanut butter syrup recipe that is cross posted to my pancake and waffle communities, I don’t get 4 posts about it, I can see it once and choose where to reply (pancakes obviously, I’m a waffle purist).

      Community interlinking/subscription fixes a slightly different problem than custom feeds IMO. It’s a really good idea, but I would personally still want custom feeds (with the ability to handle crossposts in a customizable way).

    • small44@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 day ago

      It shouldn’t be difficult to group some community automatically then users can edit it if they want

      • threelonmusketeers@sh.itjust.worksM
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        1 day ago

        How would automatic grouping work?

        Even if the communities are grouped, a given post or comment would still show up in only one community, and people not using the grouped view wouldn’t see it. Proposal 3 would solve that issue.