4 ms·
I don't want people to read my drafts. That could be highly embarassing, and they should not make it into the final saved document. Past version and undo histo
by im3w1l 3y ago
I don't want people to read my drafts. That could be highly embarassing, and they should not make it into the final saved document.
Past version and undo history should be stored separately from the document. They should be stored out of tree where they wont be commited into some git repository or be automatically synced or anything like that.
- regularfry 3y agoI want to be able to read my drafts, until I decide to bake a publication version.
- im3w1l 3y agoDid you read the other part of my comment? Where I said to store the draft, but not in the document itself?
- regularfry 3y agoI did.
- eviks 3y agoThen don't give people access to your drafts but exported versions without history? Why put the limits on the efficiency of a format by forcing it to store changes elsewhere?
- pornel 3y agoIt's better if such gotchas don't exist. Otherwise you'll have every user get burned by it at least once, and blaming them for not knowing the subtle consequences of using "Save As" instead of "Export As" is not going to help anyone.
- eviks 3y agoThere are plenty of burns on the other side as well with users losing edits and the consequences of copying your file in a file manager with/without some out-of-tree-out-of-sight history are even more subtle. This is an app feature (it doesn't have to be "Export As", it can be a "clean history" toggle in the same "Save As" dialog and a separate command), so not a reason to excise efficient history preservation from the file format