惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

B
Blog RSS Feed
D
Darknet – Hacking Tools, Hacker News & Cyber Security
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
G
Google Developers Blog
MyScale Blog
MyScale Blog
Google DeepMind News
Google DeepMind News
J
Java Code Geeks
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
C
Check Point Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
P
Proofpoint News Feed
D
Docker
Jina AI
Jina AI
博客园 - 三生石上(FineUI控件)
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
Help Net Security
Help Net Security
Google DeepMind News
Google DeepMind News
L
LINUX DO - 最新话题
T
Tailwind CSS Blog
N
Netflix TechBlog - Medium
Forbes - Security
Forbes - Security
MongoDB | Blog
MongoDB | Blog
Attack and Defense Labs
Attack and Defense Labs
Webroot Blog
Webroot Blog
A
About on SuperTechFans
Schneier on Security
Schneier on Security
Hacker News - Newest:
Hacker News - Newest: "LLM"
Microsoft Azure Blog
Microsoft Azure Blog
F
Fortinet All Blogs
IT之家
IT之家
The Last Watchdog
The Last Watchdog
腾讯CDC
Microsoft Security Blog
Microsoft Security Blog
Project Zero
Project Zero
B
Blog
Recorded Future
Recorded Future
博客园_首页
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
S
SegmentFault 最新的问题
Security Archives - TechRepublic
Security Archives - TechRepublic
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
H
Hacker News: Front Page
T
Threatpost
H
Heimdal Security Blog
Cloudbric
Cloudbric
Google Online Security Blog
Google Online Security Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
V
V2EX
云风的 BLOG
云风的 BLOG
V
Visual Studio Blog

Hacker News

