That guy breaking his contracts and agreements?

How preposterous!

As a Conservationist I'm a big fan of game preserves.

Who at Nintendo is coordinating donations?

I have a preserve just a mile up the way from me.

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.

As long as the US State Department is letting the "Chinese Spy" stay in the US we need to question the narrative

France wants the US to enter its war against Russia directly so it's trying to merge the Ukraine and Iran conflicts.

Ukraine already attacked an Iran boat to curry favor but backed off when Iran threatened missile strikes.

El Cheeto is participating by saying 'he' will blockade Iranian commerce in the Caspian Sea.

US has no assets there but Ukraine has long range drones and Flamingo missiles.

"Iran melted our ice cream" is a freebie to the DC Warmongers' narrative.

It'll help Macron get the ECB job he wants.

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")

Feds: Chinese spy.
Also feds: Not revoking her visa.

Hrmmm.

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.

> look at McCoy's face in the background of the car accident scene. That's the level of degredation in images in the PDF text format.

Holy smokes, thanks for mentioning that.

I figured the _text.pdf was just a merge of the pdf with the OCR text. Why in the world...

This seems to work:

```
pipx install internetarchive
ia download --search 'collection:starlogmagazine' --glob="*.pdf|*_djvu.txt" --exclude="*_text.pdf"
```

If you really wanted to you could get the raw OCR files and figure out how to recombine them ... I'll settle for grep.

Transfer speed seems to be capped at about 500KBps. Party like it's Frame Relay days.

Younger folks could engage in some real cultural anthropology of their grandparents' time.

The repo will just shrink as more packages take on some LLM patches. This doesn't make practical sense.

It's worth reviewing the ongoing battles between DeVault and Lunduke and you decide who is telling the truth. e.g. Stallman-report.org .

Just do a web search - DDG gets the headlines at least.