So yeah vitamin d might help on one hand, but cause it’s own issues in different areas.

No more vitamins for me. Better to eat well and get the occasional bit of Sun.

https://www.pmda.go.jp/english/about-pmda/0002.html

If you imply ivermectin has some part in japans strategy, I encourage you to read this:

https://www.forbes.com/sites/brucelee/2021/11/27/no-ivermect...

The most ideal set up would be to have a universally Yubikey or something equivalent. Preferrably with a backup pre-configured second Yukibey possible in a disaster recovery bugout kit. Then have all the initial QR codes, otp secret manual otp key strings like i demonstrated above your post, account recovery keys, backup break-in codes, or whatever other flavor of two-factor recovery a service uses, all this notated in a secured password manager. The real problem i see with two factor is that the offered recovery method is so variable from service to service. it makes knowing which information you need to have on hand when you've gotten locked out is problematic.

the other thing i do is that for core cloud service providers, i print out the password manager details for the accounts. this is apple, cloud backup service, google, microsoft and a couple of hardware device passwords. it's a risk to have this printed, but the print out is in a fireproof safe with a trusted party.

i basically assume my disaster recovery plan is that i have my wallet and the clothes on my back and nothing else. everything else gone including my computers and phones and i have to get back all services and data without having any devices.

the higher the level of security, the higher level of disaster preparedness the end user needs to practice.

I've emailed my elderly parents to make sure they understand that this mandatory 2fa roll out is happening, and I've explained how they could fuck up their accounts by not notating the recovery method. offered to review their details to make sure it passes a sniff test.

i've been able to do this because i replicated otp set up in a second source (1password).

in 1password, edit the record then inspect the otp field string. it will look like this:

otpauth://totp/Discord:you@email.com?secret=blahblahblah&issuer=Discord

save the "blahblahblah" and you can manually recreate a token at any time.

https://www.pewresearch.org/fact-tank/2020/04/28/millennials...

If the ICU patient can't breathe on a vent and are able to secure ECMO, the ECMO specialist ratio is ideally 1:1. Under a crush of patients maybe 1:2 patients. A 1:3 ratio is risking all the patients under that specialist's care because the patients are all too tenuous. Let me reiterate and restate: 3 ECMO patients are too much for a single ES to support.

The ECMO specialist isn't the only person caring for the patient. There is the ICU nursing staff, the pulmonary therapist, plus the actual pulmonary doctors, the renal doctors, plus plus plus. You are talking decades if not a hundred+ years of study just to take care of a single ICU patient.

Labor and not beds is the bottleneck.

This is Osterholm's wiki bio, notably he is the head of CIDRAP he was named as an advisor by Biden during his transition : https://en.wikipedia.org/wiki/Michael_Osterholm

Link to CIDRAP and the type of material he's putting out under his podcast for the public's benefit: https://www.cidrap.umn.edu/

Link to his YouTube channel. It's a real shame he's unable to get a verified channel due to his low subscription numbers. https://www.cidrap.umn.edu/covid-19/podcasts-webinars

I am not affiliated with Dr. Osterholm, the University of Minnesota, CIDRAP, or his podcast support team. I'm just a listener.

Comments URL: https://news.ycombinator.com/item?id=28003635

Points: 8

# Comments: 3

Okay, so my account generates five 2GB zip files. I randomly picked file #4 and unzipped to inspect the contents. The structure of the zip file included the following:

* Google Photos

* Contacts

* Drive

* YouTube and YouTube Music

Interestingly, while the general structure looks okay, the content under the directories is incomplete. I'm not sure why this is. Like for example, "Contacts" has only one person's recently added Contact and only a JPG of an emoji face at that. That definitely isn't a complete data set, and makes me wonder if Takeout Services is not a cumulative back up, rather only a delta.

I downloaded a second file, to see how it was formatted. The second file also had Contacts data. It generally followed the contact groupings I have in place (ex. family, friends, medical, shopping, etc.). It had a smattering of .vcf files with profile pictures for some, but not all, people. YouTube directory had what looked to be a complete download of all videos I've ever uploaded, plus various other historical record of my YouTube activity.

Basically, it looks like recovery of a single service is only possible with a full set of recovery files (in my case, all 5 files). The content of each recovered service depends in great part on the nature of the service. There is a lot of garbage in the back up files for the unused / lightly used services. What's happening with the Contacts is a bit concerning since the the data is split between (apparently) all 5 back up files. Same thing for Drive, and maybe Mail.

Recovery of the data and service would be service by service, and dependent on the type of service, and the data provided in each service type.

https://takeout.google.com/

This service permits the export of (nearly?) all Google services data on both a scheduled and unscheduled on-demand basis.

I have my Google account configure to automatically export all service data every 2 months and upload ZIP files to MS OneDrive. This process completely bypasses me and my local computer. I just have to remember to check that the data transferred to OneDrive as expected.

The only constructive criticism I have of the Takeout Services scheduled process is that the scheduled exports are limited to a one year duration. I have to remember to reconfigure the next year's scheduled exports. Ideally I'd be permitted to set and forget, with a periodic reminder that the export is still happening and a "Good" / "Not Good" confirmation that the process ought continue.

Takeout Services won't restore function and applications, but at least a great part of my data won't be irretrievably lost.