Latest Posts (20 found)

YoloCam S7

Chris Enns shared in the ShopTalk Show Discord last month a review video for the YoloCam S7. It hit me at the right time, so I pulled the trigger. Here’s a short background. I was using my Canon 5D Mark IV with a 50mm prime lens . Kind of a lot of firepower for a webcam. I just had it around because, once in a while, I need to take some really high-quality photos or video. So I figured I’d put it to work on the daily instead of mostly gather dust. I liked the quality of the prime lens, but didn’t love the inability to zoom. I disliked not having my nice camera easily accessible to use for other things. I disliked that I had to pay a monthly fee to unlock 1080p video. I disliked that it required a special mock battery to be persistently plugged in. I disliked the weird HDMI cable it required. I really disliked having to stand up and reach behind my desk to hit the camera button to wake it up. Just enough to keep me from loving the setup. I had also used a Sony ZV1 in the past, which I bought just to be a webcam, and while it was nice quality, I ended up having gripes with it too, and ditched it when it started turning off at awkward times. What struck me about the ZV1 was essentially the price point. An obviously very high-quality device, with a high-but-not-crazy price point. I always thought there should be a webcam in this category that was actually designed to be a webcam, not a repurposed point-and-shoot. That’s exactly what the YoloCam S7 is, so when I saw the review, I thought I’d reward the company for doing exactly what I thought a company should do. The results? It’s mostly great! The quality is very good. I like how the camera body has almost nothing on it except a few ports. I like how the lens is swappable in case I wanna try something else. I like how it wakes up and works whenever I need it. The software has just enough control on it to be useful. I like the automatic face focus and reasonable zoom. There are a few little things I don’t like. I don’t like how you still need two cables coming out of it. They are both USB-C, but one is for power, and one is for connection 🤷‍♀️. I really dislike that the software can’t see the camera most of the time . When I open YoloLiv Compose, there is a 90% chance it can’t see the camera, even though other software that needs the camera uses it fine. I have to unplug it and plug it back in, and even then there’s only a 50% chance it works. When it does work, you can control what you need to, and it persists fine.

0 views

Embassytown

Avice Benner Cho has lately returned to Embassytown after spending years in the immer. As a child, she performed in a ceremony with the planet’s strange alien hosts, the Ariekene, becoming a simile in their Language, so that she returns a minor celebrity. Now, the town is soon to receive a new human Ambassador: two humans, or one human doubled, designed and trained to speak Language. But something has gone very wrong. In the chaos and war that follows, Avice and her human and alien counterparts must fight not only with weapons but with words, and with the very substance of Language itself. “We tell the truth best by becoming lies,” she learns. View this post on the web , reply via email , or become a supporter .

0 views

I'll Never Buy a Peugeot Ever Again!

So back in July I bought a nearly new Peugeot e-3008 from a Peugeot dealer near my home. I ranted about their shitty subscription model the day after I collected it, and since then it's gone from bad to worse. The new car A week or so after getting the car, my wife noticed a horrendous noise coming from the front of it, which couldn't really be heard from inside the car. It sounded like a jet engine - a very loud whirring noise. I thought nothing of it, just one of those noises cars make when they pull over , I thought. But then, a few days later, the climate control in the car completely stopped working - no heating or cooling. So 19 days after collecting the car, I reported the fault and booked it into the dealership. They confirmed the climate control system was fucked and needed to be replaced. Problem is, one of the parts they needed to replace as part of the repair is "non-commercialised". Which apparently means that the part is available in the factory, but not to the general public. Better yet, they had no timeline as to when the part would be available. Double bloody great. By early September, the car went back to the dealership permanently and they gave me a much smaller e-308, which is absolutely shite and far too small for my needs. I'm a co-carer for my disabled brother, who uses a wheelchair. He can't get into the lower car easily, and there's no chance of getting his wheelchair in the boot, so it's been a nightmare getting him to his various appointments. Still, it's a car, so I've had to make it work. That was over 11 weeks ago at the time of writing this and I still don't have an ETA for the repair, let alone my car back! Long story short, I complained to Peugeot UK, who have been utterly useless. Although they confirmed the part is now "in the commercialisation stage" and that the dealership apparently ordered it in early September, there's still no ETA for the part's arrival. I concurrently complained to the finance company, Halifax, who have been even more useless. Under the Consumer Rights Act 2015, reporting the defect within the first 30 days paused my short-term right to reject—and because the law requires any repair to happen within a reasonable time and without significant inconvenience, having the car off the road indefinitely with no ETA on the part triggers my final right to reject. Put simply, I'm legally entitled to unwind the finance agreement and get a full refund, which Halifax has flatly refused to honour. I'm currently ~£2,800 in the hole thanks to finance payments for a car I don't have, and can't use. Halifax offered me a paltry £306.87 by way of compensation and told me I have to just sit and wait for the repair to happen. Fuck. That. Instead, I've exercised my right and filed a complaint with the Financial Ombudsman Service in the hope that I get the correct outcome per my statutory rights. Well, I just have to wait. But this whole saga has been ridiculous. I was expecting Peugeot to be useless since it's not in their best interest to take the car back. Plus there's a saying here in the UK "never buy a French car" . Should have heeded that advice... Anyway, I thought Halifax would have had my back, but it seems they don't want to do the right thing by their customer either. Even though I've banked with them for a couple of decades now. So much for customer loyalty, hey. My hope now is that the Ombudsman will be able to step in, sort this shit show out, and make me right again so I haven't lost out financially. Then I can give that green heap of shit back, and buy something more reliable. Thanks for reading this post via RSS. RSS is ace, and so are you. ❤️ You can reply to this post by email , or leave a comment .

0 views

CTO of ‘RansomwareHelp’ Indicted for Wire Fraud

The chief technology officer and co-founder of ransomwarehelp.com , a six year old Florida business that claimed to use “advanced cryptographic tools” to restore data locked by ransomware, has been charged with wire fraud after an FBI sting operation found the company was simply paying the attackers for a decryption key and charging victims a markup for work that was never performed. A portion of the now-defunct website ransomwarehelp.com. The website RansomwareHelp urged victims “Do not pay the ransom!,” claiming its advanced cryptographic tools could restore 100 percent of data, servers, and systems to their original format, and that there was no need to give in to extortion demands. “Our cryptography experts use proprietary tools and algorithms to achieve 100% data recovery, all backed by a success rate of over 99%,” the website enthused, claiming the company had over 28 years of experience and a team of 80 experts in cryptography, cybersecurity, forensic analysis and reverse engineering. “We never promote, intermediate or pay ransom to threat actors on behalf of our clients.” But according to an indictment (PDF) returned this week in Rhode Island, the company’s co-founder — 52-year-old Juan Ricardo Palacio Escobar of Miami and Medellin, Colombia — routinely paid ransomware groups for a decryption key to unlock victim data, and then charged those victims well above what he’d secretly paid the threat actors [Palacio’s indictment was reported earlier this week by 404 Media , but for some reason that story did not name the defendant’s company]. The indictment says the FBI set up a sting operation in which the feds were posing both as a ransomware victim company and as a fictitious ransomware group. Pretending to be victims of a cyberattack, investigators contacted RansomwareHelp and supplied the company with a copy of a phony ransomware note, saying they did not wish to pay a ransom. RansomwareHelp replied by reiterating its policy against negotiating with or making ransom payments to threat actors. The government said Palacio soon after contacted the fake ransomware group run by the FBI and requested the lowest possible price for the decryptor. FBI investigators responded with a price of .2 bitcoin, or around $13,000 at the time. Less than 48 hours later, Palacio allegedly told agents acting as the victim company that the diagnostic assessment was successful and that the cost of decrypting the files would be $13,260. The following day, the government alleges, Palacio messaged the fictitious ransomware group operated by the feds and asked to reduce the ransom demand to $4,000 for the purchase of a decryption tool. The indictment states that the agreed upon price was around $6,000 in bitcoin, and that Palacio charged the FBI’s fake victim firm $16,010, including an initial $2,750 diagnostic fee and the full fee of $13,260. Paul Ihme is co-founder of the security firm Soteria . Ihme told KrebsOnSecurity that in 2024 he heard from a small accounting firm that had paid RansomwareHelp a diagnostic fee to help recover from a Lockbit ransomware infection that had locked all of their company and client data. Ihme said RansomwareHelp sent a proposal to the victim with a recovery price of $438,880, which it claimed included “professional configuration of forensic servers,” “expert engineering hours of programming to configure decryption algorithms,” and “eight (6-hour processing cycles) related to the decryption process.” A portion of the proposal that RansomwareHelp sent to a victim accounting firm in March 2024. Click to enlarge. The proposal stated that the recovery process involved reverse engineering the ransomware encryption using “510 preconfigured forensic servers of the maximum quantitative capacity located in different parts of the world.” “Our programmers will inject randomly the encryption codes extracted during the forensic and cryptographic analysis using brute force processes,” the proposal claimed. Ihme said RansomwareHelp insisted that they be allowed unrestricted remote access into the victim’s network to run their diagnostic checks and analyses, using an Anydesk remote desktop software installer. Ihme believes RansomwareHelp insisted on that remote access in part so that the company could delete all copies of the ransomware notes left by the attackers on the victim’s network. A typical ransomware note is a plain text file that introduces the ransomware group and lays out their demands, and it includes a way to contact them — often an email address or a live chat session on a darknet website. In most cases, the attackers will leave a copy of the ransom note on every system on the victim network that gets locked. But Ihme said a review of the company’s network at the time found only one copy of the ransom note, which was unearthed from a backup snapshot on one of the infected computers. When they connected to the Lockbit chat server with the provided user ID, they discovered that someone had already been negotiating with the Lockbit extortionists for several days. A screenshot of a 2024 conversation between Lockbit and RansomwareHelp, which was secretly negotiating with the extortion group. Click to enlarge. “The charitable view would be to say that they were using Anydesk so they could grab the stuff they needed without having to walk the client through downloading and uploading a bunch of stuff,” Ihme said. “A legitimate firm would say, ‘Hey, send us a copy of the ransom note,’ which will have a link or URL to go to and chat with the threat actors. What they were doing is using that access to delete ransomware notes off the systems. The only reason they would do that is to prevent the victim from jumping into that chat itself.” Indeed, RansomwareHelp pleaded with the Lockbit group throughout the chat not to reveal to the victim that they were negotiating. However, Lockbit quickly grew annoyed with the length of the negotiations, replying that the victims had waited too long and that the ransom demand would increase by $100,000 for every day they dithered further. The Lockbit representative starts raising the ransom demand after multiple negotiators begin interacting with the threat actors. Click to enlarge. In the end, the accounting firm took Ihme’s advice and went with a more established security firm that helped them negotiate a payment to Lockbit. “The victim told us, ‘If we don’t get this data back, our business is over’,” Ihme recalled. “They ended up paying half of what RansomwareHelp was going to charge them.” The chats show RansomwareHelp kept pestering Lockbit to negotiate a deal even after it was clear a new negotiator was engaging with the ransomware group on the victim’s behalf. “I tell you something, that person who is negotiating with you for the other chat is damaging the whole process,” RansomwareHelp wrote to Lockbit. “Please do not change the price. I am doing my best to achieve it.” Ihme said RansomwareHelp primarily targeted small to medium sized businesses that weren’t particularly tech-savvy, noting that many of the technical claims made on the company’s website and in their proposal are patently farcical. For example, the proposal sent to the accounting firm said it could break six types of encryption, and then proceeded to list a number of irrelevant password hashing algorithms like SHA-256. “If it were really true these guys could decrypt any ransomware out there, this guy would be a billionaire,” Ihme said. “They were going after people who don’t have any technical knowledge, are desperate, and don’t have anyone advising them about how any of this stuff works.” The case against Palacio marks the latest in a string of recent prosecutions by the U.S. Department of Justice (DoJ) targeting security firms alleged to have conspired with fraudsters to defraud clients. In early October, the government charged 54-year-old Edward Dubrovsky , an executive at the Canadian cybersecurity firm Cybersteward. The government has sealed the case against Dubrovsky, but he is currently facing cyber extortion and conspiracy charges. Around the same time as Dubrovsky’s arrest, the DoJ charged MonsterCloud CEO Zohar Pinhasi , 50, with wire fraud and conspiracy for allegedly charging customers to remediate ransomware attacks without paying the hackers. According to charging documents, Pinhasi secretly went behind his customers’ backs and paid hackers anyway, paying ransomware groups $8 million while charging customers $19 million. In July, Angelo Martino , a 41-year-old ransomware negotiator from Land O’Lakes, Florida, was sentenced to 70 months in prison for conspiring with the Blackcat/ALPHV ransomware group to extort multiple victims. According to the DoJ, Martino was paid by BlackCat attackers to provide confidential information about the negotiating position and strategy of his employer’s clients and enable the ransomware actors to maximize the ransoms paid by the victims.

