robryk @robryk@qoto.org

@mcc I always(?) found it somewhat nice that this list includes cooperation but not negotiation.

@cstross @munin @SwiftOnSecurity

Do you know what's the efficiency of pushing power into something (train grid? above-surface resistors?) when braking?

@kurtseifried @hdm

At least the grapheneos reference is not about rebooting regularly, but about causing the phone to reboot (and thus lose all the secrets protected by the passphrase) when it's not unlocked for sufficiently long. That protects phones taken against the owner's wishes, insofar it gives the attacker a limited window in which they can try to get at these secrets.

@b0rk For added amusement: in the case you're depicting std{in,out,err} are all the terminal, so are all identical. You can read from stdout or write to stdin. :)

@munin

Doesn't the dynamic change once you have more than 2 players?

@whitequark BTW are there any "land immediately" failure modes listed? (The obvious one would be imminent total hydraulic failure, but I'm not sure if there's a procedure in QRH for that.)

@whitequark As opposed to "land immediately"?

@jeff @Lana @shantini

Not really? The obvious reaction then would be concern for (a) what's going on physically with them right now (b) what's going on mentally with them. I guess that reaction guided at (b) would be checking whether they are aware of what they're doing, which resembles "What do you mean?", which Lana argues against in a sibling post.

@rysiek

What if they are aiming to increase the number of people who are intrigued enough to start reading the article (á la "you can't guess what happened"-style headline)? I would expect that being imprecise helps with that goal (because you can tell less about the story from the headline) and using terms that sound less pedestrian than they are does that too. (And then you want to keep consistency in the rest of the article, maybe?)

@aredridel @mcc @AlgoCompSynth

You mean the ones that are emitted as mechanical vibrations or vibrations in current draw (they are coupled, but if I imagine things correctly the coupling will be between weak and, for motors driven by VFDs, nearly nonexistent)?

@mcc @AlgoCompSynth @aredridel

An interesting question is where the mains frequency comes through to the signal path. If there are nonlinearities along that way, they will generate harmonics. (This is e.g. why the transformer buzz is a buzz: the path from changing magnetic field to position of movable conductive pieces works similarly to a kazoo, because those metallic pieces often behave like springs that get stronger the further you pull them.)

@jasongorman

If you describe something as an FSM, you need to describe the states and transitions. For any nontrivial program you can't enumerate states nor list the full table of transitions. So, I expect that you want languages where what you write is a description of the full state of the program and a transition function (in some fashion).

Nothing that is literally like that comes to my mind, but this reminds me of https://en.wikipedia.org/wiki/Functional_reactive_programming, where you write functions that take streams of input events and produce output events. You can think of the internal state of the function as FSM state and the function's logic as defining transitions. (This approach admits compositionality in a pretty obvious way; I don't see how anything more FSM-like would, which is, I suspect, correlated with me not knowing practical languages that are more FSM-like.)

@mcc @dansup

Following that reasoning, a storm often causes water level in a river near where I live to rise a few days earlier. :)

@mkj @niconiconi

If you have a slowly-changing signal, you can use a 1 bit ADC to get arbitrary resolution, by adding white noise of a known distribution to the signal and ADCing the sum (the averaged value you get from your ADC will correspond to the noise's PDF at negative input signal value).

Amusingly, many GPS receivers (used to?) play a similar trick, because they deal at some point with something like a signal with very low SNR that they have to average over a longish period of time (although they don't care about increasing resolution, but only increasing precision), so they already had to deal with a noisy signal. (See https://s53mv.s56g.net/navsats/theory.html for the kind of simplifications that yielded in old receivers.)