We lost few subfolders (>700files) that we can't find in "Deleted files" which is terrible experience for us, and we will reconsider our usage of Nextcloud (I plan to open another topic for that). We recovered from backup.
Files are in another folder, moved by random_user_03, thus not in trash.
Files were deleted, and trash emptied by malicious_user_06.
What I'm afraid of is:
Option 3. - Some bug in Nextcloud that deleted our files or lost track of files that users accidentaly moved...
Nothing would delete something a user moved.
As for lost track? That is easy there are CLI commands to rescan files.
Never had to use it because of user error before. Only because I was administratively changing things.
Because it does at least skip the ones with no changes.
Why get convoluted with Powershell to do the same?
Not every system may have Robocopy.
it became part of theOS with Windows Vista. So anything running Windows Vista or Higher will have robocopy as a part of the Operating system (as everyone should be using higher than vista at this point.. I mean.. windows 7 is obsolete now.. sooo..)
Windows 10 1709 is obsolete too, so really anything not with a support mechanism shouldn't be used. But @JaredBusch might be getting paid stupid amounts of money to support Windows XP / Server 2000
Bottom line, in NextCloud you shouldn't be looking at the files from the command line, ever. Not NextCloud files anyway. Permissions are meant to be handled by the app and it's database, not by the filesystem.
Well mostly. Nextcloud needs the files to have the right system permissions.
But user permissions have nothing to do with system permissions.
Also, for a few specific instances, I do quite a bit with Nextcloud files on the command line. But that is a very specific use case, and also has nothing to do with group or share permissions.