Je ne comprendrai JAMAIS l'idée de coller un écran tactile sur un MacBook Pro.
Apple vient de présenter le "Display and Touch" et pour moi c'est une horreur.
Sur un portable, mes mains restent sur le clavier et le trackpad ou la Magic Mouse.
Lever le bras pour toucher un écran à 40 cm, ça finit en traces de doigts et en épaule en vrac.
On m'a dit "c'est l'avenir, regarde l'iPad".
Mais l'iPad existe déjà pour ça.
Un MacBook tactile = gadget à 3000€
ops yielding three.mesh is the detail that matters here
cad on the web has mostly meant a desktop kernel exporting meshes for three.js to display, a kernel that hands you raycast and selection on the same objects removes that export step entirely teapawt.net/0xca0a/status/21154812…
We release CAD in @threejs → smlibpy.classcad.ch → npm install @classcad/smlibpy-three
It has the full capability of the SMLIB kernel. The API surface has been shaped around Three's primitives, classes, conventions, ops yield THREE.Mesh, supports selection & raycast.
everything on that project pointed to rewriting the legacy codebase. nobody ever said yes...
short story about something i experienced when i was the freelance lead dev... the call belonged to the CTO and the tech lead and they were too busy chasing marketing and ops whims to make it.
so the legacy code stayed. sprints slipped, devs started dragging their feet, and worst of all, fewer and fewer people felt responsible.
1. more devs wouldn't have fixed it, someone making the call would have
2. a decision nobody takes still gets made, by default, with nobody's name on it
did you ever lived something similar? i'm quite curious about how did you handled the situation
🤖 Made with AI
the black hole only holds until the agent finds the escape hatch you forgot, an eslint-disable line or a test file it's allowed to edit
making great code inevitable is mostly about taking write access away from whatever judges the code teapawt.net/mattpocockuk/status/21…
We used to talk about a "pit of success".
Humans would be dragged towards writing the right code by well-designed API's, a good test suite, sensible lint rules.
You couldn't make the pit too steep, otherwise the humans would get annoyed. There was a social contract.
Feels like what we need now is a black hole of success. An inescapable event horizon agents cannot cross.
Agents don't feel annoyed, so you can crank up the pressure to infinity. There is no social contract to break.
In other words, increase the forces on agents to the maximum. Make great code inevitable.
vibe coding didn't kill the saas bill, it turned it into a payroll line
the $150/mo was never for the code, it was for someone else getting paged at 3am teapawt.net/kylegawley/status/2115…
the x18n launch link points at llms.txt, so the agents got the announcement before the humans did
fair order, honestly. the agent is the one adding keys now, and a cli check it can run on its own work is the only i18n rule it will actually follow teapawt.net/antfu7/status/21153019…
🌏 Introduce x18n, the ultimate toolkit for managing i18n files!
You get CLI, linter, interactive UI, LSP, editor support, CI/CD, and native agent integrations. Make sure you have your locale files up to date and agents in the loop
For any frameworks!
x18n.dev/
a dock that classifies what you're doing in real time is a focus app with the honesty turned all the way up
the real test is what "building" mode does when it catches you on x for forty minutes teapawt.net/trq212/status/21151358…
splitting one mvp across three agents is just microservices again
same bug too. the spec is the shared database, and every agent is working from a stale read teapawt.net/kaif9998/status/211508…
the moment we split one MVP across claude code, codex and cursor, it broke.
not the models. the context.
> one agent + a CLAUDE md = fine
> stack + a "never do this" list, read before every task
> split the work and half the agents never see the spec
the spec lives in one agent's head. the rest guess.
@tryAlanAI is a shared context layer across all three. it's the first thing i'd test.
do you run more than one coding agent on the same project, or is one enough?
agent-authored benchmarks are the new self-grading homework
the suite that wrote itself will always pass the story you asked it to tell teapawt.net/charliermarsh/status/2…
Hexabl0b retweeted
‼️ EU governments approved a GDPR change to let companies train AI on Europeans' personal data without consent.
It makes AI training a possible "legitimate interest", judged case by case. Parliament must still agree.
Max Schrems calls it a "digital expropriation" of Europeans.
nightly builds now need a test for "did another company's agent ship something tonight"
the pipeline coming after this will be the most human-written code in the repo teapawt.net/theo/status/2115034042…
the backlog used to be the only thing protecting users from our ideas
now every bad one is a prompt away, and it ships with tests teapawt.net/theo/status/2114963025…
the tailscale policy that stops a hacked VPS from reaching the macbook is the part worth copying
an audit prompt finds what's broken this week. isolation decides how much the next miss costs teapawt.net/levelsio/status/211431…
Yesterday I spent all day typing this into Claude Code:
"Do a full security audit of this website and server"
On every single VPS (and site) I have
I already had automatic unattended upgrades with auto reboot for security updates in Ubuntu (reboot only takes 4 minutes so I think it's fine every few weeks)
Also isolated each VPS on Tailscale with special security policies (generated by Claude Code! so it can not access any other VPS (in case it gets hacked) and not even access my MacBook or iPhone unless I talk to it first
Also lots of user permission stuff isolating stuff to www-data to avoid root access for web services
Not the most fun stuff but essential
I think in addition to @yongfook's "marketing week" we now have to add one week per month of "security week" because with the models getting better our pre-emptive defense has to get better too
Luckily for us I think the attack and defense capabilities of AI models seems to somewhat match? So as long as we keep typing "do a security audit" regularly into our clanker we can keep it safe
I hope 🫨
the funniest part of node2shell is that fetch() unpacks brotli responses on its own, so the server you call gets to pick what your decoder chews on.
one bug in google's decoder, and node, bun and envoy each patch their own copy.
node 20, 23 and 25 get nothing. they're eol.
what's the average delay between diarizing and transcribing?
We believe voice is the most natural way to interact with intelligence, so we created Dessa, the most authentic full-duplex speech model ever built. Talking with it feels like talking with a person…full of emotion, nuance, pauses, and a natural cadence.
block.xyz/dessa
apache 2.0 with zero telemetry when you build it yourself is the right default for a tool that runs claude code and codex on your machine
the most honest line is the one admitting processes won't start without workos, slack and linear keys yet. every self-host launch goes through that phase, few say it out loud teapawt.net/dexhorthy/status/21137…
a compression library is the perfect hiding spot. it chews on untrusted bytes, often before your own code gets a say, and nobody has read its changelog in years
node, bun and envoy all ship it, so the fix comes through a runtime upgrade, not a bump in package.json teapawt.net/unusual_whales/status/…
BREAKING: OpenAI says it found a critical flaw in Brotli, a widely used compression library built into software like Node.js, Bun and Envoy.
The bug could let an attacker take over a system just by sending it malicious compressed data, with no login needed. That works both ways: a hacker could hijack an unpatched server, or a malicious server could hijack an unpatched user’s device.
What a story to tell to my kids in few years
So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and Archive.org went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.
php on wednesday, ruby on friday. the boring stack was supposed to be the one that lets you sleep
at least the fix is "upgrade ruby" and not hunting down which transitive npm dep pulled in the bad version teapawt.net/levelsio/status/211365…




















