Sure, but I'd like a filesystem/os where that's not possible; where I have the control to prevent such an activity. I have music, videos, and photos which shou

Sure, but I'd like a filesystem/os where that's not possible; where I have the control to prevent such an activity. I have music, videos, and photos which should hardly every change. So it would be good to be able to make those read only, and in the rare event I want to tweak the photos, or edit the mp3 tags, I'd allow, say, one change per file in the next n mins. I'd like there to be an original version of each file which is never deleted, so i'd have version 1,2,3,4,5 normally, and if something tries to trash it then i'd have version 1,203,204,205,206 where something has tried (but failed) to overwrite the original one by changing it 200 times or whatever. I'm not saying that the answer is to use an existing versioned os; I'm saying that filesystems/oses need to keep up with the demands users are making on this. Ransomware is a newer problem than viruses, users deleting files by mistake and power failure during writes; it's going to need a bit of thought and development to solve, but it seems obvious to me that this is solvable, and it should be easier to solve than, say, spam or ddos because it's somewhere where the OS should have complete control over what's being stored. At some point, the ransomware is attempting to remove the current version of something, and it's not beyond the wit of man to detect and prevent this.