Introducing Claude Opus 4.7 Qwen Studio The Future of Everything is Lies, I Guess: Where Do We Go From Here? GitHub - SeanFDZ/macmind: Single-layer transformer in HyperTalk for the classic Macintosh Show HN: Agent-cache – Multi-tier LLM/tool/session caching for Valkey and Redis Moving a large-scale metrics pipeline from StatsD to OpenTelemetry / Prometheus GitHub - Nightmare-Eclipse/RedSun: The Red Sun vulnerability repository GitHub - SethPyle376/hiraeth: Local AWS emulator focused on fast integration testing, with SQS support, SQLite-backed state, and a debug-friendly web UI. GitHub - macOS26/Agent: Any AI, replaces Claude Code, Cursor, OpenClaw. Over 18 LLM providers (Claude, OpenAI, Gemini, Ollama, Zai, HF, Qwen) wired into a native Mac app that writes code, builds Xcode projects, bumps versions, manages git, automates Safari, use AppleScript, JS or Accessibility, extend Agent! w/ MCP Servers, run tasks from your iPhone via Messages. YouTube now lets you turn off Shorts I Made a Terminal Pager Burgers | マクドナルド公式 Commands — HackerNews CLI documentation ChatGPT for Excel PiCore - Raspberry Pi Port of Tiny Core Linux Live Nation illegally monopolized ticketing market, jury finds Google Broke Its Promise to Me. Now ICE Has My Data. Founding Engineer at Adaptional | Y Combinator CRISPR takes important step toward silencing Down syndrome’s extra chromosome GitHub - saffron-health/libretto: The AI toolkit for building reliable browser automations US v. Heppner (S.D.N.Y. 2026) no attorney-client privilege for AI chats [pdf] Unexpected €54k billing spike in 13 hours: Firebase browser key without API restrictions used for Gemini requests Retrofitting JIT Compilers into C Interpreters IPv6 – Google The Accursèd Alphabetical Clock Cybersecurity Looks Like Proof of Work Now Fragments: April 14 Cal.com Goes Closed Source: Why AI Security Is Forcing Our Decision | Cal.com - Scheduling Software for Online Bookings Laravel raised money and now injects ads directly into your agent When moving fast, talking is the first thing to break Too much Discussion of the XOR swap trick – Heather Cafe Introduction to Spherical Harmonics for Graphics Programmers The Grand Line Building a Z-Machine in the worst possible language High-Level Rust: Getting 80% of the Benefits with 20% of the Pain GitHub - duguyue100/midnight-captain: Inspired by Midnight Commander, tailored to my taste. How to build a `git diff` driver · Jamie Tanna | Software Engineer Center for Responsible, Decentralized Intelligence at Berkeley The Local Universe’s Expansion Rate Is Clearer Than Ever, but Still Doesn’t Add Up - A new synthesis of astronomical measurements confirms a persistent mismatch that could point to physics beyond current models The air throughout our homes is infused with microplastics. But there are things you can do to breathe less of them The disturbing white paper Red Hat is trying to erase from the internet – OSnews The Future of Everything is Lies, I Guess: Annoyances ‘Abhorrent’: the inside story of the Polymarket gamblers betting millions on war Productive procrastination — Max van IJsselmuiden maps, territory and LMs 447 Terabytes per Square Centimetre at Zero Retention Energy: Non-Volatile Memory at the Atomic Scale on Fluorographane Show HN: Pardonned.com – A searchable database of US Pardons 20 Years on AWS and Never Not My Job The Seasons are Wrong Artemis II crew splashes down near San Diego after historic moon mission We gave an AI a 3 year retail lease in SF and asked it to make a profit | Andon Labs How a dancer with ALS used brainwaves to perform live On filing the corners off my MacBooks Installing every* Firefox extension OpenClaw’s memory is unreliable, and you don’t know when it will break Steve Blank Nowhere Is Safe Chimpanzees in Uganda locked in vicious 'civil war', say researchers watgo - a WebAssembly Toolkit for Go linux/Documentation/process/coding-assistants.rst at master · torvalds/linux GitHub - callumlocke/json-formatter: Makes JSON easy to read. Founding Product Engineer at Bild AI | Y Combinator A compelling title that is cryptic enough to get you to take action on it GitHub - Keychron/Keychron-Keyboards-Hardware-Design: Industrial design files for Keychron keyboards and mice. 100+ models with CAD assets in STEP, DXF, DWG, and PDF. Source-available, with commercial use allowed for original compatible accessories within the license terms. [ANNOUNCE] WireGuardNT v0.11 and WireGuard for Windows v0.6 Released 1D-Chess Helium Is Hard to Replace Cooperative Vectors Introduction | Evolve Keeping a Postgres queue healthy — PlanetScale Our response to the Axios developer tool compromise Do Americans read print books, e-books or audiobooks more? The Zettelkasten Method in Obsidian: A Practical Setup Guide Artemis II Is Competency Porn and We Are Starving For It WeakC4 Flight Viz — Cockpit View A Mexican surveillance giant you’ve never heard of is now watching the U.S. border Surelock: Deadlock-Free Mutexes for Rust RISC-V 101 – what is it and what does it mean for Canonical? | Ubuntu The Problem That Built an Industry How Much Linear Memory Access Is Enough? | Solidean Investigating Split Locks on x86-64 Simplest hash functions Sybilproof reputation mechanisms (2005) [pdf] What is a property? How Complex is my Code? Static code analysis in Kotlin — tools overview Toffoli gates are all you need PGLite evangelism dcmake: a new CMake debugger UI Clojure on Fennel part one: Persistent Data Structures Fragments: April 2 Python Release Python install manager 26.1 The Life and Death of the Book Review - Liberties Introducing Database Traffic Control — PlanetScale Bitcoin miners are losing $19,000 on every BTC produced as difficulty drops 7.8% God sleeps in the minerals Building slogbox Apple Silicon and Virtual Machines: Beating the 2 VM Limit Who was “Not Even Wrong” first? Pokemon Evolution Vs Darwinian Evolution The APL Programming Language Source Code
Bitter Lessons from the ISSpresso
2026-05-07 · via Hacker News

The Italian space agency’s official technical report on designing the ISSpresso barely masks their astronauts’ horror at the conditions they found when they first drifted aboard the International Space Station. The Americans were up there drinking instant coffee, like animali.

After two years, four prototypes, and a great deal of paperwork, Lavazza and the Italian space agency sent a proper espresso machine to the ISS in 2015. On Earth, a basic Lavazza espresso maker costs about $150 and weighs 3.5 kilograms. The coffee machine’s spaceborne cousin was a 20kg box about the size of an oven. The cost to build it was not disclosed, but was likely in the single-digit millions

