Naively, literally logs/timeseries events (i.e. stuff that can literally be inserted and queried in order of their timestamp). This scenario can be made increa

Naively, literally logs/timeseries events (i.e. stuff that can literally be inserted and queried in order of their timestamp). This scenario can be made increasingly complex as you add user interaction, such as a settings JSON blob that you probably do want to intelligently sync. ---- In general, particularly for the timeseries case, I just want to know what the intended P2P flow looks like for different datatypes, including those that probably aren't managed by the CRDT algorithms. It seems like these systems beeline for the hard text case (which makes sense, because it's the interesting and challenging problem), but forget that in the real world, you need to sync more than just text.