Commits can be created very often (e.g. in documents), and that's great for things like live synchronization. However, it also has some downsides:
- It can take up a lot of space
- It can make navigating history awkward.
Perhaps we should have a way to combining / merging / trimming commits. This essentially means changing the history, in a way.
I'm not quite sure where this should happen. I think it should probably be a feature of atomic-server, but it also has spec implications.
So perhaps we have a /shorten-commits endpoint, which gets a Subject and some options (max count of commits, or max time gap).
It then iterates over all commits, builds new commits and signs these server side, once every N commits (depending on date delta).
Commits can be created very often (e.g. in documents), and that's great for things like live synchronization. However, it also has some downsides:
Perhaps we should have a way to combining / merging / trimming commits. This essentially means changing the history, in a way.
I'm not quite sure where this should happen. I think it should probably be a feature of atomic-server, but it also has spec implications.
So perhaps we have a
/shorten-commitsendpoint, which gets a Subject and some options (max count of commits, or max time gap).It then iterates over all commits, builds new commits and signs these server side, once every N commits (depending on date delta).