I need time to try this out for real, but the simplicity/power ratio here looks like it could be pretty extraordinary. Very exciting!
Tiny remark for @kentonv if you're reading: it looks like you've got the wrong code sample immediately following the text "Putting it together, a code sequence like this".
We are the Bennett Institute for Applied Data Science, at the University of Oxford, led by Professor Ben Goldacre (of “Bad Science” fame). We built OpenSAFELY, a revolutionary open source platform for secure clinical research. Conceived at the start of the COVID-19 crisis, it is used to produce ground-breaking research using a huge corpus of patient data which is not available anywhere else in the world.
We’re hiring for software developers at all levels, as well as tech lead and product management roles.
Tools we use include Python (and Django), Javascript (and React), Docker, Postgres, SQLite and HTMX. Our entire platform is open-source:
https://github.com/opensafely-core
Its use in MS involves injecting it into the muscle, whereas this trial was using nebulisers to deliver it directly to the lungs so I don't think looking at MS patients would tell us anything useful.
> Actually, if your parents are married and even one is a US citizen, you will be too, always.
Interestingly it's even more subtle than this: you can be a US citizen, but if you haven't spent enough time living in the US (for a definition of "enough" when years spent as a child count for more) then your citizenship doesn't automatically pass on to your children.
> Note that exercising this claim yourself will permanently disqualify you from government clearances at all levels.
Can you elaborate a bit more on this? Is it something specific to German law? A relative of mine who holds both US and UK citizenship worked for the US government and later for the UK government and was granted elevated security clearances in both roles.
I asked them about OAuth token usage at one point and this was the response I got:
> The "refresh token" does not leave the user's machine. This is the permanent token that we use to generate an "access token", a transient token (expires in an hour) that is used for actually communicating with the Google APIs. We sometimes send an "access token" to our servers for verification purposes, but we never store them (and they expire anyways).
Obviously it would be better not to have to trust a third-party at all, but it doesn't seem like you have to completely hand over the keys to the kingdom.
If you're not in a huge hurry to delete the bucket you can easily set lifecycle rules to expire all versions older than 1 day (the minimum) and then just wait for S3 to delete them for you.
Tiny remark for @kentonv if you're reading: it looks like you've got the wrong code sample immediately following the text "Putting it together, a code sequence like this".