As i read in forum , lot of people have problem when syncing from linux to windows because of some characters that exist on linux filenames but cant be used for filenames in windows.
Let me get an example:
i try to sync my mail server (which is created with dovecot,postfix) to my local pc HDD.
the problem is because files are automatically named like this xxxxx:xx:xx and in windows this file cant be created,
To fix this problem you just need to add a function to replace certain characters example we can set to replace ":" with "_" or any other character we want.
so this file xxxxx:xx:xx in windows will be xxxxx_xx_xx and if we want to send it back to server we can replace _ with :
i think is simple function which will fix a problem that is torturing users which sync between linux and windows
we dont always chose to name linux files with characters that are not supported on windows. sometimes its not on our power to change them, they are generated like that by some complex scripts/software.
so i read on those articles that you care about duplicate file. If you can add that option it will be an advanced option and just users that really know what they are doing will use it.
also Why is so hard to implement it when u see that lot of users are having this problem and are asking for this again and again
This software is great but you need to listen users what they suggest, coz its a problem with lot of softwares and if you want FFS to be the best must add functions that other software dont have
I would argue that it isn't and shouldn't be the job of FFS to fix the lack of cross-platform support of other developers and their software. The more things you add, the higher the chance of bugs. In a data sync program, that can mean possibly deleting very important data.
but FFS is software for sync and this function is needed, on other software developers dont need to change filename because that software is planed to run only on linux. Butt since FFS added SSH ftp and other options that allow users to sync from different OS it should add this option and user can use on theyr own risk
