The white paper states the definition more precisely:

"LISEP’s definition of “True” employment or unemployment accepts the U-3 rate for comparison purposes, but modifies it by adopting two important stipulations. The first stipulation deals with the workweek. To be employed for the purposes of LISEP’s true employment concept, an individual must either have a full-time job (35+ hours per week) or have a part-time job but no desire to be full-time (e.g., students). The second stipulation is that an individual must earn at least $20,000 annually."

https://svr.co.uk/news/heritage-trains-to-carry-commuters-as...

And given that the system does not have that "important but not urgent" category it's also reasonable to complain when the government uses the "urgent" notification system for something that is not urgent.

It caused me to turn off "severe" alerts (leaving "emergency" enabled).

(The PDF mentions "the standard for deidentification set forth under the California Consumer Privacy Act", which suggests this is all pretty well legislatively understood.)

The other thing about leeches is that they're a sign that you probably want to try to change something about the way you're trying to learn them, because what you're doing now is obviously not working for those things.

What other projects choose on the question is interesting and might inform the choice, but what e.g. the kernel opts for doesn't control what Debian decides for itself, any more than the kernel's choice imposes any requirements on Rust or glibc or gcc.

Choice 7 says "The proposal does not cover indirect contributions, i.e. those originating from upstream works.". It's only making requirements on Debian work specifically.

Choice 8 says "We also acknowledge that LLM usage can be hard if not impossible to detect and that Debian as a distribution cannot really impose LLM policies on other projects we package and distribute. Therefore this text is just a position statement." It doesn't impose any requirements at all on anybody, even for debian specific work: it just says "we'd prefer it if you don't use this technology".

I guess my point is that I think the problem is nimbies, not environmentalists, and since I think we need a faster and cheaper planning system in the UK I think it's important to identify the actual problem. Getting the Campaign to Protect Rural England or whoever to produce a ranking of places by importance does nothing if we still have a system where local residents can raise objections about building on locations at the bottom of the ranking and it takes forever to push something through.

Looking at the alpha architecture manual, the fp emulation traps are imprecise, which imposes constraints on codegen to make it work right: the "trap shadow" extends from the potentially trapping insn until a following trap barrier, and in the shadow you mustn't e.g. use a register more than once as a destination, have a branch, or modify registers that are inputs to any insns in the shadow. (The idea is that the hardware will have already executed some of the insns in the shadow by the time it realises it needs to trap, and the handler has to be able to emulate the trapping insn and resume execution at the insn just after that, so it will re-execute all the insns in the shadow.) That's obviously pretty inconvenient for codegen, so I wouldn't be surprised if the compiler provided some kind of fast-math mode where it didn't trap and you just had to avoid generating denormals, infinities, etc.

I think making the fp using code have to be written carefully to work with the software emulation of edge cases is unusual -- I don't think either sparc or arm imposed that requirement, and instead trap precisely, or at least before anything happens where it would matter that the fp insn is emulated late.

Personally I have always felt that most Japanese cities are very devoid of urban greenery compared to UK towns and cities.