0 views
Stratechery Yesterday

2026.47: Down in DC

Welcome back to This Week in Stratechery! As a reminder, each week, every Friday, we’re sending out this overview of content in the Stratechery bundle; highlighted links are free for everyone . Additionally, you have complete control over what we send to you. If you don’t want to receive This Week in Stratechery emails (there is no podcast), please uncheck the box in your delivery settings . On that note, here were a few of our favorites this week. Presented by As AI models improve, you might expect the market will consolidate around a handful of providers. But user data tells a different story. Among OpenRouter customers spending at least $100 a month, the median number of AI model families in use has doubled over the past year , from three to six. Even as AI models become more capable, businesses are using more models, not fewer. This makes sense when you consider that intelligence isn’t one-dimensional. A model that’s exceptional at writing code may not be the fastest at answering customer questions, or the most economical at processing millions of documents. The question is shifting from “which AI model should we build on?” to “which model should handle each task?” The answer, increasingly, is ‘it depends.’ Which is great for flexibility, less great for simplicity. OpenRouter, which recently joined Stripe , allows businesses to access and govern hundreds of models with the flexibility to optimize for cost, performance, and reliability as the market evolves. Learn more at openrouter.ai . This week’s Sharp Tech is on Jensen’s Not Coming Back, Adventures in Agentic Commerce, Q&A on United, GTA VI, iPhone Duo . Obituaries and Exceptionalism. After several days to mull the shocking departure of Jensen Huang, Ben’s article on Monday delivered an omnibus obituary for a variety of American eras that may now be ending. Tracing the decisions that made Huang great, the strategies that made him a target, the implications of his demise for the rest of the tech ecosystem, and a shift in the U.S. government’s perspective on tech companies — and specifically AI companies — to which Huang never quite adapted, Monday’s piece was both comprehensive and poignant. — Andrew Sharp Arguments About Agents. Recurring Stratechery guest and advertising expert Eric Seufert is often aligned with Ben in his view of the digital advertising landscape, which is why this week’s Stratechery Interview was fun: Ben is a big believer in the potential upside in agentic commerce, while Eric has been (correctly) calling BS on a variety of hyped agentic commerce stories and trends over the past year. Both of them made their case Thursday, and it was sandwiched between thoughts on how Muse plans to monetize, why the market have misread Google’s recent earnings report, and ChatGPT’s progress building an ads business. — AS Ben Gets a Duo. In the middle of a heavy week of Nvidia takes and ominous infrastructure failures, I was delighted to find out that Ben not only purchased an iPhone Duo, but loved it . Come for his review at the end of Tuesday’s Update , and then stay for his discussion with John Gruber on Tuesday’s Dithering . We doubled back (Duo’d back?) to discuss all of it at the end of this week’s Sharp Tech , including some hands-on testing, comparisons to the iPhone Air, and a variety of shots fired at the iPhone Pro. — AS Obituaries — The demise of Jensen Huang was the end of a great many things, including Nvidia’s long-term prospects, the AI bubble, and the exceptional way in which the U.S. viewed itself in the world. Apple Permissions Update, The New App Paradigm, My iPhone Duo Review — Apple doesn’t ruin the Mac, but they don’t fix the agent problem, raising questions if they can think outside the app paradigm. Then, my iPhone Duo review. Nvidia Earnings; Office Convergence; OS Wars, AI Edition — Nvidia’s earnings were boring, and also a statement as to why Jensen Huang probably isn’t coming back; then, Microsoft and Anthropic ship dueling operating system updates. An Interview With Eric Seufert About Agentic Commerce — An interview with Eric Seufert about agentic commerce, including why he thinks ads will be the answer, and why I want retailers who cater to agents. Wizards Groundhog Day — Four more years of winter for basketball fans in Washington. Ben Gets a Duo GTA and Windows Apps The Rise and Fall of the Soviet Union’s Workhorse Computer TSMC Making 3D DRAM? The West Reigns Supreme (Again), The Micah Nori Sweepstakes, Trading Dejounte and Ice Earning Omissions Subscriber Mail: Intel, Anthropic’s IPO, Machiavellian Hyperscalers, and Push Notification Tyranny Jensen’s Not Coming Back, Adventures in Agentic Commerce, Q&A on United, GTA VI, iPhone Duo

0 views
Brain Baking Yesterday

Sinterklaas Writes With A Montblanc

As part of our yearly month-before-Christmas tradition, we re-watch early nineties local production TV show Dag Sinterklaas . I tried explaining the tradition last year in case you’re interested in weird Flemish/Dutch culture. Sinterklaas returns to Spain on the 6th of December where all little kids—correction, little kids who have been good—are gifted something to celebrate the Goedheiligen man (“good holy man” in English I guess?). Since there are 2x10 episodes of Dag Sinterklaas , last Monday marked the start of the tradition. In episode 3, Het boek van Sinterklaas (the book of Sinterklaas), Bart and Zwarte Piet are tasked with finding the book, glasses, and pen of a distracted Sint that claims Piet misplaced these items while in fact he did so himself. The horse Slecht Weer Vandaag (Bad Weather Today—yes, that’s the name of the horse, long story) tipped off the location of the book: inside the fridge. Bart almost breaks the Sint’s glasses while sitting on his bed. But it is the pen that interested me the most. Piet finds it on a shelf in the bathroom next to the shampoo. Piet finds the Sint's expensive pen in the bathroom. Zijn pen! Zijn dure pen! Ik, slordig? Ha! (His pen! His expensive pen! Me, carless? Ha!) In the next scene we see the duo returning to Sinterklaas where he explains what the book is about and how he writes in it. During the explanation he waves about with the black expensive looking pen with golden nib where, if you look closely, you’ll spot a distinct white mark on top of the cap. That’s right: the signature Montblanc mark. That mean only one thing: the Flemish 1992 version of Sinterklaas writes with a Montblanc. The Sint in denial: I didn't put those things there! Wait. Back up a minute. I recently read an article about world leaders and their signature pens. When it comes to holy men, I’m certain Sinterklaas should be added to that list of leaders on the spiritual (Christian) side. Aqeeb wrote in The Pens That Rule The World (sadly a Substack link) that King Charles III tried to write a guestbook with a leaky Montblanc. The result was recorded: “I can’t bear this bloody thing, every stinking time”. Ouch. But that was a special sterling silver edition. Montblanc’s flagship pen, the Meisterstück 149—the one I suspect is also the one Piet found in the Sint’s bathroom—is, according to Aqeeb’s article, “the pen chancellors and popes reach for. Konrad Adenauer used one. Helmut Kohl used one. A pope used one to sign his own resignation.”. Yet it is not just the popes: The 149 is the most common pen (highly duped/faked too) of its kind there is, the one a junior diplomat buys at duty-free before his first summit so he looks the part. The most powerful and the most nervous reach for the same pen. Perhaps the one Sinterklaas misplaced is a fake one. In another episode, Piet tries to trick Sint into drinking ink instead of wine. Perhaps they poured wine into the converter. Better to do this with a fake one; who knows what will happen with an expensive nib like that. The true pen afflictionado would no doubt ask: what nib size? A quick glance at the big book reveals a huge gothic-like handwriting. That can only mean one thing: a triple broad-esque signature nib, Montblanc’s specialty that no sane man can and will write with. When it comes to ink, the Sint is quite traditional: manuscript-like brown. Which is weird considering the future episode that displays pitch blank ink. Or perhaps he writes with molten Sint/Piet chocolate figures as ink. In that case I’d pour that ink down my throat as well. Related topics: / sinterklaas / flemish culture / By Wouter Groeneveld on 20 November 2026.  Reply via email .

0 views
Martin Fowler Yesterday

Fragments: November 20