Behold the ISSpresso

Asking how a coffee machine got to be so huge and expensive in space is a good way of understanding the cost drivers in human space flight.

Espresso machines are not particularly lethal on Earth, but almost anything on the space station can kill the crew if it’s built wrong. So the ISSpresso had to prove to NASA’s satisfaction that it would not take out the station’s electrical system, interfere with the radio, leak boiling water, catch fire, dazzle the crew with bright lights, electrocute anyone, be dangerously hot, make loud noises, emit noxious gas, shatter into fragments, smell weird, or shake apart in the harsh conditions at launch. (The sharp pin that punctures the coffee capsule required a special safety waiver.)

The authors of the technical paper on ISSpresso include a list of some of the NASA standards they had to comply with to get their machine certified for launch and orbital coffeemaking.

These documents are not light reading. It can be tempting to dismiss them as NASA run wild, and there are certainly some requirements (like handle shape or enclosure color) that seem arbitrary. There is also a lot of bureaucratic connective tissue, like the standards for harmonizing processes between NASA and the European and Japanese space agencies, who all build their hardware to slightly different specs.

But most of the technical requirements in this list have substance. They fall into a few broad categories:

  • Making sure nothing on the payload damages the space station, either in normal operation or if something goes haywire.

  • Lots and lots of fussiness about electrical behavior and electromagnetic interference.

  • Consistency in interface design with other ISS hardware.

  • Demanding proof that the ISSpresso can take a physical beating (especially during launch), endure kicks from astronaut feet, sudden decompression to vacuum, abrupt surges or sags in voltage and water pressure, and other environmental insults.

  • Ensuring the heating element doesn’t burn anything or set itself on fire. This is a trickier requirement in space, where air doesn’t cool things by convection.

  • Fluid handling requirements specific to the zero g environment. The ISSpresso has to contain spills and not fill the cabin with a mist of boiling water. It also has to play nice with ISS plumbing.

  • Astronaut-proofing the enclosure, which will inevitably be kicked and used as a handhold. This includes making sure nothing can hurt a clumsy astronaut (sharp edges, pointy switches, pinch points) or break if it’s yanked on.

  • Proving that the ISSpresso won’t shake apart during launch or damage whatever it launches with.

  • Antimicrobial measures for all wetted surfaces and plumbing.

  • Basic OSHA-type stuff like noise limits.

None of these requirements are frivolous, and some of them reflect dangers unique to spaceflight. If the plastic cover shatters on your espresso maker back home, you’ll be mildly inconvenienced. But if that cover shatters in space, it can pose an acute inhalation and eye hazard.

The many technical requirements are enforced by the Safety Review Process, itself a highly regimented standard. The Process takes designers through a series of project milestones and official reviews that ultimately satisfy NASA that each requirement on their lists has been met.

The Safety Review Process begins with a friendly chat about general design ideas, and then ratchets up in rigor and unpleasantness. By the final milestone, a NASA bureaucrat is shining a light bulb in your face and screaming at you to confess everything you know about mission risk. It’s not enough to tell NASA that you plan to put your payload on a truck and drive it to Kennedy Space Center for launch; you have to analyze the g-forces for every crane movement and specify how fast the truck will go. Any conceivable failure mode has to be identified in a Hazard Report, along with the proposed fix, and that fix has to be certified.

A helpful flowchart from a NASA safety document (SSP 52005 Revision C) showing how to handle fracture risk

There is a truism in aerospace: when you pay $500 for an aviation-certified thumbtack, what you’re really paying for is the ten binders of compliance documents, certifications, and tests that accompany it through the production process, along with a promise that someone will go to jail if any part of that process is falsified.

The Process is painful, but it’s not unique to NASA. We run versions of it in aviation, military, and medical contexts, wherever human lives are at stake. It is often ridiculous and everyone hates it. But some version of it is the only way to be sure systems behave as intended.

Let me illustrate this with a moving personal anecdote!

I live in a solar-powered home in rural New Mexico. The house is not connected to the electrical grid; instead, power from solar panels feeds a rack of batteries, and a machine called an inverter draws power from the batteries and turns it into household current.

