Everybody makes mistakes and nothing in the world is black and white.
The only question is, is your cloud provider less likely to make mistakes with your data than you are?
For most people, the answer is going to be orders of magnitude less likely.
The only question is, is your cloud provider less likely to make mistakes with your data than you are?
For most people, the answer is going to be orders of magnitude less likely.
No, the second question, which is a multiplier of the first, is how catastrophic the mistakes can be. Google _can_ accidentally do much worse things with your data, but it probably much less likely to make mistakes with it in the first place.
If the cloud provider screws up, then the worst case is that my video goes viral and lives on the internet forever.
It isn't hard to imagine some troll finding he got some embarrassing video via takeout and putting it up on reddit for everyone to see.
So this is not a differentiator between storing your own data in the cloud and locally.
Most people don’t want to lose their stuff because they forget a password. That’s why unencrypted data and password resets are a thing.
What we as tech people should be doing is educating and helping those people. Set your family up with a NAS for local backup and have it mirror to, say, Backblaze. Set your parents/grandparents up with a password manager. Etc.
- If you share something, you need a way to share the key
- Things like a truecrypt drive work poorly with file sync clients
I'm trying hard to invalidate this with PhotoStructure. My goal is to be installable and usable by even my least-computer-savvy family members.
Although there are desktop installers, users can move their library to a NAS, rPI, oDroid, NUC or a VM in the cloud--anything that can host 64-bit docker images--but only if they want to. Everything in your library works cross-platform because I didn't want to be tied down to any OS or hardware.
PS: There's an image that can't be loaded on the confirmation page when registering for email updates.
PhotoStructure imports files that are available to the device that it runs on: local files and anything mounted via a network filesystem (like AFS, NFS, or SMB/CIFS).
I use SyncThing or Resilio Sync to send my phone's photos and videos to my NAS. When I'm on vacation with limited bandwidth, I add a sync node on my laptop (which is connected to the hotel WiFi), so my phone syncs quickly to my laptop next to me, and then through the course of the day, the laptop syncs back home.
Although it's certainly more convenient to have everything wrapped into one app, I think there's an appeal to being able to choose the tool that works for you. (In other words: it's much less code I have to write and maintain--writing battery-efficient, stable background jobs on both iOS and Android are a PITA!)
> There's an image that can't be loaded on the confirmation page
Are you using ublock origin or a pihole? Those block most images coming from mailchimp.
I'm currently running both syncthing and Google Photos to store my photos. syncthing is great once it works, but it is definitely not something I would expect a family member to be able to set up.
In any case I'm very much looking forward to see where PhotoStructure is going. I've set up a reminder to give it a try.
I'll be sending out instructions to my next wave of beta users soon.