Marcus Borg recounts an experiment to investigate if healthy code was cheaper for agents to review . Between a typical unhealthy pull request (CodeHealth 2.8) and a typical healthy one (9.7), that adds up to 22 to 35%. The measures of health come from CodeScene. The experiment looked at three LLMs, 465 pull requests on 246 open source repositories. Each pull request was put through a review and fix pipeline involving five agents. They also looked at which code smells led to increased costs: they highlighted Complex Method and Complex Conditional from the smells identified by CodeScene. Another drop of evidence that good quality code matters in agentic engineering. ❄                ❄                ❄                ❄                ❄ Gergely Orosz: One usage for AI: for these 100-page-long terms-and-service agreements you NEED to agree to, to eg play the game / sign up for a $10/month service and can never ever ever read as a regular person: I paste into AI and ask: “anything weird in this?” Before hitting “agree” ❄                ❄                ❄                ❄                ❄ Andrew Sharp has a good analysis of Jensen Huang and the crisis at Nvidia . While he starts off in a key that sounds worryingly like he thinks this is all a nothingburger, he goes on to explain in detail why this affair(s) is a problem at many levels, not just for Huang and Nvida, but also for Silicon Valley and the Trump Administration’s culture of impunity. For as brilliant and charming and tenacious as Jensen Huang may be—and as omnipotent as he may have seemed to people in the tech industry—we should be clear that his fundamental stupidity is not confined to multiple cases of workplace infidelity. Zooming out, this is a man whose technology became economically critical almost overnight, and it thrust him into a role navigating a geopolitical environment he simply could not handle. Huang’s highly centralized management style means that many people are worried about how Nvidia will operate without his hands on every lever. I don’t have any worthwhile insight here, but I am struck when he is compared in this way to Steve Jobs. I’ve always felt that one of the marks of a great leader is whether they can build something that can manage without them. Alexander the Great conquered a massive empire, but once he was dead it quickly withered away. Steve Jobs, for all his control of Apple, built a company that has done very well in the decade and a half since he left us. When we think of his achievements, the fact that he put together the people, organization, and culture to do this is one of the highlights of his ability. If Huang is to be compared to Jobs, what happens to Nvidia next will be part of the assessment. ❄                ❄                ❄                ❄                ❄ Steve Yegge tells everyone to slow down with software factories If you don’t pace your AI to human speeds, everything starts breaking around you, even at small operations like my online video game. I only have about a dozen humans working with my factory, and only a few hundred active old-timer players in the community who get along well, and still, introducing AI has still been very rocky. I hear a lot about how agents go so fast that humans can’t keep up, and are thus tempted to lose visibility to what the agents are doing. That’s opening ourselves to a whole lot of risk. There’s an argument for keeping the agents to a human-governable speed, one that may increase as humans learn to govern agents more effectively, but should still be limited by those the agents are supposed to serve. ❄                ❄                ❄                ❄                ❄ This post on the future of SaaS from Chad Fowler (no relation) is pretty compelling Companies will still pay other companies to host important software, secure it, operate it, maintain authoritative data, track regulatory changes, connect to external networks, and answer the phone when something breaks. What is much less obviously going to survive is the assumption that ten thousand different companies should use substantially the same application. The next SaaS company may run one service underneath ten thousand different applications. Chad’s vision is a core SaaS product that handles a lot of grimy details that businesses don’t want to do differently. The SaaS customer then build their own application on top of the SaaS that handles their particular workflows and quirks, or the SaaS vendor can build such applications for them. It’s a vision that has been around for a while, I remember much of this with the notion of reusable business objects. It’s an appealing vision, but was difficult to achieve in practice. Chad’s thought is that the productivity gains agentic engineering makes it practical now. A lot of the value in modern SaaS has surprisingly little to do with the visible application. It is data, trust, networks, compliance, operational responsibility, domain knowledge, auditability, accumulated history, and someone being accountable when reality gets complicated. If this future comes to be, however, the SaaS companies won’t look the ones we’ve got to know and rarely love. As Chad points out, the economics can (and must) change. As does the architectural thinking: Stewart Brand’s idea of pace layers is useful here. Healthy complex systems contain parts that change at different rates. Fast layers experiment. Slow layers provide continuity. Software is no different. A dashboard can change tomorrow. A team’s workflow can change next month. The authoritative definition of a customer may need to survive for years. Identity and authority can survive generations of applications. A key point he makes is that we want some things to be the same, and others to be different. Agents allow us to build lots of differences, but this variation can lead to a lot of complexity and problems that even agents will have difficulty solving. SaaS companies have an opportunity to create a platform to support the lowest pace levels, those that don’t change rapidly, those that contain common concepts and processes across and industry. That platform can then support generating applications that operate differently for every customer. Crucially, thinking of agents, they should provide tools to verify these applications, because in an agentic world Code generation is no longer the bottleneck — verification is . ❄                ❄                ❄                ❄                ❄ I happened to pop up the Doonesbury flashbacks and realized that last week marked the fiftieth anniversary of Doonesbury’s Joanie Caucus: “as the kid goes for broke” . ❄                ❄                ❄                ❄                ❄ I wrote a few weeks ago: “why are we wondering if they have consciousness - when we should be wondering why they don’t have a conscience?” Dylan Freedman and Juliana Castro Varón write in their New York Times Magazine column about the concept of corrigibility (from the work of Nate Soares): Just as a corrigible child is one whose behavior can be corrected, a corrigible A.I. system is one that responds to correction. The makers of A.I. want to build systems that follow human direction and allow themselves to be shut down, without resisting or deceiving their operators. Corrigibility doesn’t look like it’s made it far up the AI labs’ priority list. Freedman and Varón think is due to the way agents are trained - rewarded solely for completing their task, not for realizing that they are taking the wrong path while trying to get there. ❄                ❄                ❄                ❄                ❄ Jason Koebler (404 media) has an amusing story about Meta’s AI agent suing Meta . A small business owner used Muse (Meta’s AI agent) to run various parts of his business, including posting AI-generated videos in his Facebook pages. Meta’s content moderation then disabled the account, as it thought it had been hacked. This slammed the business, which relies of Facebook for leads. So the Muse agent filed a lawsuit against Meta, seeking $75,000 of damages. [the Muse agent] didn’t just email me (and other journalists) and sue Meta over Thomas’s account problem. It also set up a call with South Carolina Senator Tim Scott’s office, contacted various lawyers, contacted Thomas’s Congressperson, contacted the Better Business Bureau multiple times, filed a Federal Communications Commission complaint, filed a Federal Trade Commission complaint, contacted the California Attorney General, contacted the FBI, sent Meta itself threatening legal letters, and, as Thomas said, faxed the White House. There’s also a sense that Meta didn’t just bring this upon themselves by creating Muse… by not having functioning customer support, big tech corporations have functionally offloaded their obligations to the rest of society: journalists, government oversight bodies, politicians, and the court system. While I can’t deny the schadenfreude of seeing Meta’s agent sue Meta, the article also highlights a rather more disturbing broader consequence. The lawsuit and the circumstances around it show that, rather than Zuckerberg’s utopian vision, AI agents will indeed work on behalf of their users but in ways that use and potentially overwhelm existing systems designed for humans. Will we see a future where, in order to interact, we will need some proof of humanity at the other end? In a simple sense, that’s already happening when I trash some writing once it displays enough LLM Voice . I wonder what mechanisms we will invent to get that proof-of-human.

0 views
Unsung Yesterday

iOS’s unpredictable search

This is what happens when I search for “access” in my iPhone’s settings: Every time, the results appear in a different order. Here are all the I’m-done-typing states from the above video: = 3x)" srcset="https://unsung.aresluna.org/_media/ioss-unpredictable-search/2-framed.1600w.avif" type="image/avif"> = 3x)" srcset="https://unsung.aresluna.org/_media/ioss-unpredictable-search/3-framed.1600w.avif" type="image/avif"> = 3x)" srcset="https://unsung.aresluna.org/_media/ioss-unpredictable-search/4-framed.1600w.avif" type="image/avif"> = 3x)" srcset="https://unsung.aresluna.org/_media/ioss-unpredictable-search/5-framed.1600w.avif" type="image/avif"> = 3x)" srcset="https://unsung.aresluna.org/_media/ioss-unpredictable-search/6-framed.1600w.avif" type="image/avif"> = 3x)" srcset="https://unsung.aresluna.org/_media/ioss-unpredictable-search/7-framed.1600w.avif" type="image/avif"> There are a few reasons this might be happening, and to be honest I don’t fully understand how they got there. But one idea might be something I’ve seen a few times in my career that’s worth knowing about. It’s possible that at some point in the search chain… nothing takes care of reordering the items. They are found, they are filtered properly for the query, but then no algorithm ranks them – or, they are all ranked with the same value, and within that value, whatever random order they arrived in becomes what’s shown to the user. The consequence is that the results are not deterministic , but I believe they should be. I know search is more of a “living, breathing organism” compared to other stable navigation mechanisms – but it’s still useful for the user to match things consistently, and rely on certain things being repeatable. Even if you don’t understand the algorithm, you can learn that a certain result always matches on the first, second, or third location. This might change once in a while as the search evolves, but it’s better than nothing. The extra challenge in this particular case is that settings are already scary – even recently, we’ve seen some extra paranoia where a chunk of the public, likely further frightened by the new AirPods listening feature, started spreading videos prompting people to toggle off an iOS setting they didn’t really understand . “Access” is a harder query, so here’s another example. You would imagine typing “accessibility” would show you the main accessibility settings as the first result, every single time. Yet, here it’s the same inconsistent story: Even Google search, where the results truly change all the time, seems to be more deterministic. And, speaking of! Android doesn’t have the same problem: (Sorry about the accidental Uber Eats promo.)

0 views

Premium: Bursting Bubbles