The solar system in my home is supposed to be decoupled. One wall of the electrical closet has all the solar gear; the other has a standard junction box with circuit breakers like you find in a normal home. From the house’s perspective, alternating current flows in just like it would from a power line. And on the solar side of the system, the inverter doesn’t know or care about what’s happening inside the house. As long as the total power draw stays under a generous maximum, everything is supposed to just work.

That’s the theory.

But after upgrading the inverter last year, I found myself beset by electrical gremlins. A few times a day the lights would dim, and I could hear the pump in my aquarium start to make a choking noise. At those times, a display on the inverter showed the A/C voltage dipping. Sometimes the inverter would reboot, taking down power for the whole house for a minute. There was no discernible pattern in when or how often this happened.

I thought I could live with the problem until it started killing my furnace. The first couple of times, the victim was a transformer, a $25 part on the circuit board that I learned to replace myself. But the third time around, the voltage drop burned out the entire logic board, forcing an expensive repair that left me without heat for a week.

At this point it was November, and heating the house had become a game of Russian roulette. I knew that every minute the furnace stayed on, a blip in the electrical system might kill it. No one I talked to could identify a cause. I had to figure out what was causing the drops in voltage before the house became unlivable.

Being a software guy, I decided to try binary search. I turned off half the circuit breakers to the house one day, then the other half the next, to see which side the problem was on. Soon I had isolated it to one part of the house, and then to a single circuit in the bathroom.

There I found the culprit: a Japanese shower toilet.

The toilet had a small heating element that turned on and off to keep the water in the bidet attachment and seat warm. Whenever the heater came on, its modest appetite for electricity was somehow enough to destabilize the inverter, which then briefly delivered lower voltage to the entire rest of the house. While most appliances could handle these dips, the furnace could not, and died dramatically. Even though the toilet’s power demand was low, there was something about its Japanese expectations for voltage and frequency (just a little bit off the US standard) that made the American-made inverter crazy.

Figuring that out took me several weeks and a few thousand dollars. My mistake was believing that the power system really was decoupled—that nothing in the house could affect things upstream of the junction box. That is what the inverter specs and circuit diagrams all said. That is what customer support told me. But it wasn’t true.

Since that time, I’ve learned that small heaters (like coffee makers or kettles) can be kryptonite to an inverter, and that this is common folk knowledge among solar installers. But the consequence, that a guest can do damage to my home by plugging in a hair dryer, is still unsettling and counterintuitive.

This is the class of problem all those NASA interface requirements are trying to forestall. If you’ve ever had a faulty wiring harness in your car (hello Jeep owners!) you know what a nightmare it is to try to chase down intermittent, poorly localized faults. NASA inflicts eye-watering certification costs on itself and its partners to avoid trying to diagnose this stuff in space, where half the systems can’t be powered off, and where there’s a high chance of killing the crew if you break something.

Undoubtedly, some proportion of NASA’s Safety Review Process is overkill. But even if we could cut regulatory overhead by 75%, a device like the ISSpresso would still cost a few hundred thousand dollars to develop and end up built like a tank. The blast radius of malfunctioning hardware on human-rated spacecraft is simply too big to avoid doing some version of the safety dance.

This has uncomfortable consequences for space dreamers.

There is a widespread belief that launch costs are what has been holding back space exploration, and a corresponding excitement now that they are dropping by a potential two orders of magnitude. Many SpaceX fans in particular believe that Starship solves every problem by being huge and cheap. And they are partially right! It would be much easier to send people to Mars on a 1200 ton rocket than to try to fit all the equipment they need into a 60 ton transit habitat engineered like a Swiss watch.1

But cheap launches can’t solve the equipment problem. Ultimately, whatever we put inside the spacecraft has to work as advertised, and until we have hundreds of person-years of experience living in space habitats, the only way to guarantee that will be an expensive process of flight qualification and testing.

That means future human missions to space will have the same cost profile as big space telescopes do today—a few hundred million spent to launch stuff, and billions spent inventing equipment and trying to get it to work right.

A view of the impressive internal plumbing on the ISSpresso

Like all our problems, this one gets worse on Mars.

