I made a honest effort, but in the end went back to Git for my personal projects. The advantages Fossil has over Git (wiki, bug tracker) are trivial to emulate with versioned plaintext files, and everything about Git’s version control system just clicks with my head. Having years of experience breaking and unbreaking things helps too.

Tho one thing Fossil taught me is to merge by default, not rebase. Rebase when there’s good justification for it, and the rest of the time, have an alias for git log --oneline --graph --first-parent (or whatever that was). --first-parent collapses a horrible branchy-mergy history into a linear overview thereof, with details available when needed.

Yeah, 4 is tricky socially and 8 is tricky anatomically. I touch it to something, as an alternative to holding it up.

Using binary with bent/straight fingers gets you up to 31. There are other ways - like touching your thumb to different phalanges of different fingers, for 0…12.

OP didn’t want to delete anything, but to compress them all, exploiting the fact they’re similar to gain efficiency.

Indeed! Interesting! I made an experiment now with a non-compressible file (strings < /dev/urandom | head -n something) and it shows you’re right. 2nd commit, where I added a tiny line to that file, increased repo size by almost the size of the whole file.

Thanks for this bit.

Highly unlikely to succeed. The tiny differences are spread out all over the image.

You could store one “average” image, and deltas on it. Like Git stores your previous version + a bunch of branches on top.

Cool idea. If this doesn’t exist, and it probably doesn’t, it sounds like a worthy project to get one’s MSc or perhaps even PhD.

192.168.0.00? 'Shopped.

So true. Sway forever.