Working with remote files in LibreOffice is a main feature which supports collaborative work for users and institutions. However there is no default features or options that protect against failures in LO or the internet connection, which can cause data loss. The proposal that I suggest is this: Autosave: LibreOffice should have own options for remote file storage. Autosave time should be around 5 minutes or take an autosave algorithm during idle times (similar to how it works in the cloud). Backup: In case of loss of connection, I could save the file locally and then ask the user if they want to update their work in the cloud. Cheers
Non-local files might be accessed by more than one user. Auto-save makes sense only when you update all parties (like etherpad or gdocs), otherwise it will end in a big mess. Of course it's the same issue in case of manual saving. But you can easily check if changes were made (just like mid-air collisions in the bugtracker) and ask for confirmation.
We're replacing our use of the 'ux-advise' component with keyword 'needsUXEval': Component -> LibreOffice [NinjaEdit]
Decision is up to the devs if such a feature can be implemented reasonably. Removing needsUX.
I think that this topic is significant. You did a great job of talking about backups. I want to add one thing to this topic. I want to tell you why you should backup your Office 365 with the help of https://spinbackup.com/blog/should-you-backup-office-365/ and not other services. This service will allow you to do scheduled backups of your data. You will always know what's happening with it.
We do have a UserAutoSave (although the UI was hidden in LO 5.0 - see bug 65509). Does it actually not work for remote files? (I expect it would work) We also have an AutoSave (which saves to the local backup folder). We also have an backup option (which saves to the local backup folder). So, I'm wondering what is actually actionable in this bug report.
(In reply to Justin L from comment #5) > We also have an AutoSave (which saves to the local backup folder). This is better referred to as timed autoRecovery (fixed in 24.2) > So, I'm wondering what is actually actionable in this bug report. I think I'll mark this as a duplicate of bug 98576 - which requests detection and actions when working with remote files. *** This bug has been marked as a duplicate of bug 98576 ***