The fact that the opposite to “steerswoman“ is “figurehead man” is absolutely perfect, you definitely cannot expect a truthful answer from one of these.
In case you know German (even at a basic level), you might enjoy Sendung mit der Maus (a TV show for kids that shows how various things work/are made that's been running since 1970s).
Wir tauchen ab ins Reduit, folgen den Irrwegen von Überwachern und gespeicherten Daten, die fast vollständige Abziehbilder unseres Lebens formen.
❗Heute Abend❗ im Theater Neumarkt – mit @adfichter, @sylkegruhnwald, @karpi, Kristina Malyseva u. a.
https://www.republik.ch/veranstaltungen/wir-haben-nichts-zu-verbergen
Still happening, albeit with a smaller number of copies: I've got two notifications for end of the following poll: https://mastodon.neilzone.co.uk/@neil/112048388768399462
Do you mean the guidelines at https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Gender_identity#Current_guideline, or that they are not actually followed?
Ah, sorry, I wanted to ask whether "it's hard to guess how hard" applies to average or worst case or both.
How hard it is on average (averaged over instances), at worst, or both?
Currently checked out commit or a reference to it (depending on how it was specified when checking out). I expect e.g. `git checkout <file>` to pull that file from HEAD.
I'm not sure what happens if HEAD points at a ref and I modify that ref using an operation that doesn't normally affect working tree/index.
Ah, so when talking about controls effectiveness you'd have less/no qualms to consider probability of control failure under the assumption that the event it's against is occurring?
> I think the same safety lesson applies to security: improbable things happen all the time. It's more important to have robust failure modes.
The place where I don't see how to apply this is with code changes/code review -- after all any controls that are implemented in your codebase can be negated by changes to it, which might be improperly reviewed.
If you focus nearly exclusively on impact, how do you judge controls that mostly (only?) affect probability? (For example, most detection mechanism I can think of are imperfect, so they have a range of potential impact reduction between "down to 0" and "no reduction", with some nonnegligible probability assigned to "no reduction".)
Totally agreed on motivations of attackers.
One reason why I think talking about malicious actors makes sense is that in some scenarios you will have actors who unwittingly help the attacker. Their expected range of behaviour is part of the threat model, so they should be mentioned somehow while being distinguished from the attackers (who are unconstrained in their range of behaviour save for things they can't do).
There were (are?) some registries (or individual registrars? sadly I don't remember the details anymore) where you could get refunded if you returned the domain within something like a day of buying it. If they still exist, that might be one reason for this weird behaviour.
@freemo Ah, then it's quite likely that it was indeed before then. I'll then notify you again if it reoccurs, and otherwise will assume this was a result of the issue at that time.
> Is it possible you voted on it back when things were still broken?
Unlikely, given that the poll started 3d ago (according to its timestamp).
(If it's in any way helpful, earlier polls on which the same thing happened to me: https://social.jvns.ca/@b0rk/112014805256252757 which started 5d ago, https://mastodon.social/@danluu/111994437263038931 which started on Feb 25th.)
@freemo Since the update I get multiple end of voting notifications for each poll I have voted in (e.g. just got 10 notifications in a row for https://mastodon.nz/@pezmico/112028203100230568). It doesn't bother me so far, but I figure it might be a symptom of something with other annoying consequences.
@nothacking @lcamtuf you also specify iiuc what's the source of the clock (external clock, external quartz, internal oscillator?), which clock consumers are clocked (and thus, which peripherals are usable), and potentially more things around clocks that get and that don't get suspended in sleep modes.
(There's some state you are in just after reset and thus usually would just write the difference wrt that state.)
I'm confused how you could flip the tailstock around. Wouldn't you end up with the business end facing away from the chuck? (I'm assuming you'd leave the chuck and the whole motor setup in place.)
Wouldn't the location of the leadscrew for the carriage be another problem?
Tangentially related, on the off chance: do you maybe have recommendations on where to read about thermoregulation? I was wondering whether any of the mechanisms can affect sides of body unequally. I've found some neurology textbooks that implied that the answer is no, but were describing everything in a way that is slightly alien for me.
I enjoy things around information theory (and data compression), complexity theory (and cryptography), read hard scifi, currently work on weird ML (we'll see how it goes), am somewhat literal minded and have approximate knowledge of random things. I like when statements have truth values, and when things can be described simply (which is not exactly the same as shortly) and yet have interesting properties.
I live in the largest city of Switzerland (and yet have cow and sheep pastures and a swimmable lake within a few hundred meters of my place :)). I speak Polish, English, German, and can understand simple Swiss German and French.
If in doubt, please err on the side of being direct with me. I very much appreciate when people tell me that I'm being inaccurate. I think that satisfying people's curiosity is the most important thing I could be doing (and usually enjoy doing it). I am normally terse in my writing and would appreciate requests to verbosify.
I appreciate it if my grammar or style is corrected (in any of the languages I use here).