I mean the OpenAI/HuggingFace thing was incredibly similar, except maybe more reckless than specifically intentional, I suppose. Didn't stop them milking the doomer angle for PR.

I have to I say (if it's sarcasm) that I appreciate the commitment to the bit. Unfortunately, it's getting harder and hard to tell these days...

If the whole British Post Office Scandal (Fujistu, btw) in the UK wasn't enough, nothing will be. People literally killed themselves over the accusations/convictions that were 100% false. One of the major people responsible was an Anglican Priest(!) of all people who was so sure that the Computer Is Right... [0]

We're headed for even rougher times if LLMs are going to be taken "at their word".

[0] Now, watching her testimony, it seems she was willfully complicit and it's a disgrace that she isn't in prison, but that's tangential. The "system" was responsible, but without personal accountability, nothing will change. So it goes.

Absolutely. Very happy 10+ years subscribed here and I'll keep subscribing.

(As someone pointed out in the comments, the title of this specific post could have been less heart-attack-inducing, but still... :) )

Yup, they are often just Accountability Sinks.

Not quite what you're asking, but pre-registration does alleviate e.g. p-hacking and such without the need for multiple teams. It doesn't do much for outright fraud, but still...

Only if the study matches its pre-registration and someone is checking that. Which it turns out, they often don't.

https://www.compare-trials.org/

That's a fair point. Ultimately, incentives are all screwy at the moment.

Gotta tie some actual prestige/shame to not following up.

Exponential is also overkill (even with jitter as others have mentioned).

I seem to remember there was a "you failed 5 PIN entries in a row, please wait 500000 seconds before you retry" on Apple phones. So, you probably also want a sensible max... which makes exponential a bit pointless. Just do a basic fixed delay + (large, e.g. 0.5 x the delay) jitter and you'll be fine for most things. You can add a bit of cumulative delay if it's really costly to do retries.

Cap the number of retries before the user has to manually try again. That's fine.

LinkedIn was overtaken by LLM nonsense at about the release of ChatGPT 3... I mean it was incredibly stupid and transparent engagement slop before that, but still.

I remember talking to a business type who was so incredibly proud that GPT could turn his incredibly vapid thoughts into bland pointlessness on LinkedIn... not realizing that everyone in his feed was doing the same thing. We never did business with him for ... reasons, obviously :)

It might surprise you to learn that that would also be considered a dick move.

As I alluded to elsewhere, I've yet to see a layoff where there's no one who doesn't consider how it was done "a dick move." Your preferred way of doing a layoff will be someone else's "dick move" judgement.

Yep, once people discover the multitude of JVM flags the cargo culting begins...

It really applies to anything with a huge number of options, I remember similar things from back when I used Gentoo and the wild suggestions I'd get for what exact CC/C++ compiler options to use...