3 ms·
Yeah, unless there's some automatic backup/snapshot implemented before any actions are taken, hard pass on this. Or at least I won't be using it on anything I'
by scottLobster 9mo ago
Yeah, unless there's some automatic backup/snapshot implemented before any actions are taken, hard pass on this. Or at least I won't be using it on anything I'm not willing to 100% lose. Maybe give it read-only access and have it put results in a designated output folder?
Particularly in a work environment, one misfire could destroy months or years of important information.
- bheadmaster 9mo agoIt's funny how easy Plan 9 would make all this. Just mount the work dir as readonly in Cowork's filesystem namespace and mount a write-only dir for output. We can still do this via containers, though. But it does have some friction.