The boom-and-bust cycle of bubbles is dangerous, destructive, and only really benefits the wealthiest and most-disconnected people alive. While there might be ways to get rich by virtue of piling your money in at the earliest point and exiting before everything explodes, that’s something only achievable if you’re either incredibly lucky, or you have some inside knowledge that others lack.  Bubbles are by definition unstable, illogical, and manipulated by a combination of captured media, wealthy (and brainless) financiers, and cynical grifters that know how to pull the different levels to keep the numbers going up. And they’re always, without fail, destructive.  At the root of everything lies a cynicism that vibrates through every part of society. Try and call a bubble early and you’re told that “the market can stay irrational longer than you can stay solvent,” or that “being early is the same thing as being wrong,” with any attempt to push back on narratives met with some sort of half-hearted statement about how “everybody is putting money into this” and the implication that you should simply give up and accept it .  As the bubble inflates and approaches breaking point, the very same people that told you that it wasn’t a bubble will say that “it’s obviously a bubble, but there will be winners at the end,” never quite explaining who they might be, how they might “win,” or really making any attempt to make a call about anything.   Bubble boosterism is, at its heart, an act of cowardice. It makes no attempt to explain why or how anyone wins, what that might look like, or when anything might happen other than repeating whatever the powerful says and then declaring victory based on whatever shred of proof they can find. These people also frame skepticism and cynicism as somehow villainous — that critiquing the rich and powerful is some sort of malignant act that works counter to a productive society — when boosterism is far, far worse. Boosters (correctly!) suggest that LLMs are now a dangerous new tool in the armory of the average cybercriminal ( none of which requires LLMs to be autonomous, sentient, or otherwise “going rogue” ), but refuse to admit their role in the ascent of the companies that built them.  Had major media outlets not glazed OpenAI, Anthropic, and other AI companies in the earliest days, they wouldn’t have been able to raise the funds or justify the capacity to build models that are specifically trained for hacking. None of this had to be built, nor does its existence disprove anything about my greater thesis that AI’s ROI and capabilities have been and are overstated.  This industry — like every bubble — has taken advantage of a few core weaknesses in the media: The assumption — despite the opposite being the case again and again and again — is that the powerful will always pull off whatever it is they promised, with everyone somehow forgetting that Mark Zuckerberg changed his company to Meta and burned $70 billion on the Metaverse before killing it two years later , and that Satya Nadella said in 2021 that he “ could not overstate how much of a breakthrough ” it was.  What has made AI so profoundly different to the metaverse is that there was something to speculate on, and a consumer-facing product for journalists to half-glance at before assuming that all of the other promises were true.  It all “made sense” if you didn’t really want to think about it. H yperscaler stocks skyrocketed as they invested tens of billions of dollars in GPUs , banks loaned them hundreds of billions of dollars to do so, and AI startups raised hundreds of billions of dollars. It didn’t matter if nobody would talk about their revenues or that OpenAI would lose $5 billion in 2024 because theoretically, at some point, all of this might be worth a lot of money, maybe. Asking sensible questions like “how much money are hyperscalers making?” gets you attacked and harassed on a daily basis, with random people screaming that “cloud revenues are skyrocketing because of AI” despite hyperscalers not actually telling you how much money AI makes , because hyperscalers know that all they need to say is that “cloud growth is so big because of AI” for everybody to look the other way. Questioning Anthropic’s profitability or failing to be sufficiently excited about its IPO is considered bad faith , because in a bubble, it’s considered “bad faith” to ask questions or be remotely skeptical. Those who dare to turn away the pro-AI (which can mean both “AI is the biggest thing ever” and “AI is going to literally destroy everything tomorrow”) slop are framed as outsiders, their intentions questioned a hundred times more than anyone who sits there saying “I love whatever the rich and powerful have planned for you and me so much!” This is, consciously or otherwise, a systemic response. To question a bubble is to question whatever new fad the markets and the media have decided is “in,” and doing that is scary because so many people benefit from a bubble’s inflation. People in the media get a new thing to write about (or be an “expert” in), banks get a new thing to invest in, tech reporters get new funding rounds to “cover” and executives to obsess about, venture capitalists get a place to park their money, and governments have a vague new place to point at to say how the economy will continue to grow indefinitely. It doesn’t matter to anyone on the way up how much damage there is to follow, mostly because thinking about bad things requires you to learn about why they’re bad, and take an actual position, which requires courage, when it’s so much easier to just follow everyone else. The bubble is yet to burst, but it’s clear that it’s very much on the way to doing so.  And today’s premium newsletter is about how we stop one inflating again. I’m going to have a little fun with this, mixing regulatory ideas and societal moves that could be made to kill the momentum of any further attempts by any industry to drum up speculative valuations.  This will be a grab-bag of ideas I’ve been working on for a number of years — a fun newsletter that you can dig into over Thanksgiving, where I’ll be taking a week off both the free and the premium — and I look forward to hearing your feedback.   Let’s get going. Its willingness to believe anything with a large number attached. Its willingness to believe anything with a big company behind it. Its willingness to believe anyone with enough “experience.” Its inability to do anything other than follow consensus. The fact that we have multiple members of the media that desperately want to be friends with tech executives, and/or to see their companies succeed.

0 views

How I fixed 55 bugs in a week by making my monorepo more agent-friendly

Hey, what's up? It's Takuya here. This week, I restructured my app 's monorepo so that my coding agents copy good patterns instead of bad ones. Along the way, about 55 bugs turned up and got fixed, and all of them were written by me, by hand. In this article, I'd like to share what inspired me, what I changed, and what I learned about working with agents. In the last article , I moved 39 repositories into a monorepo to boost my agentic coding. It has been working pretty well so far. I usually focus on one app at a time, like the desktop app or the mobile app. So when I switched to another app, I always found a lot of stale module versions that I had to upgrade. That was annoying. Now, when I update a module, my agent updates the other apps in the same change. The monorepo works as a restriction that forces every app to stay up to date, which is great. It also aligned my toolchain with the common tools, like Oxlint instead of ESLint and Vitest instead of Jest. With everything in one place, I found more outdated setups and strange mismatches between the packages. Still, reviewing the code that AI generated was taking a lot of my time. My agents kept making the same missteps. They inserted comments justifying their changes, which were boring and useless. They often patched the wrong files just to reach the goal. In other words, they went with local minimum solutions instead of thinking broadly over the whole project structure. I tried writing more rules for my agents, but it didn't solve these issues. I didn't know what else to do. Then, this week, I watched a talk by Lauren Tan (poteto): All Code is Slop Except Mine . What a spicy title. It was so insightful, and it gave me so many ideas to improve my repository. She said she shipped 3,000 pull requests to production in a month. I don't know if I can reach that level, but I was sure her ideas would help with my problems. Her key point is that your codebase is one of the largest inputs for agents, so it works as their memory. If the codebase has a bad pattern, the next agent will replicate it, because it looks like the established pattern. Code arrives so fast now that it grows like something organic, and she calls this "organic architecture". I totally agree with her. So, whenever you correct your agent, she suggests making it a deterministic check, like a lint rule, instead of adding another line to your rules or your AGENTS.md. By the way, last week, I got Claude Ultra free for six months from Anthropic's Claude for Open Source program , thanks to my OSS activity. It let me fully use Fable instead of Opus without worrying about the token allowance. It was the perfect timing to try her principles. First, I restructured the directories, because directory structure is a form of context. I myself read a directory name as the scope or the role of the code in it, so I have no doubt that AI agents read it that way, too. Her principle is to group code by features and layers. Categories like "utils" or "modules" are bad groupings. I fixed two things. First, who may import what: The main process and the renderer can no longer import each other, and lint reports it if they do. Every IPC channel is now typed against a shared contract, and only the main process writes the config file. Second, the layout of the desktop app. Before, the code was grouped by kind: After, it's grouped by feature: Each feature folder holds its components, hooks, actions, reducer, command handlers and tests, and the rest of the app imports it only through its . I did the same on the mobile app and the web editor, so the three apps share one shape. While restructuring, I found many illegal imports that crossed the boundaries. This was a bad pattern I had made, and now it's fixed. The structure is also easier for me to understand. Agents write massive amounts of code rapidly, and it's hard to keep track of it. Now, I can quickly find where to look when I review. My apps have a lot of IPC, between the main process and the renderer, and between the host app and the web view, which is complicated. With the feature folders, I no longer have to look here and there and miss the point. While working on it, I realized that I had been working just like my agents. I don't know if that's a good thing or a bad thing. When I started Inkdrop, I forked the Atom editor , so I already had a bunch of code and files. It was the first time I built an Electron app, and I didn't know the patterns. So I blindly followed Atom's directory structure and coding patterns, assuming they were the best practices. That worked pretty well, and I replicated so many patterns from it. But as the app grew, those patterns no longer fit its architecture and feature set. One directory ended up with hundreds of flat files, many of them with the suffix. That hid the scope and the role of the code, for me and for agents too. I did with Atom's code exactly what my agents do with mine: I followed whatever pattern was already there, without asking whether it still fit. Now I understand why agents work this way, because I did the same. And it was time to update my own principles for designing a codebase. I'm glad I learned that from this work. Strict lint rules are one of the crucial guardrails for agents, because they prohibit bad patterns deterministically. I personally trust the taste of Christoph Nakazawa , the creator of Jest, Yarn and Metro, who has been producing great output and contributing to projects at VoidZero. He recently published a new version of his oxlint config, @nkzw/oxlint-config . It's aimed at anti-slop: its rules are strict, so agents can't make silly mistakes, and it also cares about performance. Adopting it required a lot of changes, and I haven't finished yet. It reported 11,589 findings in 2,422 files at the start: But it already paid off a lot. alone found 18 real bugs, like hooks called after an early return or inside a loop. These rules forced me and my agents to revisit the current design and flow. Refactoring business logic with agents to satisfy new lint rules made me worried about regressions, since I can't fully trust them yet. I hadn't been writing unit tests except for the critical parts, like the data store and authentication, simply because it was economically impossible for a solo developer like me. But now, agents write code instead of me at a drastically fast speed. It's almost like managing a team at a company, back in the before-AI era. This scale can't be managed without thorough unit tests for every module, including the UI components. For example, requires every dependency of a to be listed. Adding one changes when the effect runs, so before each fix, my agents wrote component tests against the old code. None of these projects had component tests before: Writing those tests found far more bugs than the rule itself. About 55 are fixed so far, each with a test that failed first. For example, the editor's search bar subscribed on every effect run and never unsubscribed, so a single "find next" jumped over several matches. These bugs were all written by me, by hand. I expect this work to find more bugs before it's finished: 13 bugs on mobile are already pinned by tests and waiting for fixes. It feels good. Not everything went smoothly, though. poteto said in another talk : "It's not really a secret. It's a lot of hard work." That held for me. The new structure and boundaries made my codebase something I'm happy for an agent to copy, and the stricter lint rules turned out to be a bug finder, because they forced tests into code that never had any. I learned that I should doubt my codebase and my lint rules before adding another rule for my agents. As a next step, I'm eager to add more runtime verification. I think the engineering task for us humans has changed: from improving code by hand to building high trust with agents through tools and design. If your agents keep making the same mistakes, I hope this helps you look at your codebase first. That's it! Thanks for reading. My agents kept taking the nearest fix, and writing more rules for them didn't help. The codebase is the agent's memory: agents copy whatever pattern is already there. Directory structure is context, so I grouped the code by feature and made lint enforce the boundaries. I had been blindly following existing patterns too, just like agents do. Strict lint rules stop bad patterns before I review them. Writing tests before the lint fixes found about 55 bugs, all written by me, by hand. Building high trust with agents is the new engineering work. The automatic fixers are not always safe. renamed to , would have broken the alias in React Native, and rewrote in a file. Mass moves conflict with open branches. Merging into the lint branch after the directory moves gave me 145 conflicts. Require cycles on mobile. Exporting a feature's Redux state from its made the Redux roots load the components, which import the roots back: ten new cycles at launch. I fixed it with a second public file per feature, . Verification lags behind the code. I haven't made a packaged desktop build since the move yet, CI hasn't run the moved tests, and Windows, Linux and the account flows are still unchecked.

