We're reaching the end of an era wherein billions of dollars of investor money was shovelled into tech startups to build large user-bases, and now those companies (now monoliths) are beginning to constrict their user-bases and squeeze for every single penny they can possibly extract. Fair or not.
Now more than ever, it's important for us to step back and reconsider whether we want to be billboards for these companies anymore.
For anyone unfamiliar, some good resources to have when starting your degoogling journey are below:
Privacy Guides - A list of privacy-respecting services you can use.
Plexus - A crowdsourced information bank of service compatibility with degoogled devices.
This random PDF - A study from 2018 detailing data that Google tracks about its' users.
Hah, that's a fair question! We use syncthing in place of cloud storage.
We have several 1-way and 2-way shares configured across about 10 devices. Our camera rolls are synced to the home file server while we're on the road, thus eliminating the need for Google Photos. It also keeps our shared KeePass database in sync between all clients, syncs wallpapers across desktops, etc. It's excellent software and I really can't say enough good things about the project.
It's no replacement for actual backups, which I do perform monthly with copies stored off-site, but it can be a great solution for those wanting to move away from Google Drive, Dropbox, etc.
Ahh okay thanks for the explanation. The way you use it seems alot easier and concise than what I thought you used it as, specially the central home server part. Have you experienced any corruptions or loss of data using your method? That's the main concern I have with programs that sync, like syncthing.
We've been using it across many devices for several years now and haven't had any data loss or corruption. It handles 2-way conflicts very well, creating duplicate files that allow you to compare and merge when necessary.
This has only happened with our KeePass database, which is shared across all of the devices, and even then it was only when two of us modified the db within just a few minutes of each other (rare).
Wow, surprising really, might just have to try it and set it up tomorrow! Thank you, hope it works out for me lol.
No problem! Just a couple of tips...
It will create a default share upon installation; you can just delete this and create a new share for whatever/wherever you actually want it to be
Don't try to nest your shares (e.g. don't create a share in a subfolder of another share). I think Syncthing prevents this now, but in the past it would let you do it and it caused issues due to recursion.
Try to think about a logical structure of your shares that will make the most sense for your use case. If you're only syncing one folder, this won't be an issue, but if you have lots of clients with various shares, you'll need to consider how those folders are structured on the devices so that they don't overlap.
If you have any questions, feel free to shoot me a msg or post to one of the selfhosted communities. Good luck!