The defining feature of a human mission to Mars is that risks are sequential and cumulative. Every link in the chain has to go right, or the mission fails. This means early visits to Mars will have safety and reliability requirements that make the Space Station look like a middle school science fair.

These requirements will be especially tight for the surface part of a mission. Any equipment that lands on Mars will have to demonstrate that it can launch from Earth, sit dormant for six months, survive entry and landing, and then work in partial gravity and dust without breaking for 17 months. Machinery that is pre-positioned on Mars in advance of the crew (a common risk-cutting measure in mission designs) will also have to prove that it can sit out in the weather for two or more years.

To make matters worse, any payloads sent to the surface will be severely constrained by weight. This is not for want of big rockets to send them to Mars, but a consequence of the fact that landing heavy payloads is hard, with the difficulty going up as some integer exponent of the landed mass.2

Whenever you need a combination of light weight, reliability, and autonomy in a space context, it is time to bring your wallet to your lips and kiss it goodbye. We saw an example of this last week in the context of Mars Sample Return, where a rover whose sole purpose was to move a few titanium tubes from the ground into a box wound up costing half a billion dollars.

The same pathology is going to bedevil us when we finally get to Mars, even if launches there from Earth are free.

Astronaut Samantha Cristoforetti enjoys a space espresso aboard the ISS

It’s pretty frustrating to enter an era of cheap rockets and still not be able to do fun things. Early Mars concepts (like NASA’s Design Reference Architectures) agonized over how to fit the mission into the minimum number of launches, which were the most expensive line item in the budget.

If Starship and New Glenn succeed, we can have all the mission mass we want. But that just runs us into the next-biggest item on the cost list, the reliability and testing issues that are the subject of this post.

So what do we do to make certification and testing cheaper?

  1. Fly more. If there are a dozen space stations that all need an espresso maker, then that makes designing ISSpresso 2.0 and later models much easier. A proven flight record replaces a lot of first-principles testing.

  2. Fly more robots. Robots don’t drink coffee, but there are science missions that could use a pressurized hot water source, and validating such equipment where it doesn’t pose risk to astronauts makes it easier to adapt it for human space flight later. This holds for all kind of devices and sensors that would be useful on manned spacecraft.

  3. Learn to land on Mars. Right now we can land 2-3 tons on Mars at a time, in an error ellipse that is about 20 kilometers long. For a realistic human mission, we need to be able to land 100 tons or more at 100-meter precision, so that we can pre-position equipment and land in our favorite crater. This capability would also make it cheap to send big dumb robots in large numbers to Mars, instead of the very expensive, artisanally hand-crafted robots we send now.

  4. Fix the safety ratchet. It is easy to add safety constraints and hard to undo them. You and I will probably die before we’re allowed to take a bottle of water through airport security again.

    Many NASA rules around software reliability date back to the 1970s and don’t make sense in the smartphone era. Harsh limits on electromagnetic interference impose a testing burden on innocent components that probably don’t need it. And some of restrictions on flammability and wiring are a hangover from the Apollo I fire in 1967. There needs to be a mechanism for relaxing rules to adapt to changing conditions, or else the space program will fossilize in its own paperwork.

  5. Let amateurs fly stuff. People are inventive, and we should let gifted engineers try things in space without interference from the safety bureaucracy, as long as they don’t hurt anyone. Hopefully the new era of cheap launches will enable some risk-taking and invention by talented amateurs, and the stuff that doesn’t blow up can then carry over into our official space program.

  1. The technical paper on designing the ISSpresso is very readable and fun. ISSpresso Development and Operations (2015) DOI 10.1016/S2468-8967(16)30038-6

  2. For more on the special challenges of handling liquids in space, along with the vaguely vaginal coffee cup invented for space use, see How Advances in Low-g Plumbing Enable Space Exploration (2022) DOI 10.1038/s41526-022-00201-y

  3. Behold in all its splendor the Pressurized Payloads Interface Requirements document for ISS.

1

50-80 tons is a common Mars transit habitat size in NASA studies. I would describe it as ‘snug’. For reference, the Orion space capsule weighs 10 tons, and the International Space Station about 400 tons.

2

I don’t know what the integer is. Consider that momentum goes up as the square of mass, or that aerodynamic heating goes up as the fourth power of entry velocity.

No posts