No, I meant "most changed". I don't see how this could be better for a deterministic approach. The recommendations are always that the developer must implement

No, I meant "most changed". I don't see how this could be better for a deterministic approach. The recommendations are always that the developer must implement a saner way to resolve the conflicts. In the CouchDB world, however, I have the impression that conflict resolution is ignored most of times, so we are left with this. (I say this based on what I do, other people's code I read on the internet and the concerns of the CouchDB core developers about educating users and developers to setup saner conflict resolution approaches themselves.)