131–140 of 419 posts
Earlier quoted context omitted.
"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
As an aside, how the hell does Canon have their trademark as a TLD? Google, at least, I understand, because they control a sizeable portion of DNS; but Canon?
Earlier quoted context omitted.
The problem with that is that under GDPR you have to support full deletion of an user's data.
Store customer data immutable and encrypted, with a unique AES encryption key per customer. Encrypt that AES key again with a single RSA key-pair and store the encrypted AES-key in a database. You can access your customer data, using the customer-specific AES key. You can access the customer-specific AES key using your private RSA key. When you need to delete the customer data under GDPR, you can delete the encrypted…
Now you have the worst of both worlds. You also now have 2 points of failure where data can get lost, because if either has a problem you lose data.
Earlier quoted context omitted.
"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
As an aside, how the hell does Canon have their trademark as a TLD? Google, at least, I understand, because they control a sizeable portion of DNS; but Canon?
Earlier quoted context omitted.
I'm not a lawyer, but my understanding is that GDPR requires companies to remove user data upon request in reasonable time-frame. If you keep not deletable backups for one month in order to improve reliability of your service, then my understanding is that it is fine to fulfill the GDPR data deletion requests withing one month period, not immediately.
Filtering this stuff from a master transaction log is kinda ludicrous, not looking forward to implementing that.
Earlier quoted context omitted.
Then turn off the computer and cancel your internet.
That doesn't follow. That's like saying: - Slavery is bad. - Then don't wear cotton clothes. Maybe instead change the system so there's no slavery, and have non-slaves pick up cotton and make cotton clothes? Non-capitalist countries can have computers and internet too. In fact most computers today are made in "communist" China.
No Most computers today are made in "Special Economic Zone" China that has exempted almost all communist economic policies in favor of Free market capitalism because even hard core authoritarian communists know that their economic model is a path to poverty for everyone including the leaders
Lesson for those designing cold-storage solutions--design your system, as much as reasonable, to not support deletion operations. The reason why files get lost is usually due to software bugs, bad configurations, and operator errors. Design your system to protect against these things.
When I work on design I try to make catastrophic failure impossible. Not implementing deletion or implementing deletion with some unseparable constraint check is one way.
For example, the files could have a flag set and from that point on the only delete function would check the flag and refuse to remove the image regardless of how it got invoked or where the image is placed (think like write protect notch on a floppy disk).
Another way is to not actually remove the files but instead introduce grace period when they are marked as deleted, not accessible, to the user.
The only real deletion would happen in a vacuuming system that will actually remove the files but with a hardcoded constraint next to filesystem delet that the file must have been marked as removed at least XX days ago. This would give some time after deletion to actually recover files.
Yet another technique is to move objects marked as deleted to some other, cheaper form of storage. The function that moves objects must first confirm the object is available in new storage through its API and only then removes the original.
You can also prevent damage that could result from failed modification using immutable objects and Copy on Write. The copies would be deleted using the above described mechanism.
Yet another technique is to keep XX days of redo-log that could contain enough information to rebuild any object to any of its current or past state within XX days. Depending on the type of the file and nature of changes it can be much more efficient than keeping whole copies.
All of this of course adds overhead but you can recover a lot of that overhead by relaxing requirements on duplication of your operational or other forms of backup storage with rationale that if you have a redo log where you can locate current or past version of the object independently of operational or backup storage you can count it as one more operational or backup copy.
Earlier quoted context omitted.
Both AWS S3 and Google cloud storage buckets have an option that makes it impossible to delete stored objects for some period of time. The option was added for some legal compliance reasons, but I find it useful as an extra safeguard that important service data is not accidentally or maliciously deleted.
I suppose that feature would be incompatible with user data in a GDPR world ??
The example I’m aware of is where personal information is held due to ‘legitimate interest’ and the request to delete isn’t deemed (however that is defined) to override that.
I won’t try to go further as it’s not 100% clear cut and IANAL.
Have a look at the legislation or the various explainers that have been posted online if you’re interested.
Edit: In this case I would guess that Canon would have trouble claiming a legitimate interest in keeping hold of your photos!
Earlier quoted context omitted.
"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
And there won't be at this rate. Besides, it is now a net negative for their users. 'The cloud is not a backup' should be a mantra that everybody that uses the cloud for their work and personal data be familiar with.
A Backup requires
* 3 Copies of the data
* 2 Copies on Different Media / Services (i.e Amazon Photos + Cannon Images)
* At least 1 copy in a Geographic diverse location...
aka the 3-2-1 Rule
If you do not have those 3 items at a MINIMUM then your data is not backed up