12,250 karma · joined February 22, 2014
topcolor: 77dd44
[ my public key: https://keybase.io/striking; my proof: https://keybase.io/striking/sigs/QKCbMGAwCajv-YwVw78Vp00WB1YoOhCJyxc_nB-zW3U ]
I speak for the trees, for they have no tongues (unlike any of my employers; be they past, present, or future; for they have legal teams)
But it should be just as obvious that there are plenty of immigrants who are also necessary because they bring new ideas, their education, their incredible work ethic, to fill in the gaps that the US clearly has.
There is one thing that unites all of us (and I do mean us, as I am one of them). We all dream of a society where our hard work can become prosperity for ourselves and for everyone else, a plot of fertile soil that is worth sowing. We all come here with a dream.
And I personally don't mind so much that I'm uplifting people that don't agree with my existence. I just wish that they could stay out of our way so we could all benefit.
Unfortunately, the license actually in the repo is not even a not-quite-Apache-2 license. It doesn't appear to be FSL-1.1-ALv2 at all: https://github.com/statewright/statewright/blob/main/plugins.... This notably does not include the patent grant, which makes it unclear whether use of the software would infringe upon the patent.
For example, consider a lint rule that bans Kysely queries on certain tables from existing outside of a specific folder. You'd write a rule like this in an effort to pull reads and writes on a certain domain into one place, hoping you can just hand the lint violations to your AI agent and it would split your queries into service calls as needed.
And at first, it will appear to have Just Worked™. You are feeling the AGI. Right up until you start to review the output carefully. Because there are now little discrepancies in the new queries written (like not distinguishing between calls to the primary vs. the replica, missing the point of a certain LIMIT or ORDER BY clause, failing to appropriately rewrite a condition or SELECT, etc.) You run a few more reviewer agent passes over it, but realize your efforts are entirely in vain... because even if the reviewer agent fixes 10 or 20 or 30 of the issues, you can still never fully trust the output.
As someone with experience in doing this kind of thing before AI, I went back to doing it the old way: using a codemod to rewrite the code automatically using a series of rules. AI can write the codemod, AI can help me evaluate the results, but actually having it apply all of the few hundred changes automatically led to a lack of my ability to trust the output. And I suspect that will continue to be true for some time.
This industry needs a "verification layer" that, as far as I know, it does not have yet. Some part of me hopes that someone will reply to this comment with a counterexample, because I could sorely use one.
> Short-lived certificates are opt-in and we have no plan to make them the default at this time. Subscribers that have fully automated their renewal process should be able to switch to short-lived certificates easily if they wish, but we understand that not everyone is in that position and generally comfortable with this significantly shorter lifetime. We hope that over time everyone moves to automated solutions and we can demonstrate that short-lived certificates work well.
https://letsencrypt.org/2026/01/15/6day-and-ip-general-avail...
> No one person or team really made a mistake here, but with the benefit of hindsight it's clear the attackers perceived that the left hand of Debian/Fedora SSH did not know what the right hand of xz-utils was doing.
with OpenBSD not even being mentioned here
> These patches never went into Portable OpenSSH, because the Portable OpenSSH folks were ["not interested in taking a dependency on libsystemd"](link). And they never went into upstream OpenSSH, because OpenBSD doesn't have any need to support SystemD.
The language may have been harsher than it needed to and therefore could be more easily misunderstood, but I believe you are actually in agreement with them
The real question is if you have enough patience to power through making it work.
From this line of reasoning, my guess is that the huge discount is not so much intended to sell the data collection system as much as it is intended to sell the model. If you had to wring a geopolitical consequence from this, it would be that the US labs producing models would be impacted by a vastly less expensive competitor.
I'm clearly not the only one who thinks so, judging by both Amtrak ridership statistics and the cost ineffective nature of my attempts to travel on it.
> “Supply chain risk” means the risk that an adversary may sabotage, maliciously introduce unwanted function, or otherwise subvert the design, integrity, manufacturing, production, distribution, installation, operation, or maintenance of a covered system so as to surveil, deny, disrupt, or otherwise degrade the function, use, or operation of such system (see 10 U.S.C. 3252). (https://www.acquisition.gov/dfars/subpart-239.73-requirement...)
There's a little bit of leeway here, but this definition means either the company is an adversary (or an extension of one, e.g. Huawei/the CCP) or is under threat of being compromised by an adversary.
So which is Anthropic? Well, neither: the government's court filings and public comments in the media claim that Anthropic has an "adversarial posture". They want to simultaneously get away with bucketing Anthropic under the statute for adversaries, but without calling Anthropic an adversary directly in a court of law. They want to apply the statute without needing to follow the actual definition of an adversary.
From a CNBC interview:
> We can't have a company that has a different policy preference that is baked into the model through its constitution, its soul, its policy preferences, pollute the supply chain so our warfighters are getting ineffective weapons, ineffective body armor, ineffective protection. That's really where the supply chain risk designation came from. (https://www.cnbc.com/2026/03/12/anthropic-claude-emil-michae...)
That's why the judge rightly called this situation Orwellian: we're looking at linguistic sleight of hand designed to allow the government to turn what is a simple contract dispute into a company-threatening classification that threatens to uproot them entirely from any company that does business with the most powerful entity in the United States. Because Anthropic doesn't want to do the government's bidding despite being allowed to as a matter of freedom of speech, they are being threatened with a punishment that goes beyond just not being able to contract directly with the government. And that's not fair.
I would also love to understand why you keep going back to the literal events of the book. You don't need to be locked in a room and forced to claim that 2+2=5 for your situation to be Orwellian.
from https://openai.com/index/introducing-gpt-5-3-codex-spark/, emphasis mine
> When you rotate ")" counterclockwise 90°, it becomes a wide, upward-opening arc — like ⌣.
but I'm pretty sure that's what you get if you rotate it clockwise.
Why am I confident that it's not actually doing spatial reasoning? At least in the case of Claude Opus 4.6, it also confidently replies "umbrella" even when you tell it to put the parenthesis under the J, with a handy diagram clearly proving itself wrong: https://claude.ai/share/497ad081-c73f-44d7-96db-cec33e6c0ae3 . Here's me specifically asking for the three key points above: https://claude.ai/share/b529f15b-0dfe-4662-9f18-97363f7971d1
I feel like I have a pretty good intuition of what's happening here based on my understanding of the underlying mathematical mechanics.
Edit: I poked at it a little longer and I was able to get some more specific matches to source material binding the concept of umbrellas being drawn using the letter J: https://claude.ai/share/f8bb90c3-b1a6-4d82-a8ba-2b8da769241e
Is there anything to be gained from following a line of reasoning that basically says LLMs are incomprehensible, full stop?
3DSes require a little more work and have a longer boot chain, but it's been thoroughly broken all the way to the bootstrapping process so you can use whichever firmware version and whatever patches you like with enough effort.