Xin

hacking stuff • opinions are my own • AI @ Bloomberg • 💻 hooman of lovely Shiba ユミ🐶 🐕 📷🧑🏻‍💻

[Xin @_imfing]

got my brand new toy - Codex Micro keyboard ⌨️✌️

[Xin @_imfing]

@andymadrick @cursor_ai Neat, what was the book in the back 👀

[Kimi.ai @Kimi_Moonshot]

Introducing Kimi K3: Open Frontier Intelligence

🔹 2.8 Trillion Parameters, 1 Million Context, Native Multimodal
🔹 Kimi Delta Attention enables up to 6.3x faster decoding in million-token contexts
🔹 Attention Residuals deliver ~25% higher training efficiency at <2% additional cost
🔹 Built for long-horizon agentic coding and self-evolving workflows

Kimi K3 is now live on on https://t.co/zrk6zZxZUo, Kimi Work, Kimi Code, and the Kimi API.
Open Weights by July 27, 2026.

🔗 API: https://t.co/XCrgjXAqMw
🔗 Tech blog: https://t.co/YTfiMSNM1f

[Armin Ronacher ⇌ @mitsuhiko]

Some thoughts of mine that nobody asked for on the EU's fight with Apple and my worries related to Mythos and Fable. https://t.co/6dT7FXoEVf

[NomoreID @Hangsiin]

When Fable 5 is used for frontier LLM development, it does not notify the user and instead limits the model’s capabilities through methods such as prompt modification, steering vectors, and PEFT.

Anthropic estimated that this would affect approximately 0.03% of traffic.

[Xin @_imfing]

lol there's mandatory data retention for 30 days 🙃

[Claude @claudeai]

Introducing Claude Fable 5: a Mythos-class model that we’ve made safe for general use.

Its capabilities exceed those of any model we’ve ever made generally available.

[Guohao Li 🐫 @guohao_li]

Impressed by Anthropic's customer service. We paid for one year subscription for the team plan. Our org was disabled for unknown reasons. Three weeks have passed. Many appeals. No refund. No reply.

[Xin @_imfing]

@jarredsumner dynamic workflow for blog post too? 👀

[Xin @_imfing]

inspired by this, built an offline, single-binary cli version of diffshub in Go 🫡
https://t.co/j3Y87g394m

[Pierre @pierrecomputer]

diffshub[dot]com

Take any public diff from GitHub and virtualize it nearly instantly, no matter how large, with DiffsHub. Built to show off our brand new CodeView component.

To try it out, replace `github` with `diffshub` in your address bar.

[Xin @_imfing]

@pierrecomputer the music is 🔥

[Xin @_imfing]

impressive

[OpenAI @OpenAI]

Today, we share a breakthrough on the planar unit distance problem, a famous open question first posed by Paul Erdős in 1946.

For nearly 80 years, mathematicians believed the best possible solutions looked roughly like square grids.

An OpenAI model has now disproved that belief, discovering an entirely new family of constructions that performs better.

This marks the first time AI has autonomously solved a prominent open problem central to a field of mathematics.

[Mitchell Hashimoto @mitchellh]

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.

I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).

It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.

The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.

We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.

I worry.

[Xin @_imfing]

@ClaudeDevs Calling this “dedicated monthly credit” is such misleading marketing spin

this is a brutal rug pull dressed up as a feature 🙃

[Xin @_imfing]

super cool!

[Thinking Machines @thinkymachines]

People talk, listen, watch, think, and collaborate at the same time, in real time. We've designed an AI that works with people the same way.

We share our approach, early results, and a quick look at our model in action.

https://t.co/AFJZ5kH7Ku

[Xin @_imfing]

@claudeai claude for xbox when? 🫣

[Xin @_imfing]

was github down twice today — yes 🙃

[Xin @_imfing]

@claudeai @SpaceX https://t.co/Lidi9pIChJ

guess it’s time to unban spacex from using claude

[Kylie Robison @kyliebytes]

