With that kind of airflow and consistent temperature I would suspect the failure rates to be incredibly small on those batteries - typically what kills them is extreme temperatures and high C charge/discharge at high temperature deltas (as measured from 25'C) which is where the cells have lowest degredation, which they should see very little of in this environment.
What would be more pertinent is changing the charging logic so the packs are held at 50% state of charge vs being always charged up to 100%, that will significantly decrease the chance of pack issues while greatly increasing the longevity of the battery itself. If you hold a lithium ion cell at 50% SOC for years without varying it and keep the temperatures flat, it can last for a very long time without capacity degredation. If you leave it at 100% it will be degrade in a few short years and can swell, at which point it has twice the chemical potential to flame out. Also if it's charged to 100% when the datacenter is at 20'C ambient and datacenter cooling fails and temps go up, having the pack warm up to 40'C can overvolt it and that is usually where they swell/fail.
Also fair to note here that Apple is probably at the frontier in terms of using the highest safety cells and battery management logic so I'd feel better about this than I would putting a lesser brand's lipo pouches in datacenter environment.
> With that kind of airflow and consistent temperature I would suspect ....
A lot of words, many of which might well be true. But it ignores the fundamental point.
I think we can safely assume its not their building, not their datacentre.
As a result, they need to play by the rules of the datacentre operator.
The datacentre operator has fire suppression systems build to a certain spec.
The datacentre has risk assessments and insurance covers to think about.
The datacentre has other customers to think about.
The datacentre has its own staff to think about.
Yes, datacentres have some of the most advanced multi-layer fire detection and suppression systems in the world.
But a fire caused by multiple racks stuffed full of LiPo batteries will likely result in very hard to control results, especially if it becomes a cascading event.
Yes, it is arguably highly unlikely to ever happen, especially with Apple hardware as you say.
However at the very least the guy should fess up and have a chat to the datacentre operator to at least give them a chance to say (preferably in writing) "ok, no problem, we'll just add it to our risk register".
We run lithium ion UPSs in our racks and have for many years - I think you're taking the airline approach here but the reality is the environment inside a datacenter is much more stable than almost everywhere else lithium ion batteries are employed today, and the fire suppression detection and suppression systems add on top of that.
When the MacBook is fully charged and still plugged in, it bypasses the battery and runs directly off power from the wall adapter. So those batteries are hardly doing anything.
I am sorry, this is "Resolved"? How can they even consider marking this resolved in any situation. Yeah we exposed your env vars but we told you about it over email so it's all good... We dont know how or to what extend though.
> As an eternal reminder of the need to do better?
Eternity is a very, very long time. Longer even than 80 years (arguably the total age of the whole "programmable electronic computing and data storage machines" industry), you know?
So I don't think that having an open issue in a bug tracker forever is even possible; not that it would even serve as a remainder — I assure you, most long-existing firms have "ignore open issues older than X years" filter enabled by default in their Jiras or whatever people use nowadays, those are only ever looked at once year by the upper management when they're out of ideas.
Reminds me of Cloudflare going down every time there was a football game in Spain as the ISPs blocked all the "bad" ips, which ironically also served government websites.
It’s still happening every time there is football, at least they now seem to lift the block when the games end, when this started sometimes they took 12 hours after the game ended.
Spain's government is made up of spineless dinosaurs. So the official soccer diffusion corps bought the courts and sued all the ISPs to force them to block all the soccer piracy sites during a match. Those sometimes ended up being hosted on cloudflare's IPs. Thus, a good portion of cloudflare goes down for the spanish clients when there's a game on.
Did that work? Hell no, piracy sites just moved elsewhere. But big soccer is slowly ruining the internet and all the EU governments are letting it happen
One of the things I find most amusing is that Movistar is both one of the main football diffusion corp, and one of main national ISPs. So Movistar sued itself so that it can block the parts of the internet that they don't like
Eventually the soccer corpos will end up tasking an AGI with solving soccer stream piracy and it will hopefully destroy all stadiums and free us from this bullshit.
Started reading the book recently and one thing stood out:
> Blameless postmortems are one aspect of a blameless culture. Creating a safe environment and fostering a culture of learning requires understanding blame and acknowledging cognitive biases. Blame can be a way to discharge discomfort, as Brené Brown suggests. It’s crucial to recognize cognitive biases such as the fundamental attribution error (where we attribute others’ actions to internal traits and our own to external circumstances) and hindsight bias (the tendency to see past events as predictable).
> Blamelessness shifts the focus of responsibility from people to systems and processes after an incident. Finger-pointing leads to risk aversion, fear, and a tendency to hide mistakes, which reduces situational awareness, increases the risk of problems accumulating, and limits the organization’s ability to be proactive—stunting the ability to innovate and improve. A blameless culture instead focuses on identifying and improving the systems and processes that allowed the incident to occur. It assumes that individuals act in good faith and make decisions based on the best information available.
This is probably the most important thing in my opinion in a lot of scenarios and cannot be emphasized further.
How? NASA budget is around 20-30bn in recent years, same scale as US Space Force department budget (26bn in recent years, 40bn in 2026). Comparable, but not minuscule.
The total 2026 US Defense budget is 1.06 Trillion dollars, or ~1,060 Billion dollars. NASA's 2026 budget is 24.5 Billion dollars, or 2% as much as the defense budget.
You chose to single out the Space Force, which has the smallest budget of the 5 branches of the US military. For contrast, the Navy's budget alone is 235 Billion $, close to 10x NASA.
For further comparison, the R&D budget of a single private company, Apple, was $34B in 2025.
It's hard to say specifically that the exact figure of the Space Force budget is the entirety of what the US military spends on "space" annually. Additional large amounts of funds will be committed through programs which are under the umbrella of the NRO or NSA or NGA (aka NGIA) agency budgets.
For one thing, because the parent you were responding to did not make that distinction, and it wasn't clear why you chose to make it. For another thing, limiting US defense space activity spending to just the Space Force budget is naive. All departments of the military operate space activities, and have not and will not hand all of that over to the Space Force (see also: military intelligence vs CIA). We can't know the exact budgetary amounts of each department, and then there's the NRO (National Reconnaissance Office, managing space-based spying), infamous for donating [1] its obsolete telescopes to NASA, which were of comparable performance to Hubble.
Why is the space force budget relevant? The US has had spy satellites decades before the clown made the space force for his family and friends to feast.
We have organizations chartered for land, air, and sea superiority. It seems fairly reasonable to have an organization chartered for space superiority, instead of leaving that adhoc across the other forces.
This. All services have experience doing most things - they do those things to maintain superiority over their domain. And the way they do them is specialized to that domain.
The navy was up there to maintain superiority over water. The airforce over the air. The army likewise.
But nobody clearly owned maintaining superiority over the domain of space and any operation that needed to ensure uncontested operation in space was a joint agency nightmare.
Space force is chartered to provide superiority in space so the other services can conduct their operations up there. Space is clearly a specialization that is differentiated from the air.
I've known Navy people to make the case that the Air Force shouldn't be separate from the Navy. I have no idea if they're right, but I'm sure there are websites arguing the pros and cons out there.
The Space Force has existed for decades before Trump. It was part of the Air Force and is still organized under that Department. They have been slowly increasing its independence as a branch of the military for a long time.
It isn't much different than how the Air Force was eventually carved out of the Army Air Corps.
"Air Force", "Space Force" are maybe well known to the general population, not many people outside of military/government/tech circles even know the NRO or NGIA exists or what the acronym means. The line gets a bit blurry between Air Force money spent, NRO, NSA, in some regards it's just better to think of it as buckets of how things get labeled within the larger DoD.
FWIW, I think you mean NGA instead NGIA. They added a hyphen between “geospatial” and “intelligence” to avoid the eternal embarrassment of a 4-letter acronym.
The mission scope of the various intelligence agencies has evolved a lot over time as capabilities and requirements have changed. Even the histories of how these independent agencies came to exist is pretty interesting.
Former PMC here - at least within the corporate organization I worked for, we consumed ngia product and we called it ngia. We had a totally unrelated thing that had the acronym nga so we used the longer acronym to be clear, I guess I got in the habit of it.
NGIA (Natural Gas Innovation Act? Nursery & Garden Industry Australia? Next Generation Identification and Awareness) had me stumped until I realized it must be a typo:
Although the new title is four words long, the agency will officially use a three-letter acronym. This is by design, according to NGA officials, who feel that the new title more accurately reflects the agency's true mission, which is to provide intelligence and analysis rather than simply reproducing maps and imagery.
There is one NGIA on the Wikipedia page, in the title of a document from 2014:
FWIW, I’ve known some of the OG NGA people a long time and they always referred to it as NGA in my experience. If anyone referred to it as NGIA I never heard it.
NGA is of course its correct name but if you Google:
" "NGIA" intelligence mapping"
It'll turn up a ton of results where people external call it NGIA including a number of .edu sources...
In some ways I guess it's a bit of a stylistic choice, putting a letter for each of the four words of its name, much as how BBC News does not always capitalize all acronyms. Copy and pasting from their style guide:
"acronyms
Use the abbreviated form of a title without explanation only if there is no chance of any misunderstanding (eg UN, Nato, IRA, BBC). Otherwise, spell it out in full at first reference, or introduce a label (eg the public sector union Unite).
Where you would normally pronounce the abbreviation as a string of letters - an initialism - use all capitals with no full stops or spaces (eg FA, UNHCR). However, our style is to use lower case with an initial cap for acronyms where you would normally pronounce the set of letters as a word (eg Maga, Sars, Aids, Nasa, Opec, Apec).
There are a few exceptions:
The National Institute for Health and Care Excellence is capped up ie NICE
Special educational needs and disabilities becomes SEND
The UK Independence Party is capped up ie UKIP
Strategic Health Authority becomes SHA ("Sha" looks like a typo)
Seasonal Affective Disorder becomes SAD ("Sad" would be confusing)
Where a capped-down acronym risks being misunderstood as a word.
For names with initials, we avoid full stops and spaces (ie JK Rowling and TG Jones).
When abbreviating a phrase, rather than a name or title, use lower case (ie lbw, mph)."
> NASA's total enacted budget for fiscal year 1996 was approximately $13.9 billion
> a 1996 bipartisan commission report noted that the NRO possessed "by far the largest budget of any intelligence agency," and contemporary experts track the broader military space budget at roughly $10 billion to $11 billion annually for the NRO alone
So pretty similar budgets. The NRO imaging lens used in Nancy Grace was manufactured in 1999 but planning started in 1996.
Hmm ShinyHunters seems to be in the news quite a bit recently. Most high profile was the Canvas LMS hack last spring right during college finals. Wonder if there will be a ransom for this data as well.
reply