![](https://media.kbin.social/media/74/06/7406481d0b57e911e6b83fbc68f8bdcccc51fe6ad896186f477719d10cd86f81.png)
![](https://lemmy.world/pictrs/image/eb9cfeb5-4eb5-4b1b-a75c-8d9e04c3f856.png)
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.
This is fantastic. I’ve been a $5 Kagi user for a few months and have been really enjoying it. The only issue has been that sometimes when I’m working on a project I need to blow through a ton of similar queries to find what I’m looking for; I’ve been forced to switch back to google for those. Now I’ve upgraded and am going full Kagi.