That’s literally what a pi-hole is.

Lead-based solder is preferred for high-reliability electronics (space, nuclear, military, etc.) because it’s easier to rework, easier to verify by visual inspection, and it’s not vulnerable to tin whiskers.

Here’s the relevant safety guides from Stanford and MIT.

In short, if you do a lot of soldering, there are long-term occupational hazards from both lead oxides and rosin. Both guides agree that the main hazards are the fumes (workstation should have a fume extractor or suitable filter) and residue on your hands (wash hands with soap and water before eating).

I couldn’t find any numbers on how much material is removed by washing, but every reference emphasized that soap and water are vitally important.

We are the Cube Rule. Lower your shields and surrender your ships. We will add your food’s biological and technological distinctiveness to our own. Your food categories will adapt to service us. Resistance is futile.

I’ve had great luck running HomeAssistant on an R.Pi with the “HUSBZB-1” USB dongle. Zigbee support is perfect so far. Z-Wave required installation of an additional tool, but also working just fine.

Doesn’t the ESP32 module this project is using require the same thing?

It works for now on x86-64, yes. For now. As always, we are one “think of the children” crisis away from lobbyists taking that option away.

It’s not for you, it’s for them. Secure boot means it only runs their operating system, not yours. Trusted enclave means it secures their DRM-ware from tampering by the user who owns the PC.

“The definitive Voyager torpedo inventory log” is a classic.

With this event’s non-occurence, the thread of prophecy is severed. Restore a saved game to restore the weave of fate, or persist in the doomed world you have created.

“Hmm. Computer says no.”

Every time I see “lichess”, it makes me think about “lich-ess”, i.e., a female undead wizard.

Elerium-115?

Sure, but there’s still no excuse for “store the password in plaintext lol”. Once you’ve got user access, files at rest are trivial to obtain.

You’re proposing what amounts to a phishing attack, which is more effort, more time, and more risk. Anything that forces the attacker to do more work and have more chances to get noticed is a step in the right direction. Don’t let perfect be the enemy of good.

No, defense in depth is still important.

It’s true that full-disk encryption is useless against remote execution attacks, because the attacker is already inside that boundary. (i.e., As you say, the OS will helpfully decrypt the file for the attacker.)

However, it’s still useful to have finer-grained encryption of specific files. (Preferably in addition to full-disk encryption, which remains useful against other attack vectors.) i.e., Prompt the user for a password when the program starts, decrypt the data, and hold it in RAM that’s only accessible to that running process. This is more secure because the attacker must compromise additional barriers. Physical access is harder than remote execution with root, which is harder than remote execution in general.

Is this why Ian McCollum’s videos are getting altered? Over the years, he’s had many historical deep-dives featuring firearms from the Murphy’s auction house. In recent months, he’s been re-uploading those videos to cover their logo with the word “Morphy’s”. Even though the auctions are long over, I suppose Google counts them as promoting sales.

Phase 1: Fuck around

Phase 2: Find out

Incentives like this are tricky. You can reduce the numbers by fixing the problem, or by sweeping it all under the rug. Guess which is easier to do on a quarterly basis?

Vulcan science academy: Why do you need another warp core?

Humans: We’re going to plug two of them together and see if we go twice as fast.

VSA: Last time we gave you a warp core you threw it into a sun to see if the sun would go twice as fast.

Humans: hahaha yeah. It did tho

VSA: It exploded.

Humans: It exploded twice as fast

Send them an invoice at your expected hourly rate.