Communities on different instances about the same topic should have the option to essentially federate so a post on one appears on all of them and opening any of them shows you the comments from all of them. This way when lemmy.world is down its not a big deal because posting to any news community federates to all of the communities instead of barely having people see your post. Federation could be decided by the community mods and the comments can have a little “/c/[email protected]” on it so you know which community the comment was originally posted on.

    • czech@kbin.social
      1·
      1 year ago

      require all participating communities to store ALL of the data.

      Wait, what? No, not at all. There is no reason for them to redundantly store all the data.

      Imagine the same concept but the data is just being aggregated. The purpose is that content gets more exposure and engagement not to create an archive.

        • czech@kbin.social
          0·
          1 year ago

          Is that so different than how the fediverse currently works? Subscribed content is already being federated across instances I’m just asking it to be organized together. When your instance federates with a community on another instance it doesn’t get the entire “5-year” backlog sent to it; only new posts and old content that someone interacts with is sent.

          I think there are limits to the scalability of the fediverse, in general, I just don’t see how organizing the data differently is breaking anything. Only the most limited servers are going to be impacted from receiving content from three /c/butterflies instead of one. Most people are probably subscribed to the duplicate communities already; I certainly am.