Scoop: xAI staff had been using Anthropic’s models internally through Cursor—until Anthropic cut off the startup’s access this week.​​​​​​​​​​​​​​​​

Here’s what xAI cofounder Tony Wu sent to staff on Wednesday according to a copy of the internal Slack message I viewed:

“Hi team, I believe many of you have already discovered that anthropic models are not responding on cursor. According to cursor this is a new policy anthropic is enforcing for all its major competitors.

This is a both bad and good news. We will get a hit on productivity, but it rly pushes us to develop our own coding product / models. We're at a time in which Al is now a critical technology for our own productivity. This coming year is rly going to be wildly exciting for all of us.

The team is rapidly developing our own models / product. We will have something to share with everyone soon. In the meantime, you may still try all different kinds of models in grok build.”

Anthropic declined to comment. A Cursor spokesperson directed me to Anthropic for comment. xAI did not respond to request for comment.

[Xin @_imfing]

@OpenAIDevs 🐶

[Xin @_imfing]

finally figured out how to reset my forgotten sudo password

[International Cyber Digest @IntCyberDigest]

‼️🚨 BREAKING: An AI found a Linux kernel zero-day that roots every distribution since 2017. The exploit fits in 732 bytes of Python. Patch your kernel ASAP.

The vulnerability is CVE-2026-31431, nicknamed "Copy Fail," disclosed today by Theori. It has been sitting quietly in the Linux kernel for nine years.

Most Linux privilege-escalation bugs are picky. They need a precise timing window (a "race"), or specific kernel addresses leaked from somewhere, or careful tuning per distribution. Copy Fail needs none of that. It is a straight-line logic mistake that works on the first try, every time, on every mainstream Linux box.

The attacker just needs a normal user account on the machine. From there, the script asks the kernel to do some encryption work, abuses how that work is wired up, and ends up writing 4 bytes into a memory area called the "page cache" (Linux's high-speed copy of files in RAM). Those 4 bytes can be aimed at any program the system trusts, like /usr/bin/su, the shortcut to becoming root.

Result: the next time anyone runs that program, it lets the attacker in as root.

What should worry most: the corruption never touches the file on disk. It only exists in Linux's in-memory copy of that file. If you imaged the hard drive afterwards, the on-disk file would match the official package hash exactly. Reboot the machine, or just put it under memory pressure (any normal system load that needs the RAM), and the cached copy reloads fresh from disk.

Containers do not help either. The page cache is shared across the whole host, so a process inside a container can use this bug to compromise the underlying server and reach into other tenants.

The original sin was a 2017 "in-place optimization" in a kernel crypto module called algif_aead. It was meant to make encryption slightly faster. The change broke a critical safety assumption, and nobody noticed for nine years. That bug then rode every kernel update from 2017 to today.

This vulnerability affects the following:
🔴 Shared servers (dev boxes, jump hosts, build servers): any user becomes root
🔴 Kubernetes and container clusters: one compromised pod escapes to the host
🔴 CI runners (GitHub Actions, GitLab, Jenkins): a malicious pull request becomes root on the runner
🔴 Cloud platforms running user code (notebooks, agent sandboxes, serverless functions): a tenant becomes host root

Timeline:
🔴 March 23, 2026: reported to the Linux kernel security team
🔴 April 1: patch committed to mainline (commit a664bf3d603d)
🔴 April 22: CVE assigned
🔴 April 29: public disclosure

Mitigation: update your kernel to a build that includes mainline commit a664bf3d603d. If you cannot patch immediately, turn off the vulnerable module:

echo "install algif_aead /bin/false" > /etc/modprobe.d/disable-algif.conf
rmmod algif_aead 2>/dev/null || true

For environments that run untrusted code (containers, sandboxes, CI runners), block access to the kernel's AF_ALG crypto interface entirely, even after patching. Almost nothing legitimate needs it, and blocking it shuts the door on this whole class of bug...

[Xin @_imfing]

@GergelyOrosz it’s a matter of time, Cursor switched over last year which already proved the subsidized usage is not sustainable https://t.co/Njgc5t411a