You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently new folders have no vfs support enabled unless it's explicitly switched on during folder creation. That means one needs to edit the config file to enable it later.
New folders should default to the best availabe vfs mode, but with the root folder starting out "available locally". Or Vfs::Off should migrate to the best available vfs mode once the first item is unpinned by the user?
New folders start out with the best available vfs mode and the root as AvailableLocally by default.
The wizard vfs setting just changes the root folder pin state to OnlineOnly instead.
If any vfs mode is enabled (independent of pin state), selective sync is disabled.
Old accounts without vfs enabled continue like that by default.
Old accounts with suffix-vfs enabled are attempted to be migrated to better-vfs and stay suffix-vfs if it doesn't work.
There's an option to switch on vfs for existing accounts where it's disabled.
There probably should be an option to switch between vfs modes, in particular to off, so users can use selective sync again. Even though we might want to gradually deprecate selective sync.
The wizard "choose what to sync" option sets up vfs pin states if vfs is available, not selective sync.
Speaking about selective sync: It'd make sense if features such as "don't automatically sync external storages" or "don't automatically sync folders with >100MB of contents" were available in the vfs world too.
I don't think the remaining 1,2,8 should be done while vfs is considered experimental. That means the remainder of this ticket (new ticket?) should move to 2.7. @michaelstingl
Currently new folders have no vfs support enabled unless it's explicitly switched on during folder creation. That means one needs to edit the config file to enable it later.
@michaelstingl fyi
The text was updated successfully, but these errors were encountered: