101–110 of 419 posts
Earlier quoted context omitted.
I suppose that feature would be incompatible with user data in a GDPR world ??
Git is also incompatible with GDPR, you can't simply delete a file from all history.
But you might have a hard time chasing down every copy, it's a distributed system by design.
This is all because someone thought it would be “easy” to add a stream of recurring revenue for cloud photo storage but didn’t take the time to design the service from a technical perspective to be resilient enough to not crash and burn.
This can be just calculated risk. Incredible damage for some users can be negligible damage to the company. In this case just 10TB of data was lost, so maybe thousands of users for the long term storage option. Losing customer data has potential for big reputation or brand damage, but surprisingly often the damage is relatively small. Putting in too much effort when potential damage to business is minimal may not be…
Earlier quoted context omitted.
On topic topic, can I get HN’s advice on my backup strategy? All important files on Synology Ds218+ NAS, which has 2x12TB helium HDDs in mirror. Daily HyperBackup to Google Drive. I test restoring files on a monthly basis. Email alerts on failure. Anything I can improve?
You’re way ahead of the average. The only improvement I can think of would be to server side copy the backup files to another Google Drive account that the account linked to HyperBackup can not access. That way if the Synology gets hacked it cannot delete the offsite backup too.
So, for example, ssh key access from backup to production, but not vice versa. Definitely keeping that backup system as simple and low access as possible.
Earlier quoted context omitted.
>budgets to engineer redundancies You dont need that, but a backup ;)
They obviously do have _some_ backups (since were able to restore all videos and all photos - but not all photos at the original resolution). In the end it's all a tradeoff... ignoring cost, we all know what to do to get pretty safe storage. But how much are you really willing to pay, per month, for that safety?
Thats why you backup the original data and NOT the downscaled etc one.
>But how much are you really willing to pay, per month, for that safety?
You have to backup ALL your customers data, otherwise DONT go into file-hosting business.
This is all because someone thought it would be “easy” to add a stream of recurring revenue for cloud photo storage but didn’t take the time to design the service from a technical perspective to be resilient enough to not crash and burn.
More likely than not some manager decided all those extra nines weren't really necessary.
Earlier quoted context omitted.
More likely than not some manager decided all those extra nines weren't really necessary.
The manager probably put five 9s onto the spec sheet, and provided absolutely no resources. You’ll never guess who’s going to get the heat for this, the manager or the poor person who didn’t follow the spec.
This is all because someone thought it would be “easy” to add a stream of recurring revenue for cloud photo storage but didn’t take the time to design the service from a technical perspective to be resilient enough to not crash and burn.
"Is image.canon free to use? Yes, it is free to use." from: image.canon/st/en/faq.html so as of now there is no recurring revenue added as of now
Earlier quoted context omitted.
The problem with that is that under GDPR you have to support full deletion of an user's data.
Not necessarily if you have a valid reason to storing the data. You might for example have to keep user's billing data around for legal reasons.