ohazi

People struggle to get their Bluetooth headphones to pair reliably with their phone, can you imagine the nightmare of simultaneously pairing with a phone, an excavator, and two bulldozers?

You can't be serious.

We're talking about the kind of training needed to work some garbage CRM that the employer uses, not a decade spent mastering a fine art...

Helvetica looks better

These are private jet flights, not hobby Cessna flights.

> “The next day, I enjoyed pan-roasted oysters with a tomato sauce over rice and broccoli salad, followed by bread pudding with chocolate sauce.”

This just moves the ambiguity.

Is the tomato sauce over rice, with a side of broccoli salad? Or is the sauce over [rice and broccoli salad]?

In this case "rice and broccoli salad" doesn't really sound like a dish, but why the fuck wouldn't you just use a tiny piece of syntax to make it super clear, rather than relying on the reader hopefully having similar culinary sensibilities?

> You should switch carriers immediately.

They all do this.

Another useful thing to store as `pass` secrets is credit card numbers / parameters.

This makes it easy to fill in card info online using the same password tools you're already using (passmenu, rofipass, etc.), without needing to go find your wallet, or rely on your browser's form auto-fill database (and worry about hidden fields attempting to exfiltrate that auto-fill data).

I'm tempted to use `pass` to store TOTP seeds as well, but this seems like a bad idea because you'd be putting both factors in one place. Maybe a separate pass db stored offline or something...

Fine, turn my statement around if you prefer. The reason people aren't afraid of being murdered is because being a victim of murder is rare.

But the statistic you're citing here conflicts with your earlier statement (which is the one I take issue with):

> isn't because we have super advanced defense systems but because the fear of punishment keeps people from doing it.

The "fear of punishment" deterrent is clearly doing absolutely nothing for the 40% of women who have been / will be sexually assaulted.

Fear of punishment does not work when "correct" execution of justice is so rare and arbitrary. That's my point. Police are corrupt. Prosecutors are corrupt. Therefore, there is no justice. Therefore, "fear of justice" doesn't work as a deterrent.

Even if the police were better, if all it takes is a few murdering, raping, psychopaths to do all of the damage, how could "fear of punishment" possibly work?

There is, however, fear that the bureaucracy will decide to come after you in a Kafkaesque horror show...

> The reason most people aren't constantly worried about being murdered isn't because we have super advanced defense systems but because the fear of punishment keeps people from doing it.

No, the real reason most people aren't constantly worried about being murdered is that most of the people we encounter aren't murderers.

> This was not caught by Dell, or even the STH team at first, it was a YouTube commenter. If that is how we as an industry are catching the easy plain-to-see stuff, that should scare everyone about what may be hard to see.

And this is why the people shouting that "the direct cause of the log4j bug is our collective failure to give open source maintainers bags of money" are wrong. Don't get me wrong, you should give people bags of money if you want them to drop everything and go fix a critical bug after it's been discovered.

But our collective ability to discover bugs is abysmal.

They should probably supplement this "expensive corporate SaaS pricing" model with a "free for personal use" option if they want to have any hope of maintaining their standing.

> They should have been buried in useful pull requests.

Drive-by pull requests during a highly visibile emergency are rarely useful.

In Drone<Hovering>, shouldn't land be:

    fn land(self) -> Drone<Idle> {
        Drone::<Idle>::from(self)
    }

instead of:

    fn land(self) -> Drone<Idle> {
        Drone::<Idle>::new()
    }

Otherwise the position assertions in drone_flies fail, because it's looking at the position of a brand new Drone<Idle>, rather than one based on the position you just flew to.

Edit:

Yes it should. [1]

[1] https://github.com/rustype/drone/blob/main/src/drone.rs#L53

Not necessarily. If it's the smoke and smell that bothers me rather than intoxicated antics, I might be more annoyed by someone lighting up at the coffee table next to mine than if they were just sitting there stoned out of their mind.

> Only thing missing was reading out the OTP, obviously, which I would not have done.

