I started shortly after Dropbox deprecated BTRFS and told me to move to a "better" FS like FAT.

After the initial setup, which wasn't that hard after all, but took more effort than doing nothing and continue on Dropbox I was amazed. My setup became better as now my phone is a real client that syncs files, not just a file browser that can "star" and cache some files, and there's more granularity on what's shared.

Funnily enough, the Android app not being (or not having the option) to be a browser and cache is one of the things holding me back from wholeheartedly embracing Syncthing. Different needs for different users.

I'm aware of https://github.com/syncthing/syncthing-lite but the consensus seems to be it is not quite there yet. I should perhaps give it another go.

This is why I run both Syncthing and Nextcloud. As you say, different needs.

What's wrong with the android 'app'? It works fine and besides initial setup I have openned it like maybe 3(?) times in the 3 years I have used it.

For those who don't know (including me) could you explain what you mean by deprecating BTRFS? I don't understand how the file system is relevant to a file syncing app like Dropbox.

Neither does.. well anyone. Dropbox decided to drop support for BTRFS and pretty much any other Linux file system that isn't ext4, and to my knowledge still hasn't explained their rationale to this day.

See: https://www.dropboxforum.com/t5/Error-messages/Dropbox-clien...

Sharing the reason is either a legal risk, or a loss of competitive advantage risk (some optimization that only works when their whole pool is in particular format).

As of last November, Dropbox only supports ext4 on Linux, NFTS on Windows, and HFS+/APFS on Mac. Couldn't tell you the technical reasons for the change, but they're listed here:

https://www.dropbox.com/help/desktop-web/system-requirements...