I'm not sure if this is a joke or if you just didn't read the article. If it's the latter, the article mentions 4 distributions it works on, as well as the code in the kernel driver that causes it, so yes, we're sure.
Personally, I prefer manual sync like Burcu does. You have way better control with manual sync, imagine you were editing a video or had source code in your drive that was shared, any saves would toggle syncing. Also you could potentially clog up your bandwidth with auto syncing. Plus I can get to review a manifest of files before letting them get pushed. Lots of other features with manual sync such as `cat pipe | drive push --piped streamedContent` or `drive push -m ~/contentNotInDrive .` and many others. These would be very difficult to get in with auto-sync.
So before the usage of golang.org/x/text/collate this was causing this problem. However, I got rid of it with PR https://github.com/odeke-em/drive/pull/331. That comment is a legacy one.
