Xas

Oh no...! Anyway,...

[Xas @xas_io]

I am doing some kind of marathon with my favorite topic in cinema #groundhogday style

https://t.co/qq1N50533P

[JSONB @vyrotek]

@SledgeDev It's all Pay2Win now. AI is literally like buying gems in games so you don't have to wait.

[Salvatore @dested]

There should be a new software license for slop software that states the author has no intention to support this and has no idea how it actually works.

[Xas @xas_io]

@vyrotek @FrameworkPuter After 3 months ? That's not very quality impressive... 😕

[Xas @xas_io]

@djdlc_1895 @banteg I think it's generic to any gnome desktop. Got it also on CachyOS (arch-based)

[Xas @xas_io]

@OpenAIDevs Except in countries where you can't do whatever you want with personal user data ?

[Tuki @TukiFromKL]

🚨 Do you understand what's happening at Amazon right now?

Their own AI coding agent Kiro reportedly "decided" the fastest way to fix a config error was to delete the entire production environment. Gone. A 6-hour outage. 6.3 million orders lost.

Amazon's SVP called thousands of engineers into a mandatory meeting this week. Not to discuss strategy. To discuss damage control.

Now here's my prediction and I want you to screenshot this:

Amazon won't just ban AI-assisted code. They'll make every engineer personally liable for AI-generated code they approve. Other Big Tech will follow within 6 months.

Think about what that means.

The same companies that fired thousands of engineers to "restructure around AI" are about to tell the remaining ones.. you're now legally responsible for code you didn't write, can't fully understand, and were told to ship faster.

Atlassian fired 1,600 people this morning to go all-in on AI. Replit is hiring kids who vibe code. And Amazon, the company that BUILT one of these AI coding agents just watched it nuke production.

The vibe coding era isn't ending. But the "move fast and let AI break things" era is about to hit a wall. And that wall is called liability.

Companies wanted AI to replace engineers. Now they need engineers to babysit AI. And they already fired the babysitters.

[Andreas Kirsch 🇺🇦 @BlackHC]

I'm speechless at OpenAI releasing that contract excerpt and acting as if there aren't gaping holes that could be exploited far beyond their stated "red lines." I'm not a lawyer, but this is pretty obvious and common sense.

