Use case or problem
Currently, we only notify users that their vault is located in a third-party syncing folder after the remote vault has been set up. It could be more intuitive to alert users to this before setup and offer them an option to move their vault out of the third-party syncing folder as part of the remote vault creation process.
This would help prevent potential conflicts with syncing services from the start and streamline the experience for users who may not be aware of the implications of keeping their vault in a third-party folder.
Proposed solution
Adjust it so that as a part of setting up a remote vault, we help automate the moving of the vault to a more ideal location.
Current workaround (optional)
Hopefully, educating users on the front end of the potential dangers of third party syncing on top of using Obsidian Sync.