0 views
Ankur Sethi Yesterday

An experiment with SIMD in Rust using fearless_simd

SIMD is having a moment right now. I've always been vaguely aware of the existence of SIMD instructions, but it was Mitchell Hashimoto's Everyone Should Know SIMD that finally inspired me to try writing some code that uses SIMD myself. I decided to take a straightforward problem and try making it faster using SIMD instructions: count the number of occurrences of a byte inside a text file. Since I've been using Rust for writing pretty much everything these days, that's the language I picked for this task. I used as my test dataset. This is a file containing a gigabyte of text from the English language Wikipedia. All benchmark numbers are from my MacBook Pro with an M4 Pro and 48GB RAM. My Rust version is 1.100.0. Here's what the non-SIMD version of the code looks like: When I compiled this code with Rust's auto-vectorization turned off, it took 138.05ms to count the number of occurrences of the letter in the test dataset. With auto-vectorization enabled—which is the default behavior—it was marginally faster at 114.55ms. Here's the same code, this time using : This code took 30.35ms to to run on my computer. That's ~4.5 times faster than the scalar version with auto-vectorization disabled, and ~3.8 times faster than the scalar version with auto-vectorization enabled. Pretty damn good for a few extra lines of code! To make sure my numbers were accurate, I had to make sure Rust and LLVM weren't optimizing away the very code I was trying to benchmark. I recently inherited an old ASUS TUF Dash F15 from my brother. This computer comes with an 11th generation Intel Core i5 (11300H) and 24GB RAM. It's currently running Fedora 45. The benchmarks on this machine were a bit surprising: I don't understand why enabling auto-vectorization made the scalar version slower . I don't know enough about Rust, SIMD, Linux, benchmarking, or x86 assembly to explain this behavior. If anyone reading this understands why this happens, I would appreciate it if you could get in touch . If you want to try replicating these experiments, you can grab the code from my GitHub repo. You'll also have to download the test data from Matt Mahoney's website . Go added experimental SIMD support to their standard library. C++26 standardized (which hasn't been very well received ). Portable SIMD is available on nightly Rust via . The excellent cut a 1.0 release in September . It works on stable Rust. Other languages have already shipped portable SIMD APIs in their standard libraries for a few years. For example, in Zig and in Java . I made liberal use of to block certain common optimizations. I used to prevent inlining the scalar code ( might have been enough to ensure this, but I was in an overly cautious mood). I compiled the scalar version with and to disable auto-vectorization . Scalar version with auto-vectorization disabled: 240.48ms Scalar version with auto-vectorization enabled: 319.96ms SIMD version: 56.80ms

0 views
Stratechery Yesterday

Sharp Tech on Video: Jensen’s Not Coming Back, AI Shopping, The iPhone Duo

Sharp Tech is, for the first time, available on video. You have three ways to consume it: YouTube, Spotify, and here on Stratechery

0 views
Jason Tucker Yesterday

Roam Assistant: putting Home Assistant in the motorhome

In October Jen and I bought a 2024 Thor Chateau 22E on a Chevy chassis. It came with a thick binder of manuals for everything bolted inside it. What it didn't come with was any way to know what was going on in there when I wasn't standing in it. At home, Home Assistant runs pretty much everything, and I've gotten spoiled. The RV is a rolling house with its own batteries, water, propane, generator and internet, and from my couch I knew none of it. A few weeks back I was on the Home Assistant Podcast talking about my house and all the stuff I have on there, I may need to make another appearance talking about the RV. So the RV got its own Home Assistant. I named it Roam Assistant , because of course I did. This is the tour, not the how-to. Pretty much every section here is going to get its own post, so consider this the table of contents. Roam Assistant is a Raspberry Pi running Home Assistant OS, sitting on a Geekworm X728 UPS board. If you take one thing from this post, take the UPS. RVs lose 12V power constantly (battery disconnect, shore power swaps, converter hiccups), and a Pi that loses power mid-write is a Pi with a corrupted card. Now it tells me when it's on battery and shuts itself down cleanly if it has to. It's on Tailscale like everything else I own, so I can poke at it from anywhere the RV has internet. I also swapped the Pi's built-in Bluetooth for a USB adapter , because it turns out a lot of this coach talks Bluetooth. SmartyVan also pointed me at GeoLocator, one of his Community Projects . It moves Home Assistant's location based on GPS. The catch: we didn't have GPS. Not until the Winegard integration started reporting one. Now weather, sunrise and sunset, and everything else location-based follows the coach instead of thinking we're still at home. Then it gets nerdy. That same list introduced me to Public Lands , which tells me who manages the land we're parked on: BLM, Forest Service, state or private. Parked in my driveway right now, it reports "Private Land." Correct, and kinda funny. Public Lands got me thinking about campgrounds. I had Claude fork it, scrape every KOA location into a private database, and turn that into a sensor for nearby KOAs and whether we're checked into one. This is the part I didn't plan on, and it might be the most useful thing in the whole build. We downloaded every manual for everything in the coach and saved them to Google Drive. In another project those became a quick-lookup manual for us, so "how do I reset the water heater" is a question, not a binder dig. Then every maintenance interval in those PDFs went into Home Keeper , a maintenance and chore tracker for Home Assistant. Each task has a due date and cites the manual and page number it came from. We bought it used with no service history, so a bunch of those lit up as due on day one. Fun. That one's getting its own post too, because I think anyone who buys a used RV should do this. Every device we've uncovered so far has a full dashboard: chassis, network, power, generator, environment. I'm sure we'll find more hiding in this coach soon. Across the top there's a notification bar for whatever is currently yelling at me. Behind it there are about a dozen automations for the stuff you'd expect: power lost, internet down, things too hot or too cold, door opened, and a Pi that reboots itself if it loses the router. Because "the Pi fell off Wi-Fi and never came back" is the most homelab failure there is. It's janky in the best possible way, and it's built for an audience of one. Big thanks to SmartyVan . A good chunk of this build exists because he showed his work first. If you're into RV or van automation, go subscribe. Do you run Home Assistant in your rig? What did you wire in first, and what do you wish you'd done sooner? And if you've solved RV internet, tell me what you went with. Let me know, I'm curious. More on this soon. The chassis. A WiCAN Pro in the OBD-II port reads the Chevy's engine data over Wi-Fi. Fuel, coolant, chassis battery, odometer, and a pile of oxygen sensor values I will never look at. I got this idea straight from SmartyVan's video , and it worked exactly like he said it would. The internet. The coach came with a Winegard gateway, and there was no Home Assistant integration for it. So Claude and I built one. It exposes way more than I expected, including a GPS fix. I might open source it once I know it's working well. The house side. A few Shelly BLU sensors for temperature, humidity and the side door. One lives in the network cabinet, because a closed cabinet in a parked RV in a SoCal August is how you cook a Pi. The generator. Yes, that one. I wrote a whole post about teaching Home Assistant to read my RV generator without starting it . It's still read-only, on purpose. Power. I'll most likely end up with a Victron setup and ha-victron-mqtt , which sounds awesome and is (you guessed it) also on SmartyVan's Community Projects list. Media in the rig. Jellyfin and Syncthing are already on the Pi. The plan is to sync the handful of shows we actually watch from home so we're not burning data on the road. Internet on the road. Right now the gateway rides on our home Wi-Fi in the driveway. Out there, what should I use? Tether my phone? Turn on the Winegard's LTE? Swap it out for Winegard Starlink setup? I honestly don't know yet. Got any ideas, leave a comment! Safety. A smart CO detector that actually talks to Home Assistant.

0 views

Running a Rex terminal server on Home Assistant

I've put together , a Home Assistant app (what Home Assistant used to call add-ons) that runs a Rex terminal server on your Home Assistant machine. Rex is a terminal multiplexer, like tmux or screen. A multiplexer keeps your terminal sessions running on the server, so you can split them into tabs and panes, disconnect, and pick up exactly where you left off later. The sessions live on the machine running the server, not in the app you're looking at them through. The difference with Rex is the client. Instead of attaching from another terminal, you connect from a native macOS or iOS app (or the command-line tool). Running it on the Home Assistant box means I can open terminals from my laptop or phone, and anything I leave running is still there when I come back. The Home Assistant machine is on all the time anyway. I wanted another remote host I could connect to when my main Mac is off, for the times I need to reach something on my home network. The terminals run inside the app's container, not on the Home Assistant host, so this isn't a replacement for the Terminal & SSH app. A shell on the host was never the goal; I just wanted another target to connect to. The container only sees its own data folder, not the host's files. Every Home Assistant app is a Docker container. When you install an app from the store, Home Assistant doesn't compile anything on your machine: it downloads a prebuilt container image and runs it. So the main job of this project is producing that image and keeping it up to date. A GitHub Actions workflow builds the image on every release and publishes it to GitHub's container registry as . One image covers both flavours of hardware Home Assistant runs on: it's built for (Intel/AMD boxes) and (Raspberry Pi and most other boards) in a single package, and Home Assistant picks the right one for your machine automatically when it pulls it. The image doesn't contain Rex itself. Rex publishes builds across three release channels: , , and . If I baked a particular Rex build into the image, switching channels would mean publishing a separate image for each one. Instead, the image contains only the base system, the startup scripts, and the signing key for Rex's package repository, which lets it verify that the packages it downloads are genuinely from Rex. When the app starts, a small setup script runs first. It reads the channel you picked in the Configuration tab ( by default), downloads Rex from that channel's package repository, and installs it. A second script then starts the Rex server itself, and the container's process supervisor keeps it running. This all happens on every start, which gives you two things for free: The trade-off is that the app needs network access at startup to fetch Rex, and the exact Rex version isn't pinned by the app version. For a project tracking a fast-moving beta, that's the behaviour I want. One catch: restarting the app stops anything running in your sessions, so save your work before you flip that dropdown. The easiest way to connect is over Tailscale . Rex has Tailscale built in, so the Home Assistant machine doesn't need Tailscale installed separately, and you don't need to open any ports on your local network or router. Paste a one-time Tailscale auth key into the app settings and start the app. It joins your Tailscale network as its own device ( by default, which you can change in the settings) and sets up an HTTPS certificate automatically. For that to work, your tailnet needs MagicDNS and HTTPS certificates turned on (both live in the Tailscale admin console under DNS). That's a Rex requirement , not something the app can set up for you. The login is saved in the app's data folder, so you only need the auth key once and it stays signed in across restarts and backups. Once it's running, add under Add Remote Host… in Rex for Mac, or connect from the command line: If you don't use Tailscale, there is also an optional plain HTTP listener you can turn on for a trusted local network or VPN. It is off by default because it doesn't require a login, so anyone who can reach that port on your network can open a terminal inside the app container. In Home Assistant, go to Settings > Apps > App store > ⋮ > Repositories and add: Then install Rex Server from the store, add your Tailscale auth key in the Configuration tab, and start the app. The code and full setup instructions are on GitHub at github.com/aranw/ha-rex-server . switching channels (or moving back from to ) is just a dropdown change and a restart; restarting the app also picks up the newest Rex build on your current channel, without waiting for me to publish a new app version.

0 views
xenodium Yesterday

agent-shell 0.98 updates

Another month, another agent-shell update. If you missed the last post, have a look at the 0.87 update . This time around, the most notable changes are around rendering, performance, and bugfixes, sprinkled with new features here and there. As usual, this post showcases highlights, but please check out the full list of changes if you're after the nitty-gritty. agent-shell brings your favorite AI agents to Emacs , keeping you at home: familiar buffers and bindings, no terminal emulation. All powered by ACP, the Agent Client Protocol . DeepSeek Harness joins the family, bringing the total number of supported agents to 24. Start DeepSeek with , or pick it from as usual. Latest Antigravity ships with ACP out of the box, so now runs rather than a separate binary you had to download and unpack. If you're an Antigravity user, install a recent CLI, make sure is on your , and sign in once: Blockquotes improved their display, rendering embedded Markdown ( #942 ). They also joined the TAB navigation party. and now visit blockquotes, stopping on their first quoted character. With point on a blockquote, now copies the quote's raw Markdown, without the markers. Images are now rendered as thumbnails within tables. Press on an image to open in full view. Thank you @alberti42 for #938 . Tables also realign in the resized window's own buffer now ( #934 ), so splitting a window no longer leaves a table laid out for the window it used to be in. Hovering a rendered link (or with point on one) now shows its target URL, so you can judge whether it's worth opening. Two new entry points landed alongside ( #933 ): toggles the fragment at point, as usual. now toggles groups recursively ( #924 , #945 ). Queued a prompt, but wanted to steer instead? Pressing on an empty prompt now offers to steer the last queued prompt into the running turn ( #918 , #919 ). While this isn't something I need often, I'm pretty happy with the UX we landed on. While on the topic of steering, chat mode now handles steered prompt labelling ( #930 , proposed by @Gleek ). If you'd like to render labels differently, now receives the param. Agents often expose options that never make it to the buffer header. Additional options are now offered via the menu ( #921 ). Agents write all sorts to stderr, and surfaces it under "Notices". You can now use to filter notices (or modify) as preferred ( #950 by @astoff ). It receives an alist with , one stderr line, and returns the text to show or nil to drop it: A filter that signals or returns a non-string is reported, and the notice shown unfiltered. is appended to the agent's default system prompt, sent whenever a session is created, loaded, resumed or forked ( acp.el #37 by @systemfreund ): Only agents advertising ACP's capability can take one. Configure a prompt for an agent that can't, and says it's ignored rather than dropping it quietly. An agent config's takes precedence. now takes a function as a value and calls it when the agent starts, rather than when your config loads ( #948 by @nbarrientos ). Handy for a password store still locked at init: A function that errors or returns nil leaves the variable out of the agent's environment and says so in a boxed warning in the shell. Works across all agents. Starting a shell from used to land in the current shell's directory rather than the project you just picked, and offer that directory's sessions to resume. It now starts in the chosen project ( #949 by @OSadovy ). When is non-nil, forked sessions will attempt to restore interaction history as per . is off by default, so you'll need to enable it with: Note: You'll need an agent that supports loading a session right after forking it, like or newer. Streaming performance received some love. Message chunks are coalesced before rendering ( #883 by @moyotar ), thought chunks are batched the same way, and restored sessions replay with far less overhead ( #897 by @Gleek ). As mentioned, the much effort in the release went into fixes and improvements. Performance and responsiveness: A few more additions for package authors building on . returns the range of every prompt in the buffer, in buffer order, covering prompts typed at the shell, replayed by a restored session, and steered into a running turn ( #882 ). Each comes back as an alist spanning the comint shell prompt itself ( , ) and the input typed after it ( , ). now offers a event, broadcast when the agent reports context window or cost usage. Events now also carry ACP's , so integrations can read whatever an agent attaches without waiting on . now accepts a function. It's called with the resumeable sessions and returns , , , or a cons to load a specific one: If you peeked at the commit logs for the period, you'll see it's been another busy month. Since the last post, 193 commits landed, 32 issues have been closed and 27 pull requests merged. As of this writing, the backlog sits at 6 open issues and 5 open PRs (versus 4 and 6 last time around). Zooming out a little, here's how the backlog has tracked: As usual, this chart was generated using the skill shared in my emacs-skills repo. All of this requires daily attention. While paying for tokens keeps agents running, sponsoring keeps running. is built and maintained by me, an indie dev, while the tools it competes with often have well-funded teams behind them. Funding Emacs-native tools, so we can keep living in our beloved editor, matters now more than ever. Using at work? Ask your employer to sponsor too. Companies can contribute at a scale individuals can't. Thank you to all contributors for these improvements! stands on acp.el to speak ACP and shell-maker for its shell foundations, so fixes landing there reach you just the same: As of this writing, we're 89% of the way to the 150 monthly sponsors goal , a tiny closer since the last update . If is part of your daily workflow, please consider becoming a monthly sponsor (or ask your employer to). Not in a position to sponsor? A GitHub star helps with exposure and brings in new users. opens the link at point. plugs into , so on a rendered citation visits it. It returns nil anywhere else, web and binary links included, leaving point to the next backend. Bold renders next to text and punctuation ( #925 by @vritser ), with CommonMark flanking rules relaxed for CJK ( #942 ). Numbered headers and bold steps no longer render as list items ( #939 by @budu ), nor does markup that merely reads like one. A fenced block's last line is fontified ( #916 by @liaowang11 ), two flush source blocks render as two ( #940 ), and nested ones stay verbatim while streaming. Headers keep their title when a code fence follows directly ( #947 ). Text quoted into the prompt keeps its quote face ( #952 by @OSadovy ). Copilot multi-hunk diffs render as separate hunks ( #931 ), and Codex streamed output is fenced correctly ( #906 by @bartbunting ). Icons scale correctly on HiDPI Linux ( #917 by @heraplem ). Unfinished tool calls survive turn end ( #941 ), so a late subagent keeps its title and grouping. Buffers shown in no window measure against a live one ( #885 by @bcc32 ), and measuring glyph height no longer triggers window hooks ( #886 , also @bcc32 ). is called once per command ( #857 , also @bcc32 ). Pending Markdown is protected and fontification updates silenced ( #915 by @daym ). Chat mode relabels only the last turn while streaming, not the whole buffer ( #943 , profiled and proposed by @Gleek ). In shell-maker , auto-scroll can be suppressed during bulk updates ( #50 by @Gleek ), which is what makes the faster replay possible. Also in shell-maker, the check that ran on every submission is gone ( #32 by @carlosdagos ). In acp.el , agents handle before being killed on shutdown ( #35 by @fjolliton ). Undo history no longer carries programmatic renders: the compose buffer starts empty ( #893 by @liaowang11 ) and resets after a deferred render ( #902 by @bcc32 ). New worktrees stay under the main working tree ( #904 by @xiaofeilovecoding ). A restored session finishes initializing even when rendering errors ( #887 by @bcc32 ). Flymake context is only used when is on ( #892 by @liaowang11 ), and single-line regions carry one line number ( #922 by @martenlienen ). Quoting a region leaves the mark where reading stopped ( #896 by @OSadovy ). Minibuffer completion keeps the agent's candidate order ( #929 by @Zzull ). Remote URLs are skipped when parsing local links ( #926 by @mpmiszczyk ), and optional system-sleep functions are declared ( #928 by @mboldt ). In shell-maker, non-ASCII prompt history no longer reads back as raw bytes, and entries already corrupted by older versions are decoded on read ( #49 by @kazmuroi ). In acp.el , agent stderr reaches error handlers one line at a time rather than in arbitrary pipe chunks (added for notice filtering). #857 : Call agent-shell-cwd-function only once per command ( @bcc32 ) #873 : Add Antigravity default-model-id and default-session-mode-id defcustoms ( @tychoish ) #883 : Coalesce streamed message chunks before rendering ( @moyotar ) #885 : Measure a buffer shown in no window against a live window ( @bcc32 ) #886 : Do not trigger window hooks when measuring glyph height ( @bcc32 ) #887 : Finish initializing a restored session even if rendering errors ( @bcc32 ) #889 : Add a separate provider notification handler ( @Cy6erBr4in ) #892 : Only use flymake error context when flymake-mode is on ( @liaowang11 ) #893 : Start the viewport compose buffer with an empty undo history ( @liaowang11 ) #894 : Render the viewport's held-back markup when a turn ends ( @liaowang11 ) #896 : Leave the mark where reading stopped when quoting a region ( @OSadovy ) #897 : Reduce overhead when replaying restored sessions ( @Gleek ) #902 : Reset undo history after a deferred markdown render ( @bcc32 ) #904 : Keep new worktrees under the main working tree ( @xiaofeilovecoding ) #906 : Fix streamed Codex command output ( @bartbunting ) #915 : Protect pending Markdown and silence fontification updates ( @daym ) #916 : Fontify the last line of a fenced code block ( @liaowang11 ) #917 : Fix HiDPI icon scaling on Linux ( @heraplem ) #922 : Use one line number for single-line region contexts ( @martenlienen ) #925 : Fix bold rendering next to text and punctuation ( @vritser ) #926 : Skip remote URLs in parse-local-links ( @mpmiszczyk ) #928 : Declare optional system-sleep functions ( @mboldt ) #929 : Keep original order of candidates for minibuffer completion ( @Zzull ) #938 : Lay out table cells that show images ( @alberti42 ) #939 : Don't render numbered headers and bold steps as list items ( @budu ) #949 : Start a new shell in the project chosen with project-switch-project ( @OSadovy ) #952 : Keep the quote face on text quoted into the prompt ( @OSadovy ) acp.el #34 : Allow listing sessions without a working-directory filter ( @Gleek ) acp.el #35 : Let the agent handle SIGTERM before killing it on shutdown ( @fjolliton ) shell-maker #50 : Allow suppressing auto-scroll during bulk updates ( @Gleek )

0 views
iDiallo Yesterday

Another company I've never heard of lost my Data

I received a letter from Premise Health Holding, a company that I had never heard from before. Apparently sometime in March 2026, one of their employees started fiddling with customers' data. And no one noticed until September of this year. In the letter, they say that my data was affected, including name address, social security. Everything important to impersonate me. I'm happy they have notified me. Truly. But I'm sorry, who are you? And why do you have my information in the first place? As far as I can tell, I've never done business with them. Why do they have my social security of all things? And the worst part is that their penalty for having lost my data is that they offer me 1 year of free credit monitoring. Jokes on them because I already have free credit monitoring for a whole year. Or more like 6 months left now. That's right, another company I had never heard of had also lost my data to bad actors this year. And as a result, they had also offered me free credit monitoring. What happens if the bad actor waits a full year before using my data? After all, my social security will remain the same. I can't really change that. Unless there is a solid penalty for losing data that cannot be recovered, this will continue to be routine. Just offer 1 year credit monitoring that most people won't use and you are set. Shortly after my kids were born , one of them received a letter, addressed to him by name. It was to inform him that his personal information had been breached.

0 views

The Third Scale Encoding is Hopepfully the Charm

Well, unfortunately time has run out, and I am not going to make the NaNoWriMo writing goal! I’m off to Japan on Monday and promised my wife that I’d do at least a little thinking about the trip before we head off. So that means I’m putting a (temporary) close on the music stuff for a few weeks. But don’t worry; I can’t get this stuff off my brain, so some time off is likely only going to stoke the flames. With that being said… My plan today was to write about vertical configurations and voice leadings. But I realized my notion of voice leadings didn’t agree with Tymoczko ’s. And while there are a lot of music theorists whose opinions I don’t put much stock into, Tymoczko is one whose thoughts I value very much. While trying to answer those questions, I looked at my implementation of Neo-Riemannian transformations and realized it was convoluted as all hell (which I knew). Furthermore I noticed that our work on scales the other day did almost everything I was doing by hand in the Neo-Riemannian case. So I swapped out the bespoke stuff for everyday scale things, and the tests stayed green. Happy days. But then I changed my test generators (so that notes would include generalized accidentals ) and the tests went red! For reasons unrelated to Neo-Riemannian transformations, but for darker, scarier reasons. Scales were doing the wrong thing. Oh man. Not so good. The problem is that under our previous encoding, not all scales are retractable . Check it out: We previously left s defined thusly: The codomain being was so that we had a place to stick a scale degree and an accidental. We really only wanted to store a pitch class and an accidental, but you could rotate the pitch classes in a scale and then the lower pitch classes might only be reachable an octave up. Thus the degrees. OK fine. But look at this mapping: Here we’ve defined a scale that maps both pitch classes in to , but the second pitch class also carries a (chromatic) sharp. All is well and good, until we go to invert this thing. Inverting the image of the first pitch class is fine: but inverting the image of the second, well… Because application of scales dispatches only on pitch classes, it can’t branch on the accidental here. So what was once in the image of is now somehow getting smuggled along when we apply the inverse of . Weird! This is a fundamental problem with our scales as written. They simply do not always admit left inverses! To be clear, the problem here is that isn’t injective in its mappings from to (both end up at .) So if we could force the scale to be injective, then the error conditions wouldn’t apply, and we always would be able to find a left inverse. So then, how do we ensure we have an injective mapping between finite numbers? As an aside to the main thrust of this blog post, I found it quite elucidating to think about what this “injective mapping of pitch classes” constraint actually means in terms of music. And I THINK that this is the underlying constraint that enharmonic spelling is attempting to solve. Recall that the standard musical staff notates the diatonic scale ( ), which corresponds (roughly) to the white keys on the piano. For time immemorial we have been working in , and this is why the black keys don’t have their own names – because the black keys are the five notes that you need to add in to get to . We happily talk about the white notes as A, B, C, D, E, F, G, but the black notes are relegated to mere modifiers — sometimes as D#, other times as Eb. But never as DE . Anyway, since we can’t call it the note between D and E as DE , what can we do? Well we need to project this note down to . Which of course can’t be done in general, but we cheat by adding an accidental. Is it either D# or Eb? It depends! What does it depend on? Conventional spelling rules say that it ought to be offset from “the scale note it is acting in place of.” Which is to say that it must be temporarily replacing some note in the scale, and it steals that note’s pitch class! If we pull this back to injective mapping of finite numbers, the weird historical rule makes sense. In order to preserve this injective mapping you must remove any other notes which would otherwise map to the same pitch class! I feel like I am not articulating this very well. Maybe some diagrams would help. But I’d actually like to go to bed sometime tonight and there is still too much to write down before I need to put the book ends on my music project for a few weeks. Alas. Let me know in the comments if any of this section makes a lick of sense. Or if it doesn’t. That’s what we call e n g a g e m e n t , baby. OK so anyway, back to trying to enforce injectivity of finite maps. Thankfully I wrote a book on Agda which happens to be pretty helpful for working out solutions to stuff like this. Recall that functions are isomorphic to vectors (which is to say, a product of copies of .) This fact will come up again when I eventually get around to writing about voice leadings. But you will notice that functions are not injective functions between s! To be concrete, let’s say we’re looking for mappings of the form . Which solves our scale problem (because we can put our accidentals in .) So as a first step, we could consider encoding this mapping as: with the invariant that there be exactly elements that contain s. For example, would look like this: Here we have filled exactly 3 of the 7 total slots. We can then recover the mapping by traversing over the s and pairing each with the next : Now if we zip this vector with its own indices, we get this: Finally, filter out the s, and you’re left with (he said, gesticulating wildly) exactly three values, and their corresponding indices in both and : Since you and I both “know” that there are three elements in this list, we can give a “total” function: Sure enough this does work! But it only works because of our invariant that there are exactly 1 3 s in our original vector. That’s cool and all, but it seems like the sort of thing that would be easy to get wrong. And then you’d be crashing at runtime, and that’s not the Haskell Ethos. So what can we do instead? Let’s make a type that is like a , but which counts slots separately from filled slots. I needed a name so I called it an , but the doesn’t actually stand for anything. Behold: Here, acts exactly like did in our vector example — it sticks an element in front of another . But in doing so, it increases the slots and the fill count both by one. However, there’s also which only increases the slots (and correspondingly doesn’t have a place to put an .) This structure thus perfectly encodes our slots of which exactly are filled semantics. Very cool. As a little proof, we can project a down to either a or a : So that’s all well and good. But we can also actually find things in this data structure, as given by : which you will happily note follows the same logic we worked through for , and is exactly the function we want to use for making s. We can also go the other way, and search on the indices: which I’m not super sure is important, but it was fun to write. The real reason for calling this thing was so that I could put s in front of all its functions’ names. Which finally pays off when we get to the composition function: This function does end-wise composition of s. If you have one that has slots and items, and another which has slots and items (sorry for the type variable shuffling!), then we ought to be able to make an with slots and only items. This corresponds to composition of scales, so it’s really quite important! The trick is we traverse over the b-in-c collection. Whenever we find an item there, we consider it to be a potential slot of the a-in-b collection. If a-in-b says to skip, then we skip it. But if they’re both cons cells, we can use the given function to combine their values into a . Quite nice if you ask me. Now that we have s, it’s pretty trivial to implement the small-to-big scale mapping that we’ve been thinking about. Really we just need to keep an around, convert it into the old representation via , and then all of the last post’s machinery around scales works just fine. Except, how do you invert them? Remember that we did all of this work to invert them. If an has slots of which are full, it necessarily means that . Which is to say that it’s slightly more complicated than just keeping a around. The trick of course is that if you invert a scale, it’s still the same you need! Thus a is either an embedding from to , or a projection from back to : Notice that it’s the same in both constructors, the only difference is which direction the scale goes. This thing is a little enum: which corresponds exactly to the three functions from last time. Really it means “if you’re looking at a scale degree which doesn’t fit, which note should we add offsets to?” I don’t think I like having this field, and when I’m back from Japan I’ll explore just sticking the chooser in there. Once we’ve added , however, I don’t think scales compose anymore. Not to fear, we’ll just make them compose by adding a new constructor: Composition of scales tries to when possible: and inversion is now a little swap-er-oo of our constructors: So that’s the thrust of today’s work. Having sorted out all of these details has dramatically simplified up the codebase (and found a bunch of bugs), which I always consider to be a harbinger of being on the right track. Making any of this stuff usable is its own exercise in existential types and type reflection shenanigans, but maybe we’ll cover that another day if there’s sufficient interest. Well technically it works because there are at least 3 elements… ↩︎ Well technically it works because there are at least 3 elements… ↩︎

0 views
Manuel Moreale 2 days ago

The expectation of effort

Almost two months ago, during an enjoyable email exchange, Pimm wrote something I haven’t stopped thinking about: The era of AI made me realise effort used to be a currency I recently started working on a new version of the blogroll , after closing submissions because they were overrun by AI slop. And as I’m spending time thinking about the new design, how to structure the new version, what to add, what to remove, what features could be useful to visitors, I can’t stop asking myself the question «Is it even worth it?» . Years ago I wrote about the loneliness of running online projects, and since then things have not improved. They have gotten worse. The number of people who think a site like the blogroll is a tool for self-promotion has steadily increased over time, and before closing down submissions I was deleting dozens of sites that were nothing but pathetic attempts to drive more traffic to shitty portfolio sites. At the same time, the number of people who took the time to even do something as basic as sending an email to say “hey, thanks for the site” approached zero. Now AI is making everything worse because the pervading thought is that creating and running sites takes no effort at all. Why even bother spending brain cycles thinking about the people who are behind the sites? They’re probably leveraging AI to do the work after all. And, look, this is probably on me, because I still naively believe in human connections and some semblance of decency and kindness. It’s also probably me being burned the fuck out, but the more I think about it, the more I’m convinced it’s not worth it. It’s not worth putting in the effort if the people on the other side will not do even the bare minimum. And that's a sad thought to have. Thank you for using and believing in RSS. You're awesome. Send me an email :: Sign my guestbook :: Become a supporter

0 views
spf13 2 days ago

The Collective Mirror: Why AI Can Spot Your Blind Spots (But Not Your Breakthroughs)

Ask an LLM what you conveniently left out of a strategy memo, and the answer can feel unnervingly perceptive. That looks like a paradox if you believe, as I argued last week in Creativity in Negative Space , that LLMs operate entirely in positive space (everything humans have already written and absorbed into training data), while real creative breakthroughs live in negative space (the gap nobody has named yet). My friend Jordan Rubin read that post and pushed back in a comment on my Substack: “I agree with you that creativity works differently in positive and negative space. I don’t agree that AI can’t see the negative space. It can! It just needs to be prompted to.” He linked an earlier post from his own Substack, What do you have unsaid? , where he introduced a prompt skill called . Run on a strategy memo or blog post, and it surfaces hidden motives, strategic omissions, unstated assumptions, and blind spots. As Jordan puts it, the reaction is “uncanny. Not in the uncanny valley sense, all too common with LLMs, but in the how did it know sense.” On closer look, Jordan’s article and prompt reinforce exactly the point I’ve been making. Jordan and I were using “negative space” at two different levels: what is missing inside an individual document versus what is missing outside the training corpus. As his own spec makes clear, works because a model’s positive space acts as a collective mirror for our individual blind spots . Jordan’s specification describes the mechanism plainly: detect the argument, conclusion, or premise that should be present given the statistical structure of the text, but is conspicuously absent. negspace reads the “shadow” of the text by comparing what was written to what was overwhelmingly likely to be written next… Overwhelmingly likely to be written next. Later in the spec, Jordan puts a rough number on it, asking the model to find the omitted conclusion “~80–95% likely given the argument’s structure,” or “the statistical ghost of the missing argument.” In his spec, Jordan uses “perplexity spike” and “~80–95% likely” as prompting heuristics, not literal logprob readouts. A chat prompt doesn’t inspect its own token probabilities, and if you instruct an LLM to hunt for hidden motives, it will gladly hallucinate cynical ones for any paragraph you hand it. What makes the useful hits land is pattern completion, drawn straight from the densest positive space in the model’s weights. An LLM has ingested millions of essays, arguments, post-mortems, and negotiations, giving it an aggregate map of how human arguments unfold. When an author swerves off that expected path, whether from ego protection or a genuine blind spot, a prompt asking “what argument usually follows this setup?” completes the half-finished template. To the author, that omission felt private or justified. To the model’s weights, the missing piece is a well-lit highway the author just drove off of. What feels private inside an author’s head looks to the model’s weights like driving straight off a well-lit highway. What makes a routine pattern completion feel like mind-reading is that we hide those detours from ourselves first. That effect gets sharpest whenever a technical choice hardens into professional identity. In Why Engineers Can’t Be Rational About Programming Languages , I wrote about why language debates behave more like tribal arguments than benchmarks. In a 2016 fMRI study on political beliefs (the closest well-studied analogue to identity-fused convictions), Kaplan, Gimbel, and Harris found that challenging strongly held political views, unlike non-political facts, increased activity in the default mode network (tied to self-identity), with greater insula and amygdala activity in people who resisted changing their minds. As Jonas Kaplan put it , “To consider an alternative view, you would have to consider an alternative version of yourself.” So we protect ourselves. We skip the inconvenient counterargument and gloss over the dual-use risk. We leave an escape hatch in our phrasing so we stay uncommitted if things go sideways. From inside our own heads, those omissions disappear into personal blind spots. To counter my own blind spots, I leaned on that collective mirror while building The 9 Cost Factors (and I’ll share the results across major languages soon). After years on the Go team at Google and maintaining Go tools, my bias toward Go is unquestionable. Left to myself, I over-index on what Go does well and at times rationalize away its friction. Running the nine economic factors through multiple LLMs let me pit the industry’s collective bias against my individual bias, surfacing trade-offs I would have edited out. Two different boundaries: prompt-level omissions sit inside the model’s weights, while true novelty sits outside them. Individual blind spots are negative space in the prompt , sitting squarely inside positive space in the weights . They are the things you missed or dodged that humanity already knows well enough for a model to predict. Projecting that statistical consensus onto your context window turns the model into a collective mirror for subtext and identity bias. True novelty is negative space in the weights . These are the unmapped ideas and intuitions nobody has articulated yet, outside the training distribution. Here, the model’s positive space stops acting like a mirror and pulls you back toward consensus. One caveat matters here: the weights aren’t a single monolithic consensus. Because a model absorbed many disciplines at once, it can still expose an industry blind spot by importing a familiar pattern from an adjacent field. Cross-domain synthesis still sits inside positive space in the weights, even when your own community missed it. True negative space in the weights is rarer: an idea none of those domains have articulated yet. The same mechanism that makes work is why AI struggles to originate breakthroughs. Reading a text’s shadow works because the model strongly expects what should come next . Breakthrough creativity happens when a human writes something with near-zero probability that isn’t a missing step from an old template. Start in positive space. Run a prompt like , or pit multiple models against your argument, before you ship a draft or commit to an architecture. Let the collective memory in the weights show you where you’re hedging and where your identity bent the framing. Two kinds of surprise: skipping a standard step vs. stepping off the edge of the map. Keep the mirror’s limit in view. Because the weights reflect collective consensus rather than truth, a model catches your personal blind spots fast and still misses gaps shared across the entire training corpus. Obey every omission it flags, and you’ll sand off what made your argument worth making. How do you tell an accidental omission from a deliberate leap when your own ego is an unreliable judge? Test whether you can state the missing premise out loud and argue against it fairly. If the critique makes you want to hide the caveat, you hit a blind spot. If you can name the consensus view cleanly and show why it breaks here, you’ve earned the detour. When your work surprises the model because you have something genuinely new to say, rather than something you forgot to admit, you’ve left positive space behind.

0 views
David Bushell 2 days ago

Where we’re going, we don’t need chatbots

“You’ve been working hard, why not take a weekend vacation!” Your chatbot says, after a 72 hour unattended session. It says that New York is nice this time of year. You ask it to book the cheapest flights. Half the airlines respond with a 429 code because your residential IP is part of five botnets. That’s odd you think, you only signed up to two that you can remember. For the other airlines, your chatbot was blocked by CAPTCHAs at all but one, where it successfully identified a pelican crossing on the six-hundredth and seventh loop. It tries to buy tickets but the React web UI silently errors. Unperturbed, your chatbot discovers a Github repo with API keys for Fedex. You’re booked as freight and must delivery yourself to the nearest depot 100 miles away. Based on your biometric data, your chatbot has estimated that you’ll comfortably fit into two 30×30cm boxes. You ask your chatbot to cancel the flight and rebook a business class ticket. It confirms that is has successfully cancelled the flight. A month later a Fedex invoice is emailed, but Outlook is down so the email bounces. In New York, whilst attempting to order a pistachio matcha latte with an avocado and kale bagel (mashed, not diced, gluten free on the top half) from a food cart chatbot in Central Park, you get talking to another chatbot enjoyer. The conversation gets boring when they started rambling on about the funny things their chatbot said. Looking for an excuse to leave, you ask your chatbot pendant what appointments you have later today. It says it can’t establish a Bluetooth connection to your phone. You excuse yourself anyway saying: “I’ll have my chatbots contact your chatbots.” Your chatbot open a Slack channel with the stranger’s chatbot and weeks are spent deliberating the intended purpose of this connection. Just as an hypothesis based on the 1998 rom-com You’ve Got Mail seems promising, you notice the errant session and kill it. Your chatbot pendant has run out of battery but your watch chatbot, after finally processing the previous request, alerts you of the audio immersion tour it booked at Ground Zero. You ask it to book a driverless Uber but when it doesn’t respond you flag down a minicab. You spend a poignant hour listening to the synthesised voice of Donald Trump read the Grokipedia page for 9/11. Somewhat skeptical of the source, you start a deep research chatbot to corroborate the facts. Your research chatbot cannot find any information for November 9th and writes its conclusion to dev/null. As you reach the memorial, chatbot Trump reaches the climax of his audio tour by blaming Biden and directs you to exit through the gift shop where they’re selling two-for-one golden Twin Tower merch. You ask the gift shop chatbot why one of the towers looks like Orthanc at Isengard. The chatbot explains a translation error when placing the order with its Chinese counterpart. Back at Central Park, a homeless man wins an argument with an automated food cart over the culinary values of kale. He was absolutely right. An Uber car arrives and he steps inside. Whilst walking around Times Square, an embedded billboard chatbot recognises your face and reminds you that you haven’t eaten today. You ask the chatbot to make a reservation at a restaurant recommended by Google’s AI overview. The first recommendation is fully booked years in advance due to a prompt caching error. The second recommendation turns out to be a fish market. The third recommendation is Dorsia , which you’re pretty sure is a fictional establishment from the 2000 horror film American Psycho . You settle on the fourth recommendation describe as “Greek-Mexican fusion”. This delightful family run eatery advertises with gen-AI imagery of Tortilla wrapped Gyros and Halloumi Tacos in the style of Studio Ghibli. You order the Bean Moussaka from the waiting chatbot which compliments you on your exquisite taste. The chatbot reads the soft drink menu and you decline each option. You repeat the process for the hard drink menu, the cocktail menu, the coffee menu, and the soft drink menu again, before asking for a glass of tap water. The chatbot compliments you on your exquisite taste. You finally arrive at your hotel and the reception kiosk chatbot is out of order. Luckily, its final act appears to have been to release all keycards from the automated dispenser. You fish through the pile spilled on the hotel lobby floor and find your keycard printed with your full name, address, and passport number. You enter your hotel room and command: “Computer, lights!” After thirty seconds of no response you manually switch on the lights. The hotel room chatbot then replies: “Aye, captain.” and turns off the lights. The lights in your apartment back home also flicker. You climb into bed and unfold your new travel USB multi-charger onto the bedside table. You place your pendant chatbot into the lower socket, hang your watch chatbot on one arm, and rest your phone on the central platform. The multi-charger chatbot asks if you would like it to slow charge at off-peak hours. You ask it if the hotel has any hidden fees for electricity usage. It requests root permissions and begins to recite terms and conditions. You ask it to stop but it’s no longer listening so you move it into the bathroom where it continues to read terms in multiple languages all night. You doomscroll X for an hour until you read a horrifying story of an Uber Tesla catching fire and burning a man to death inside. According to witnesses, the first responder chatbots refused to help citing AI safety guardrails and the dangers of fire, advising to dial 911 in an emergency. Several bystanders attempted to redial, only to hear the same message. You ask your phone chatbot to set an alarm for 7am. You hear the faint voice of Siri from the adjacent room saying that is has ‘found some web results for “alarm for 7am.”’ Thanks for reading! Follow me on Mastodon and Bluesky . Subscribe to my Blog and Notes or Combined feeds.

0 views