Jarred Sumner

i wonder if there’s a variant of overlayfs upper filesystems that keeps every change, never deletes and has an easy way to go back/restore/fork

if content addressible it probably wouldn’t be too crazy in space usage. just very slow. at worst maybe you have a TTL of days/weeks

you probably would want this to respect .gitignore. you probably wouldn’t want to run this on your whole filesystem, just your code folder.

can’t you use a hook that reads the git reset or rm command?

why this would be cool:

model can do dumb stuff and run commands that themselves do dumb stuff you don’t have to care. you can always go back. even if the files changed are not observable through the CLI directly (like if it runs code or commands that deletes files)

if you do it in zig and be clever about metadata storage by copying tricks used by other copy on write stuff and initially implement as a fuse filesystem performance would probably be fine. I imagine metadata is probably more expensive than content because text is small

application-level sandboxing isn’t robust to changes outside the application