- 1 Post
- 3 Comments
Joined 3 years ago
Cake day: November 18th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
TapedeckNinja@lemmy.worldto
Technology@lemmy.world•Evidence Is Growing That the Massive Tech Outages Are Trump’s Fault: "If we cut the fire department, we shouldn’t act as if we’re surprised when we can’t put out the fires."English
1·5 hours agoI don’t see any reason to think the official explanation isn’t truthful. It makes perfect sense.
TapedeckNinja@lemmy.worldto
Technology@lemmy.world•Evidence Is Growing That the Massive Tech Outages Are Trump’s Fault: "If we cut the fire department, we shouldn’t act as if we’re surprised when we can’t put out the fires."English
1·6 hours agoSMART was being used in DC airspace in September.
They rolled it out nationwide on November 10th (not the 12th as you said): https://www.faa.gov/newsroom/statements/general-statements?hl=en-US
Does not seem likely to be related as SMART mostly reads from the SWIM data feed.

There are a bunch of ways that a proof written in Lean can be invalid.
The most obvious is that the problem statement is invalid or incomplete. This was not really a concern here as the proof used Mathlib’s built-in definitions rather than restating the problem, but nonetheless it has been verified.
Beyond that Lean proofs can contain custom axioms/assumptions, shortcuts, tricks, exploits. And there’s the possibility that the Lean compiler used in the proof had a bug.
Anyway all that has been tested and verified. The problem statement is valid. The proof doesn’t contain any tricks or assumptions. It compiles on every major Lean kernel.
Basically: it is almost certainly mathematically true. The next step is humans actually understanding it.