I don’t understand how regex comes into it? Sounds tricky though!

I asked an LLM to write a jq scriptlet for me today. It wasn’t even complicated, it just beat working it out/trying to craft the write string to search Stackoverflow for.

It’s a shame that you’re so quick to express skepticism but so reluctant to do any research of your own, because the facts are a bit embarrassing with the exact same trend in the USA as in the UK.

Driver safety peaks in the 60s, and only moderately worsens after then. The large increase in fatal accidents, by the way, is clearly a result of older drivers being more vulnerable in a crash - because the chart at the bottom doesn’t show any such large increase for passengers and others.

I’m interested to know if this changes your mind.

That doesn’t affect the ability of older drivers, only the number of them.

In fact, since one reason very old drivers might get more accident prone is because they stop driving as much and lose some of the skills, you would expect that, if older Americans really persist in driving more as they get older (you haven’t provided any evidence that they do) they would retain those skills and be less accident prone, not more, so would be safer, and less at need of re-tests, than their UK counterparts.

Focusing on the driving safety of the elderly is a classic example of Saliency Bias. A 20-year old kid wrecking his car is nothing unusual so you don’t remember it when thinking about safety. An 80 year old who can’t even remember which way to turn the wheel getting in a wreck is unusual and extreme, so it’s more salient. Getting stuck behind an elderly driver gives you the impression that they’re a bad and hence unsafe driver, which contributes to this.

Fact is that if you want to spend some money, time or political capital on improving road safety, targeting older drivers is not where you should focus your efforts. The fact that it frequently is, is due to ageism.

In the absence of forthcoming data (hint hint), what factors do you think differ between the UK and USA which affect the ability of very old/very young drivers?

This is your regular reminder that it’s generally not older people who are high-risk drivers: https://assets.publishing.service.gov.uk/media/628ce5c7e90e071f68b19dfa/02-image-2.svg

Drivers get safer until about 70, and only get less safe than your average young driver when over 86.

There is a perception that older drivers are an absolute liability on the roads, which I can only assume stems from impatient people who get frustrated when stuck behind an older driver going more slowly than they’d like.

Really, you can’t think of any reason to be upset that you’re required to take an exam that you then pass?

As far as I can work out about this USA, this is not true. It is certainly not true where I am from. It may be true in the case of postdoctoral researchers (but not always), i.e. relatively junior researchers who don’t yet have a permanent position. But a permanent position is just that - it’s like a permanent job, and you’re paid a salary by the university that gave you that position. You will typically also need to apply for grants in order to pay for things like:

• travel to conferences
• travel to collaborate in person with colleagues at other institutions
• make papers open access
• hire postdoctoral researchers and PhD students.

I did two postdocs during my time in academia and both were grant funded (one awarded to me, one awarded to a more senior researcher who then took me on as a postdoc). I also applied to one postdoc position I remember which although fixed term, not permanent, was paid for by the university. I worked with many permanent staff who had salaries from the university as well as grants for other things.

As far as I can tell in the USA the only real difference is that your salary may only be for the 9 teaching months, not the full academic year, and you’re expected to top up those 3 months if you want to be paid a proper wage.

This is not really “mildly infuriating” and you should make the link point to the article, not to a screenshot from it.

Hey if you’re colourblind, all blues can be blurple. And so can all purples!

The requirement to not track users with cookies does not extend to cookies that make the site work in the first place, such as those which track your login session, or your refusal of other cookies.

Shouldn’t the engineer be a bit more worried if the cable’s been cut?

If UDP drops packets it’s probably nothing. If TCP drops packets it’s because something’s actually wrong.

If you’re using TCP and losing packets you should be panicking though, because something is very wrong…

An overarching principle of security is that of minimum privilege: everything (every process, every person) should have the minimum privileges it needs to do what it does, and where possible, that privilege should be explicitly granted temporarily and then dropped.

This means that any issue: a security breach or a mistake can’t access or break anything except whatever the component or person who had the issue could access or break, and that that access is minimal.

Suppose that you hit a page which exploits the https://www.hkcert.org/security-bulletin/mozilla-firefox-remote-code-execution-vulnerability_20230913 vulnerability in Firefox, or one like it, allowing remote code execution. If Firefox is running as root, the remote attacker now completely controls that machine. If you have SSH keys to other servers on there, they are all compromised. Your personal data could be encrypted for ransom. Anything that server manages, such as a TV or smart home equipment, could be manipulated arbitrarily, and possibly destroyed.

The same is true for any piece of software you use, because this is a general principle. Most distributions I believe don’t let you ssh in as root for that reason.

In short: don’t log in to anything as root; log in as a regular user and use sudo to temporarily perform administrator actions.

P.S. your description of the situation shows you don’t know the nature of vulnerabilities and security - if you’re running servers then this is something you should learn more about in short order.

“Prove you’re not a machine by training this machine to pass this exact test.”

There is nothing stupid about this unless you believe that the people behind it had no plan to change out the challenges over time.

you could instead do:

dcl() { docker container ls -aq -f name="$1" }

in bashrc or wherever you’re setting this up.

Why create the function _dcl()?

Must be time for a new Linux audio system. The pipewire-pulseaudio-ALSA stack of compatibility layers is old hat already.

I remember looking into the situation with non-destructive editing about… 20 years ago. I wonder how long it’s been a desired feature!