I'm wondering if there's a value in having an rclone mounted a quasi read-only mode.
what I mean, is that it would refuse to open files for writing, as we know, trying to write to many backends in a random manner, just doesn't work well, but it would allow directory entry modifications (rename/mv and delete)
idea is that one can avoid misbehaved applications causing themselves problems by trying to write to the fs, but one could still manage the contents (move them around, rename them, delete them) from within the normal comfortable confines of a file system interface, while getting data onto the remote would be the job of using the rclone command line.
perhaps, still think it make more sense at the fuse layer, disable file creation and files can't be created. disable file open for write, files can't be written
I'm not sure why it would. At the most simplistic level, it be preventing creates and assigning directories rwx bits, but files only r bit. I guess apps can break, but they'd be pretty buggy.