<a href="https:&#x2F;&#x2F;openai.com&#x2F;index&#x2F;openai-to-acquire-astral&#x2F;" rel="nofollow">https:&#x2F;&#x2F;openai.com&#x2F;index&#x2F;openai-to-acquire-astral&#x2F;</a>

Astral to Join OpenAI

An update on Steam / GOG changes for OpenTTD

Kitten TTS (<a href="https:&#x2F;&#x2F;github.com&#x2F;KittenML&#x2F;KittenTTS" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;KittenML&#x2F;KittenTTS</a>) is an open-source series of tiny and expressive text-to-speech models for on-device applications. We had a thread last year here: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=44807868">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=44807868</a>.Today we&#x27;re releasing three new models with 80M, 40M and 14M parameters.The largest model (80M) has the highest quality. The 14M variant reaches new SOTA in expressivity among similar sized models, despite being &lt;25MB in size. This release is a major upgrade from the previous one and supports English text-to-speech applications in eight voices: four male and four female.Here&#x27;s a short demo: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=ge3u5qblqZA" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=ge3u5qblqZA</a>.Most models are quantized to int8 + fp16, and they use ONNX for runtime. Our models are designed to run anywhere eg. raspberry pi, low-end smartphones, wearables, browsers etc. No GPU required! This release aims to bridge the gap between on-device and cloud models for tts applications. Multi-lingual model release is coming soon.On-device AI is bottlenecked by one thing: a lack of tiny models that actually perform. Our goal is to open-source more models to run production-ready voice agents and apps entirely on-device.We would love your feedback!

Show HN: Three new Kitten TTS models – smallest less than 25MB

How to Not Pay Your Taxes

OpenBSD: PF queues break the 4 Gbps barrier

World Happiness Report 2026

Juggalo Makeup Blocks Facial Recognition Technology (2019)

UK's Ofcom has today fined 4chan £450k for not having age checks in place

Hey HN! We’re Hayden, Ronan, Avi, and Warren of Voltair (<a href="https:&#x2F;&#x2F;voltairlabs.com&#x2F;">https:&#x2F;&#x2F;voltairlabs.com&#x2F;</a>). We’re making weatherized, hybrid-fixed drones deployed for power utility inspections.Here’s some footage: <a href="https:&#x2F;&#x2F;vimeo.com&#x2F;1173862237&#x2F;ac28095cc6?share=copy&amp;fl=sv&amp;fe=ci" rel="nofollow">https:&#x2F;&#x2F;vimeo.com&#x2F;1173862237&#x2F;ac28095cc6?share=copy&amp;fl=sv&amp;fe=...</a> and a photo of our latest prototype: <a href="https:&#x2F;&#x2F;imgur.com&#x2F;a&#x2F;bYHnqZ4" rel="nofollow">https:&#x2F;&#x2F;imgur.com&#x2F;a&#x2F;bYHnqZ4</a>.The U.S. has 7M miles of power lines (enough to go to the moon and back 14 times), and they&#x27;re aging. Over 50% of all power flows through transformers that are at least 30 years old, which is about when they start to fail.Power line conductors are just bare metal with 4,000-765,000 volts sitting on ceramic insulators, usually held up by pieces of wood. It’s a cost effective and relatively reliable way to move power. But when the wood starts to rot, or the cotter pin falls out, and a live conductor is dropped on a dead tree on a windy day, you get devastating wildfires like the Palisades Fire in LA last year.Most utilities solve this problem with foot patrols. Linemen drive out with a clipboard or an iPad, and run through a checklist with binoculars to visually confirm everything is in order. A lineman can inspect about 50-150 poles per day, yet even the smallest rural electric cooperatives (with about ~20 employees) have about 50,000 distribution poles. Clearly the math doesn’t work out. As a result, a given utility pole is inspected about every 10 years (at least that’s what they tell their insurance adjuster).Helicopters are also used, but cost $25k to get off the ground, and more importantly, every year linemen die in helicopter crashes. Satellites can’t deliver the mm precision needed for these inspections. So drones have emerged as the best solution. Georgia Power saved 60% on operating expenses when they switched to using drones, and Xcel power found drones to find 60% more defects than foot patrols (because of pole-top vantage point).Problem #2: Drones are held back by the need to constantly recharge and FAA beyond-visual-line-of-sight (BVLOS) regulations. In response, the most well funded utilities (e.g., PG&amp;E, SCE) primarily send out pilots in trucks to collect the data.Current leaders in the drone space – Skydio and DJI – have built drone-in-a-box solutions. Their charging stations have inherent concurrency constraints (only one drone at a time) and don’t scale easily over large land areas. Skydio charges $250,000 &#x2F; box, and has a there-and-back range of about 15 miles (assuming ideal performance). They are expensive and inflexible.Our first solution (and why it didn’t work): We entered YC wanting to build drones that charge inductively from the magnetic fields around power lines. We used a split-core current transformer, wrapped it around the conductor with a clamp, and harvested power. We spent about 4 months testing and developing this hardware, and successfully recharged a few batteries in the field. It was a really cool proof of concept.But we ran into a big problem. There’s not enough current on distribution lines! These are the wooden poles outside your home, as opposed to the tall steel transmission towers you might see in the countryside. Generally speaking, we needed about a MW of power – or about 1000 homes – to flow through the lines to charge our drone performantly.We also found the risk-reward calculus didn’t make sense for utilities. Line attachments (and even inductive power harvesting) is common in the utility space. Fault indicators and smart sensors like the Heimdall Power “Neuron” do this. But they are installed one time with lineman supervision and left in place for years. The risk of landing a drone multiple times per day at myriad points around the network felt too risky for utility engineers.We wondered if we could solve the range and battery swap issue from another angle. Reexamining drone-in-a-box solutions, we realized they had the tech backwards: expensive, overengineered boxes to protect fragile drones. A network of these big enough to cover a utility’s service area would cost hundreds of millions, and the drones still wouldn’t be able to fly when it matters most (during a wildfire, storm, or power outage). What if instead, the drone was ultra-rugged while the charging stations were cheap and attritable?What we’re building now: We’re making weatherized, long-range (well over 70 miles), fixed-wing drones that can live outside for months at a time. They recharge inductively (no connections or moving parts) on stripped-down charging pads that cost a couple thousand dollars apiece. It doesn’t take many of these pads along a transmission line corridor for our drones to hop between them and inspect the entire length. We reason we could cover the continental U.S. with about 1000-5000 pads.Having dedicated charging stations also solves the backhaul problem. When you LiDAR scan and take high-res photos of 50 miles of transmission corridor, you accumulate terabytes of data. Manual drone operators can pull out the SD card. We have to offload it wirelessly. Trying to do this directly from the drone over spotty LTE doesn’t work. Instead, we use the charging station as an intermediary, dumping the data from our drone to a hard drive on the station over a high-speed WiFi link. The station can then push this to our servers over Starlink, LTE, or a fiber link asynchronously, freeing the drone to get back in the field and inspect more.One cool thing we can do this way is reactive inspections. If there’s a weird harmonic on a feeder, or a utility needs a rapid scan after a storm, we can get on-site within minutes to inspect. Contractors often spend months coordinating their on-site data collection, and dedicated storm response contractors are very expensive to keep on-site.Power utilities are our first customers, but the applications for telecom, rail, oil+gas, forestry, search+rescue, and agriculture are also exciting. One thing that’s not exciting is a drone surveillance state. Unfortunately, we are now in a world where drones are increasingly weaponized, and examples of government overreach are numerous (case in point: Sonoma County, California spying on landowners). We have zero interest in supporting uses like this.(Our backstory, if you’re interested: Ronan has always had an unhealthy obsession with flying machines, from designing remote controlled planes growing up, to building eVTOL tech for DARPA and the Air Force while still a university student. Warren and Ronan met during a startup competition with a UAV solution in agriculture. Hayden, a childhood friend of Ronan, was deeply ingrained in the power utility space, and realized the true pain point there. Shortly after graduating, Ronan, Hayden, and Warren quit their jobs to take the idea full time in the Summer of 2025. Around the same time Avi dropped out of college, bringing sales skill and regulatory expertise as our fourth cofounder.)We just secured our first major contract and are working out the details of pilots with some big utilities. Our first paid flight is mid-April. Our business model is straightforward: inspection as a service. We charge per pole or tower.We are very interested in your opinion! Maybe some of you all work in the energy industry and know a thing or two about infrastructure inspections that we could learn from? We’d love all feedback (good and bad).

Launch HN: Voltair (YC W26) – Drone and charging network for power utilities

Prompt Injecting Contributing.md

The Shape of Inequalities

One of those &#x27;woke up to MacOS updates&#x27; and finding none of my dockers are reachable via dnsmasq (which I use), and low and behold, an update silently breaks custom dns resolution. Hopefully Apple will listen to the bug report I&#x27;ve made. Hold off on updating if you use this…

macOS 26 breaks custom DNS settings including .internal

Scaling Karpathy's Autoresearch: What Happens When the Agent Gets a GPU Cluster

Android: Balancing Openness and Choice with Safety

Noq: n0's new QUIC implementation in Rust

Return of the Obra Dinn: spherical mapped dithering for a 1bpp first-person game

Hey HN! We&#x27;re Aakash and Viswesh, and we&#x27;re building Canary (<a href="https:&#x2F;&#x2F;www.runcanary.ai">https:&#x2F;&#x2F;www.runcanary.ai</a>). We build AI agents that read your codebase, figure out what a pull request actually changed, and generate and execute tests for every affected user workflow.Aakash and I previously built AI coding tools at Windsurf, Cognition, and Google. AI tools were making every team faster at shipping, but nobody was testing real user behavior before merge. PRs got bigger, reviews still happened in file diffs, and changes that looked clean broke checkout, auth, and billing in production. We saw it firsthand. We started Canary to close that gap. Here&#x27;s how it works:Canary starts by connecting to your codebase and understands how your app is built: routes, controllers, validation logic. You push a PR and Canary reads the diff, understands the intent behind the changes, then generates and runs tests against your preview app checking real user flows end to end. It comments directly on the PR with test results and recordings showing what changed and flagging anything that doesn&#x27;t behave as expected. You can also trigger specific user workflow tests via a PR comment.Beyond PR testing, tests generated from the PR can be moved into regression suites. You can also create tests by just prompting what you want tested in plain English. Canary generates a full test suite from your codebase, schedules it, and runs it continuously. One of our construction tech customers had an invoicing flow where the amount due drifted from the original proposal total by ~$1,600. Canary caught the regression in their invoice flow before release.This isn&#x27;t something a single family of foundation models can do on its own. QA spans across many modalities like source code, DOM&#x2F;ARIA, device emulators, visual verifications, analyzing screen recordings, network&#x2F;console logs, live browser state etc. for any single model to be specialized in. You also need custom browser fleets, user sessions, ephemeral environments, on-device farms and data seeding to run the tests reliably. On top of that, catching second-order effects of code changes requires a specialized harness that breaks the application in multiple possible ways across different types of users that a normal happy path testing flow wouldn&#x27;t.To measure how well our purpose built QA agent works, we published QA-Bench v0, the first benchmark for code verification. Given a real PR, can an AI model identify every affected user workflow and produce relevant tests? We tested our purpose-built QA agent against GPT 5.4, Claude Code (Opus 4.6), and Sonnet 4.6 across 35 real PRs on Grafana, Mattermost, Cal.com, and Apache Superset on three dimensions: Relevance, Coverage, and Coherence. Coverage is where the gap was largest. Canary leads by 11 points over GPT 5.4, 18 over Claude Code, and 26 over Sonnet 4.6. For full methodology and per-repo breakdowns give our benchmark report a read: <a href="https:&#x2F;&#x2F;www.runcanary.ai&#x2F;blog&#x2F;qa-bench-v0">https:&#x2F;&#x2F;www.runcanary.ai&#x2F;blog&#x2F;qa-bench-v0</a>You can check out the product demo here: <a href="https:&#x2F;&#x2F;youtu.be&#x2F;NeD9g1do_BU" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;NeD9g1do_BU</a>We&#x27;d love feedback from anyone working on code verification or thinking about how to measure this differently.

Launch HN: Canary (YC W26) – AI QA that understands your code

<a href="https:&#x2F;&#x2F;www.nytimes.com&#x2F;2026&#x2F;03&#x2F;19&#x2F;us&#x2F;afroman-trial-lemon-cake-verdict.html" rel="nofollow">https:&#x2F;&#x2F;www.nytimes.com&#x2F;2026&#x2F;03&#x2F;19&#x2F;us&#x2F;afroman-trial-lemon-ca...</a><a href="https:&#x2F;&#x2F;www.washingtonpost.com&#x2F;national-security&#x2F;2026&#x2F;03&#x2F;18&#x2F;afroman-lawsuit-deputies-raid-ohio&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.washingtonpost.com&#x2F;national-security&#x2F;2026&#x2F;03&#x2F;18&#x2F;...</a>

Afroman found not liable in defamation case

Love of corporate bullshit is correlated with bad judgment

Consensus Board Game

There&#x27;s a lot of work happening around both generative UI and code execution for AI agents. I kept wondering: how do you bring them together into a fully featured architecture? I built a prototype:- Markdown as protocol — one stream carrying text, executable code, and data- Streaming execution — code fences execute statement by statement as they stream in- A mount() primitive — the agent creates React UIs with full data flow between client, server, and LLMLet me know what you think!

I turned Markdown into a protocol for generative UI

Ramtrack.eu – RAM Price Intelligence

Hyper-optimized reverse geocoding API

What if Python was natively distributable?

Conway's Game of Life, in real life

I run a building design consultancy. I got tired of paying Wix $40&#x2F;month for a brochure that couldn’t answer simple service questions, and me wasting hours on the same FAQs.So I killed it all and spent 4 months building a &#x27;talker&#x27;: <a href="https:&#x2F;&#x2F;axoworks.com" rel="nofollow">https:&#x2F;&#x2F;axoworks.com</a>The stack is completely duct-taped: Netlify’s 10s serverless timeout forced me to split the agent into three pieces: Brain (Edge), Hands (Browser), and Voice (Edge). I haven’t coded in 30 years. This was 3 steps forward, 2 steps back, heavily guided by AI.The fight that proved it worked: 2 weeks ago, a licensed architect attacked the bot, trying to prove my business model harms the profession. The AI (DeepSeek-R3) completely dismantled his arguments. It was hilariously caustic.Log: <a href="https:&#x2F;&#x2F;logs.axoworks.com&#x2F;chat-architect-vs-concierge-v147.html" rel="nofollow">https:&#x2F;&#x2F;logs.axoworks.com&#x2F;chat-architect-vs-concierge-v147.h...</a>A few battle scars:* Web Speech API works fine, right up until someone speaks Chinese without toggling the language mode. Then it forcefully spits out English phonetic gibberish. Still a headache.* Liability is the killer. Hallucinate a building code clause? We’re dead. Insurance won’t touch us.* We publish the audit logs to keep ourselves honest and make sure the system stays hardened.Audit: <a href="https:&#x2F;&#x2F;logs.axoworks.com&#x2F;audit-2026-02-19-v148.html" rel="nofollow">https:&#x2F;&#x2F;logs.axoworks.com&#x2F;audit-2026-02-19-v148.html</a>The hardest part was getting the intent right: making one LLM pivot seamlessly from a warm principal’s tone with a homeowner, to a defensive bulldog when attacked by a peer. That took 2.5 months of tuning.We burn through tokens with an &#x27;Eager RAG&#x27; hack (pre-fetching guesses) just to improve responsiveness. I also ripped out the “essential” persistent DBs—less than 5% of visitors ever return, so why bother? If a client drops mid-query, their session vanishes. No server-side queues.The point: To let me operate with a network of seasoned pros, and trim the fat.Try to break it. I’ll be in the comments. Kee