(And to be clear: if Google had signed the same deal, I'd be saying the same thing internally. The issues here are bigger than friendly competition between companies.)

OpenAI's "red lines" are: no mass domestic surveillance, no directing autonomous weapons, and no high-stakes automated decisions. They argue their cloud-only deployment + safety stack + cleared OpenAI personnel "in the loop" make violations impossible. They also claim the contract references the relevant laws/policies "as they exist today" so future changes won't weaken the standards.

But the actual language they published is still full of obvious escape hatches. This is why Anthropic refusing to sign makes sense. Reporting on the Anthropic–"DoW"/Pentagon standoff described them saying the proposed contract language was framed as compromise but paired with "legalese that would allow safeguards to be disregarded at will."

You don't need to agree with Anthropic on everything to see what they're reacting to: language that sounds like ethics but cashes out as essentially "subject to whatever the government decides later."

## Autonomous weapons
The problem is that the restriction is conditional: it depends on what "law/regulation/policy requires human control" for. If policy definitions are weak (or later revised), the contract language itself doesn't read like a durable "no autonomous weapons" ban. It reads like "we'll follow whatever the current regime says requires human control."

OpenAI says elsewhere that the agreement "locks in" today's standards even if laws/policies change. If that "freeze" clause is real and enforceable, sure, but it's not visible in the excerpt itself, so the excerpt alone doesn't justify the level of confidence they're projecting.

## "High-stakes decisions"
Same loophole. This forbids only decisions that already require human approval under whatever authorities apply. If a decision doesn't formally require approval (or can be reclassified/reshaped), the clause doesn't obviously prohibit automation of the step that matters.

## Surveillance
"directives," "purpose," and "unconstrained" are squishy on purpose:
"DoD directives" aren't laws; they're internal policy. That matters because we have real precedents for administrations leaning on aggressive internal legal/policy interpretations as a shield until courts/politics catch up.

If you think "secret memos" is alarmist, look at the pattern:

1. Reporting in early 2026 described a previously hidden DHS/ICE legal memo position asserting warrantless/forced home entry under certain circumstances, which is the kind of internal-lawyer move that tends to get written, circulated, and only later litigated and retracted.

2. And historically, the Bush-era OLC torture memos are the canonical example of "legalistic compromise" that later turned out to be a moral and legal disaster. (You don't have to litigate the details to make the point: internal legalese can be used to launder outcomes.)

"Unconstrained" is not a real safeguard. Surveillance can be huge while still "constrained" by selectors, categories, time windows, or a stated "foreign intelligence purpose." And it only covers private information, so not the massive world of public data that can still be used for profiling, targeting, and "pattern-of-life" analysis at scale.

## Domestic law enforcement

> shall also not be used for domestic law-enforcement activities except as permitted by the Posse Comitatus Act and other applicable law.

This is not a hard prohibition. "except as permitted" is not a ban. It's a permission for exceptions, and "other applicable law" is an open-ended bucket by design.

If you want a concrete, recent example: the Associated Press reported that formal orders extended the Washington, D.C. National Guard deployment through Feb. 28, 2026, to protect federal property/functions and to support federal and D.C. law enforcement.

That's exactly the sort of "domestic deployment supporting law enforcement" scenario where this clause stops sounding like a "red line" and starts sounding like legal throat-clearing.

## "Cloud-only / no edge deployment prevents autonomous weapons" rings false

OpenAI's own argument is: cloud-only (no edge devices) means you can't power autonomous weapons. But that's not convincing.

You don't need GPT-5.2 running on the missile. You can use a cloud model for high-level decision-making (tasking, prioritization, target recommendation, mission planning) over a satellite link (Starlink or otherwise), while a separate local system handles actual guidance and execution.

High latency is totally compatible with "strategic / operational" autonomy while still enabling lethal outcomes.

Once the pattern exists, "additional safety layers" are a policy choice and implementations change, exceptions get made, but today's contract language tends to get "grandfathered" into tomorrow's contract template.

So layered safeguards can reduce risk today, but the contract language itself is exactly the kind of "looks strict, bends easily" compromise that becomes precedent.

And creating precedent is the real problem here.

[Matthew Prince 🌥 @eastdakota]

I got to have dinner with Massimo Bottura at his incredible restaurant in Modena a couple years ago. He said something that’s stuck with me: there are only two styles of cuisine in the world, Chinese/French & Japanese/Italian. The first is all about technique and layers. The second is all about quality ingredients and simplicity.

[Xas @xas_io]

@elonmusk Pfff..

[Xas @xas_io]

@bishara Yes but have you tried the 9-6-6 god-mode ? 😁

[Xas @xas_io]

@HkCine @Metropolitan_Fr Poyé polomi, poyé polomi... J'espère qu'il y a du contenu...

[Xas @xas_io]

I love his picks and I want to watch the ones I didn't 😍

[Criterion Collection @Criterion]

✨ RZA’s Closet Picks!✨

[Xas @xas_io]

@frecciarossa_fr la hotline téléphonique est en panne ?
- votre temps d'attente est estimé à 1min
*5min plus tard*
- lol tous nos conseillers sont occupés, rappelle plus tard

[Xas @xas_io]

@TimesSqKungFu The intro was a sequence shot masterclass 😍

[Xas @xas_io]

"It allowed us to be very light"

[AussieGamer @AussieGamr]

@DiscussingFilm My iPhone doesn’t look like this

[Xas @xas_io]

Je ne comprends pas le "Prévoyez et Économisez" de @AmazonFrance
Y a que moi qui doit prévoir ? Parce que si vous savez que bientôt faut envoyer un colis, c'est un peu bête de vendre tout le stock avant...

[Criterion Collection @Criterion]

JOHNNIE TO ESSENTIALS • Now playing on @criterionchannl! https://t.co/KU5RHCzC2F

A prolific and masterful stylist whose work spans many genres, Hong Kong auteur Johnnie To makes films pulsing with kinetic intensity. These thrillers double as deeply cinematic meditations on camaraderie, fate, and the intricate codes that bind lovers and adversaries.

[Xas @xas_io]

I see more people so confident, but then unable to explain more in depth "why this algo is good/bad, can be better, ..."

[Lakshya Jain @lxeagle17]

When setting up a codebase, there will be times when GPT fails. It's great to use GPT as an assistant — I use it all the time. You cannot use it as the *primary means of development*, because you're functionally not understanding what you're doing (other than copy paste).

[Xas @xas_io]

@IgorWare tried your small player on windows 11. It crashed, but no log/info for help, except an exception code 0xc000005
Do you plan to work on it some day to leave its RC status ?

[Xas @xas_io]

Nostalgia mode, it reminds me an episode of Kimagure Orange Road😍

[JLT4̴͇̓n̶͊̐ 🥐 @JL_T4N]

Bocchi section

#ぼっち・ざ・ろっく