I don’t know. Depending on how much time passes between now and the moment you try to recover the key I bet at least one of your friends will have misplaced or lost that piece of paper.
Yes. GDPR allows for delays when complying with deletion requests. You should ideally document it and factor the delay into any deadlines you might be bound to.
You’d need to make sure the process is somewhat predictable, like running the vacuum on a set schedule so you know for sure what maximum amount of time a deletion request will take.
Arq works with file system level snapshots. So I guess at one point all the files have to be present for the backup work. Not ideal for scenarios where the cloud data exceeds the local storage.
Just a note: Make sure whatever you use to backup iCloud can handle files that are not currently synced to your device.
Arq (https://www.arqbackup.com) has a setting to "materialize" these files before backup for example.
Dragnet searches are controversial in many societies, not just the US.
There’s a balance between individuals rights to privacy and what makes law enforcement easier.
One argument against broad surveillance measures like this one is that surveillance infrastructure is easy to implement and hard to get rid of again. You might be fine with the laws that are enforced with it today, but you might not be with what it’s used for in the future.
> Emergency legislation to exonerate wrongfully convicted Post Office workers has completed its journey through Scottish Parliament and each will now receive initial compensation of £600,000, with the ability to claim more as financial redress for their suffering.
There is a chrome extension for everything. OPs point is (and I agree) that these things you only need once in a while are incredibly useful when they are only a search away. Installing a chrome extension for a few uses every other week is way too much effort.
Depending on how openly and where this happens you might be able to get the platform they are selling your software on or their payment processor to take them down.
That's for legitimate platforms and processors of course. If it's on some darknet bulletin board - tough luck. Not worth the time.
I cannot count the times someone felt the need to bend over backwards to accommodate me because of something I didn’t want to do/eat/drink/whatever when I‘d been perfectly fine without any special treatment and moving on with whatever we were doing.
Manually. When you merge your code back into a common branch you look at the existing migrations and the new migrations and make sure the numbers make sense (after the merge).
You can avoid stepping on each other’s toes by using a timestamp for the number in your filename. You still have to make sure (when you merge) the order makes sense.
> How does the migration tool know which migration to apply first?
Migrations are ordered by the (ascending) number in the filename. (Or some other scheme, but this is common)
> But having to check the latest migration and check that with my local db seems a little bit error-prone and cumbersome, no?
The number in the database should never be higher than the highest numbered file in source control. So you can increment without looking.
Directory with .sql files starting with a number. Each file contains a set of changes to the db. The db has a table with the number that was applied last. To migrate your db you check if you have a file with a number that is higher than the one in the db. Then you apply that file to your db. That’s it.
Sounds like you are working in a way that is not intended by your tool / framework.