Map of agricultural production changes in the nuclear winter following a minor nuclear exchange, posted for no particular reason.

(For a full-scale exchange...)

Also, for no particular reason, a map of Russia's population distribution, alongside a reminder of Russia's nuclear missile failure rate, particularly booster failures. And that nuclear warheads have been commonly lost disturbingly often even during peacetime, with at least seven weapons from four incidents lost in flight landing in a way that left them fully intact and easily reparable, just from the US alone. And that Ukraine is rich in nuclear engineers, including still some retirees who worked in the Soviet nuclear weapons programme.

There's also this myth that "if you just use a nuclear weapon, you automatically win the war". Nuclear weapons are immensely effective terror weapons, but their effectiveness on the front is a lot weaker than most people think. People on frontlines tend to be in trenches, bunkers, basements, armoured vehicles, etc, and can be surprisingly close to a tactical nuclear blast while still surviving. They're effective against hard points but struggle against a broad, diffuse front (aka, today's front, which is a sparsely populated, deep, amorphous zone, thanks to drones). Amortizing Russia's estimated budget for tactical nuclear weapons comes up with ~$15-25M per weapon (not counting the delivery system), so they're hardly a dime a dozen either.

IF, via terror bombing or threats of terror bombing, you can convince your enemy to surrender, then congratulations, you have won (enjoy your nuclear waste heap and restive population who wants nothing more than to kill you). If they do not, however, their only goal remaining will be to focus 100% on using their extensive nuclear waste supplies rich in plutonium, their extensive long-range strike weapon supplies, and their extensive metallurgical experience, to render your major cities to ash in the same way that you did theirs.

(I also just assume herein that Ukraine doesn't actually have a secret nuclear weapons programme already, which is certainly an assumption).

I look forward to the unplanned broadcast of Swan Lake.

Mail all the rotting meat to them.

Nah....just all the PORK, and associated liquids and blood.

And maybe air drop it rather than mail it....that'll get them where it hurts.

To me, that is basically an acoustic Stockholm syndrome. Motorcycles with their open engines are necessarily very loud to the rider. Like the hostages start to love their captor, motorcycle riders start to love the sound to cope with the fact that they can't flee it.

From that,I'm guessing you are not a biker.

And as the old saying goes..."..if I have to explain it to you....you wouldn't understand.."

That's now throwing shade at you, mind you.....it's just if you aren't of the biker mind, you likely won't "get it".

To be clear: you can still totally argue about qualia, sentience, things of that nature. What is not up for debate is that they work through unimaginably-complex chains of logical reasoning on superpositions of conceptual states and engage in forward-planning and metacognition. These are just demonstrable facts.

There is no 'sentiment' in an LLM or internal state equivalent to 'thinking' anything.

Yes, there is.

Ugh....I dread the day when all you can get is a silent electric motorcycle....

Half the fun of one is the sounds and smells and vibrations it gives you....a visceral experience.

No, it's called "Evidencing The Fact That It's A Widespread Shorthand" (in specific, among Wikipedians, where it's in official terminology as well), a widespread usage that was falsely claimed to not exist.

(I'll also take this opportunity to note: rage about the use of shorthand on "copyvio", but not a word about "algos")

Oh wait, second hand EV prices have gone Up as people try to avoid paying high petrol prices

Must be a EU thing.

In the US, the used EV prices are still tanking (no pun intended)....you drive an EV off the lot here in the US, you are pretty much guaranteed to be close to upside down in it immediately.

Then walk - When people being up "I can't charge, I live in an apartment" as some sort of reason to not make EV's, I have to chuckle. I don't have space to put in a Dump truck, that doesn't mean they shouldn't exist.

I know you jest....as that "walking" for most folks isnt' a viable option at all.

I think the main thing is....while there are significant number of folks that can NOT charge at home for various reasons, people should not be penalized for sticking with ICE vehicles which still server them quite well.

Shorthand should be something that other people actually use

Okay Felicia.

TL/DR: "copyvio" is the Wikipedia-standard shorthand for copyright violation, used both in direct speech and in official templates. If a person says "copyvio", they've probably spent a lot of time hanging out at Wikipedia, where copyright violation is a frequent topic of discussion.

I'm sorry if shorthand offends your sensibilities. Should I spell out all shorthand for you? Maybe make sure I only use emdashes instead of "-" while I'm at it?

Oh, also, as pointed out further downthread, any LLM with a training cutoff before the license change date is pretty much assured to be okay for use in a cleanroom implementation. Copyright holders cannot make retroactive copyright changes, and open source licenses generally explicitly grant rights in perpetuity anyway. The threat would be new code. But since the cleanroom side has never seen that new code (it was released after the training date), it remains untainted. And training cutoffs generally lag model releases by many months, so not only should all current models be in the clear, but most next-gen models as well (subject to cutoff date verification, and various kinds of nuance such as avoiding RAG, potential post-training contamination, etc - but there's easy ways to guarantee these aren't problems that are present)

First off, you can always just use a LLM with an open training dataset (OLMo, Pythia, etc) to prove that the data isn't in it, and have that handle the "clean" side of the equation.

Secondly, you are under the mistaken impression that a LLM that has been exposed (which, BTW, does not mean "memorized", or even any rough understandings of the workings - ask the LLM (ideally an abliterated one to avoid refusals) to reproduce the original code verbatim, it'll almost certainly fail badly) automatically fails in such a suit. It does not. There is no such thing as "homeopathic copyright contamination". Copyvio requires substantial similarity. LLMs will tend to have common algos memorized, but those are the very things that tend to be simultaneously not copyrightable.

The cleanroom is an evidentiary shield, not a pillar of copyright law. If you can prove that the cleanroom team had no access to the original, then you can prove that they didn't copy it, and potentially get summary judgement. If you can't prove that, that doesn't mean that it's not copyvio, it just means that you instead have to focus on substantial-similarity defenses. Access without substantial similiarity is not copyvio. If you read an open-source codebase, close it, and then later write a new program purely on your own that looks nothing like the original, you had "access", but still did not infringe. The same applies to LLMs - but even moreso, because humans are much better at learning from brief, limited exposures to content than LLMs are. A court will usually apply an "Abstraction-Filtration-Comparison" test - they break the code down into layers (source code, parameters, architecture, algos, etc) (abstraction), remove everything that copyright law does not protect (ideas and common algos, things where there's only a limited number of ways to possibly do it, etc) (filtration), and then compare the creative expression that remains to see if there exists sufficient similarity to count as infringement. It is highly unlikely that a LLM-implemented version will fail that.

(That said, you're talking about a long, expensive legal battle if you get to that point, so you obviously prefer to be able to get summary judgement if you can)

What the GP described is known as a cleanroom implementation, and it's perfectly legal, and has been done many times in ways that have been upheld by the courts. The dividing line, by and large, is that the documentation has to be flexible enough that there's multiple potential ways it could be implemented, that you're not just transforming a code flow into "text pseudocode" and back. It doesn't matter if, by chance, it looks like the original - only that there were multiple means by which it could have been done under the specification produced.

There's also some various process-specific factors you need to manage - full separation of the teardown and cleanroom-implementation teams, a judge filtering all communications (with an audit trail) back and forth between the teams to make sure that they meet legal standards of separation, things of that nature. But a competent LLM can help set up the process and run each agent for each role in its own isolated context.