Gluing together feeds via some higher-level concept is a bit of a hack, if you ask me, but I guess in the current architecture, might be the best choice.

@dpc it's maybe worth mentioning that this architecture is not by accident. by having a linear history on one-feed-per-key, we can avoid entire schools of problems: consensus ( #against-consensus ), conflict resolution, dag/tree replication, and so on. the idea is that by starting with less we can create simple protocols that can provide a solid foundation for doing more. everything is trade-offs and this seems like the best option given what we currently know from the first few years of playing with this system. that being said, thanks for your alternative ideas, there's still much exploration to be done if you want to help experiment with some alternative protocols.