This is the real red flag here. No workflow that I'm aware of ever has you read a one-time code to a human, it only ever goes into a text field.

Wow, I didn't realize they still relied on a golden-key style root of trust... I assumed they were trust on first use. That seems pretty bad!

Does anyone make a "glass house" TPM? As in, a device that you can plug in to your motherboard's TPM port that implements the complete TPM 2.0 protocol, that looks/acts/feels like a real TPM, but then deliberately includes a side-channel like a USB port or something that gives a user full access to the TPM internals (keys, registers, etc.).

Obviously you'd never use something like this for trusted boot, but with Windows 11 requiring a TPM, and applications moving in the direction of "we refuse to run unless the environment is pristine" (e.g. video games with anti-cheat features, banking apps), it seems that something like this might eventually be useful for getting around DRM and restoring our ability to run whatever we want on machines that we own.

Source?

We skipped AGI and invented a paperclip maximizer directly instead.

> The key thing is to ensure they are not too save-worthy.

Basically the definition of a chilling effect...

I once heard someone suggest that creating mirror-prions out of mirror-proteins might one day be a safer way to study prion diseases, since an accidental leak wouldn't be able to trigger the misfolding cascade on the researcher's own proteins, since they're not mirrored.

No idea if this was meant seriously, but it simultaneously sounds reasonable and terrifying...

I particularly like lock-free (wait-free?) SPSC queues because they're (relatively) easy to get right, and are extremely useful for buffering in embedded systems. I end up with something like this on almost every project:

One side of the queue is a peripheral like a serial port that needs to be fed/drained like clockwork to avoid losing data or glitching (e.g. via interrupts or DMA), and the other side is usually software running on the main thread, that wants to be able to work at its own pace and also go to sleep sometimes.

An SPSC queue fits this use-case nicely. James Munns has a fancy one written in Rust [1], and I have a ~100 line C template [2].

[1] https://github.com/jamesmunns/bbqueue

[2] https://gist.github.com/ohazi/40746a16c7fea4593bd0b664638d70...

Doh. You're right. And that's even why they call it the fraction, because it's the fractional component of that 1.XXX number between [1.0, 2.0).

My brain fart was forgetting how floats work, seeing that the integer-resolution range for both single and double precision floats was exactly the number of bits in the fraction + the sign bit and then pattern matching.

This is how you get the equivalent float value from an integer, assuming it fits within that 53 bit range. You're correct that you could pick a larger exponent at the expense of being able to store consecutive integers.

Edit: Ignore this, I'm wrong.

53 bits.

If this seems strange to anyone, it comes from the fact that all numbers in JS [1] are represented as double-precision floating point values. The bit format for doubles is a sign bit, 11 bits for the exponent, and 52 bits for the fraction.

When storing integers in floats, you use an exponent of 1, and then stuff the integer into the fraction and sign bits.

[1] I think bigint is a thing now?

The way that Destin described "revoking access" in his original video is misleading enough that I think it warrants an actual retraction.

As Drew points out, the thing that he described is clearly not possible, thanks to the "analog hole" (or even an equivalent "digital hole" -- if the protocol is open source, there's nothing stopping me from creating a fork of their software that logs everything it ever sees).

Closing the analog hole is impossible. Closing the digital hole would require some sort of DRM, which is definitely counterproductive, and most likely ineffective.

No, you're definitely not the only one.

GTK is used by a lot of projects that are unrelated to GNOME, but unfortunately GTK still lives under the GNOME umbrella, and the GNOME developers are an unbelievably antagonistic bunch.

In California they're definitely timber because earthquakes.

> One of Microsoft's greatest strengths on show here. Embrace and extend.

Why would Android developers go along with anything Microsoft tries to "extend" Android with when Google will just go "lol, no"?

This seems more like a desperate grasp than "embrace/extend/extinguish."

> Detached no matter the cost - so close they may as well be terraced, but they'll be detached 'gah-damnit'!

The difference between "so close" and "terraced" is hearing your neighbors fucking at night. No thanks.

Agree with you about the shutters, though...