strstr

Slightly off-topic, but I think you mistranslated the word for corporation. I suspect you translated “Konzern” from german to english’s “concern”. But I’m honestly unsure. In context the word concern could almost work.

Seems like you didn’t read the article to the end. It discusses the spike in unsheltered chronic homelessness on the west coast, which is the most visible type.

Shame sounds like a bad way to retain otherwise reasonable employees.

Water has a strong absorption peak at 2450 MHz (it’s what kitchen microwaves use).

A lot of the early study members were physicians and health care workers, so this doesn’t come as a huge surprise.

A pulmonologist I know that was in the Moderna study was offered a vaccine from their employer back in December. They tried to get urgently deblinded (this was after the primary study was done but before deblinding) so they could ensure the doses didn’t go to waste. This ended up being a bit of a bureaucratic nightmare, and they weren’t able to find out the answer until a few hours before their scheduled appointment. They had in fact been in the treatment group, so the dose was fortunately redirected to another healthcare worker.

Physical TPMs are crazy slow (though fTPMs might be reasonable). Is that a performance analysis? Not really, but if you are looking for performance look elsewhere.

It's a toctou bug, so probably not.

KVM is stable, small, and well fuzzed. I'm not super surprised this CVE is in the nested support since it's complicated and in flux. Last time I ran CLOC on x86 KVM it was only ~50k lines, but that was years ago.

The amount of context necessary for virt is sort of silly. IMO most of the complexity is not from the code style (though kernel code style doesn't help). It's mostly that reading KVM requires thorough context on the underlying architecture, and its virtualization features.

That said, I'd really like to see parts of KVM replaced with rust code (particularly the x86 instruction emulator). Shoving it into a safe language would give me some extra faith.

The frequency and maximum strength of tornadoes are higher in the central US. Casual skim of the wikipedia page indicates about as many F4 tornadoes in Europe as F5 tornadoes in the US since 2000.

Another neat (more common) misprint is the Foreign Black Bordered "Wald"[1] (Forest) that was printed with the coloration of a Plains.

[1]https://www.cardmarket.com/en/Magic/Products/Singles/Misprin...

This seems obviously false? I want it and I understand it? Corporate ITs would want it to mitigate risk?

You then have write amplification from the merkle tree. Ignoring performance, something like this should be possible though. For atomicity, there’s going to be some clever journaling based solution.

The frustrating flaw in these setups is disk integrity. It’s pretty consistently {speed, integrity, mutability}, choose two. Dmcrypt, dm-integrity, and dm-verity cover all the pairs, but none of them completely solve the problem. If you have fairly static configuration, I imagine you can set up a blend of, say, dm-verity (for binaries/static files) and dm-integrity (for mutable files) and get something workable.

Caveat: I seem to recall dm-integrity being somewhat flawed and vulnerable to rollback.

Isn't this Google Ventures? (https://www.gv.com/)

Most VM providers now support live migration for common machine varieties, so forced reboots are uncommon.

I guess I don't really see the benefit of "true" virtualization, other than it's usability improvements. I generally want to squeeze out ever bit of performance out of the GPU if I care to share it with the guest at all (at least on my home machine). I'd be using it for playing games.

For the cloud, I could imagine wanting vGPUs so you can shard the massive GPUs that are used there. But in cloud, you would then have a single device be multi-tenant, which is a bit spicy security wise. Passthrough has a very straightforward security model.

Passthrough is workable right now. It’s a pain to get set up, but it is workable.

You don’t need vgpu to get the job done. I’ve had two set ups over time: one based on a jank old secondary gpu that is used by the vm host, another based on just using the jank integrated graphics on my chip.

Even still, I dual boot because it just works. It always works, and boot times are crazy low for Windows these days. No fighting with drivers. No fighting with latency issues for non-passthrough devices. It all just works.

Discussion of salary and (iirc) discussion of working conditions are strongly protected in the US. Anyone know how universal that is?

For those that aren’t familiar, there is also ebird.org

This app is a much more straightforward than navigating ebird’s hotspot UX though.

Do you mean cryptography or cryptocurrency?

The keys are stripped out if you put it into the required unlock mode.

This seems like yet another thing on the list of “x86 hardware issues that sound worse than they are”.

I’m interested to see what people are able to reverse engineer with these sorts of tools. It wasn’t even that long ago that ucode wasn’t even encrypted with integrity. I don’t think AMD started doing that until around 2010.

I’m also curious which hardware versions this works on, since it’s not obvious it’s universal. I’ll be amused if it’s some forlorn low power chip from 10 years ago.

Those are also known for damaging tendons. I was already planning on avoiding them, but now I have even more reasons!

They are a post-doc? They probably don’t see it is a priority in their budget.

I’m confused by what you are trying to prove. The issue isn’t whether people believe what you are arguing. As far as I can tell, most experts seem to believe something along these lines is most likely.

The question is whether or not they have verified it in this context.

The problem is the lack of certainty. Most suspect that you won't lose protection by waiting longer than the suggested timeline, but what you really don't want to do is sleep-walk into throwing away the currently administered doses.

Frustratingly, I'm guessing the timelines for a study on the durability of single dose moderna/pfizer would take about as long as it will take to ramp up production.

My impression is that this is more about publishing tree head hashes as a way of promising that you have nothing up your sleeve. You can't remove something after someone has depended on that value being there without someone noticing. The certificate transparency comparison is helpful.

If it's append only, you should be able to find the old head in the log. Not sure if that is what it's going for though. I'm still a bit confused by this myself.

I'm not totally sure those solve the problem this aims to solve. That's like saying that certificates solve the problem that certificate transparency solves.

They are related, but not quite the same.

He is getting paid to.

Friend of a friend did the same thing as GP. I believe it “just” requires visa approval and quarantine.