Re: It's only a matter of time ...
@LDS, I mostly agree but still think snapshots can be used ...
My home ZFS box snapshots itself every minute, whilst another cronjob tidies snapshots periodically (keeping a few hours' worth of per-minute snaps, a few days' worth of 6-per-hour snaps ... etc., etc., ... down to quarterlies which are never auto-removed). None of the remote users are sudoers; root cannot log in remotely; so I think snapshots can only be removed from the console.
I have, very recently, deliberately infected a client machine attached to this storage, and sure enough it immediately started encrypting every file in its network attached folder (in fact, one of my monitoring scripts on the ZFS box mailed me to tell me that there was a huge peak in write activity). When it subsided, I successfully recovered all the test files from snapshots (although I cheated and just went for a the last snapshot before my deliberate infection: if I had not known the date of the infection and the files had been changing there'd have been a bit more work to do (I'm trying to work out a decent way of automating this).
One could create and market a NAS box which was "reasonably ransomware resistant" using a number of similar approaches.
"Backups should not be local" --- agreed, because of fires, theft, etc. I'm not remotely suggesting that snapshots replace backups. My box makes encrypted copies of my most important files and dribbles them up to Dropbox.
But it seems to me that there is no technical obstacle to "reasonably ransomware resistant" local storage.