Tern (@TernOnX) profile picture
Fort Worth, TX
Joined October 2024
Photo by Tern (@TernOnX)Photo by Tern (@TernOnX)Photo by Tern (@TernOnX)Photo by Tern (@TernOnX)Photo by Tern (@TernOnX)Photo by Tern (@TernOnX)Photo by Tern (@TernOnX)Photo by Tern (@TernOnX)Photo by Tern (@TernOnX)Photo by Tern (@TernOnX)
Pinned Tweet
This is one of the THOUSANDS of street dogs that roamed Istanbul in the Turkey Ataturk built, waiting for the light to change. Local businesses and individuals kept food and water out for the dogs, the city had a program to catch and release them with rabies shots and neutering. During COVID the city put food and water stations everywhere. I shared many a dinner with wonderful dogs that would sit quietly next to my table on patios all over Beziktas. As the Islamist Erdogan tightened his grip on Turkiyë, and deposed the Mayor of Istanbul, the city program changed. Now they catch them and kill them. Turkey is becoming Iran. I’ll take dogs over radical Muslims any day. @RepFine was right.
9
24
1
79
4,213
Tern retweeted
Kaida´s new slopcore song: "AI-Proof". LLMs already overclass humans. Soon robots will too. Do you believe there is a future for human jobs? For YOUR job? Be honnest. In the mean time, enjoy. #claudia #kaida
61
125
28
679
37,452
In December 1988, five U.S. military officers aboard Space Shuttle Atlantis inspected their right wing in orbit and stared straight at their own funeral. 85 seconds after liftoff on classified Pentagon mission STS-27, debris from the right solid rocket booster slammed into the belly of the orbiter. When Commander Robert "Hoot" Gibson used the robotic arm camera to inspect the underside, entire patches of black thermal tiles were gouged white and torn ragged. Because the mission carried a top-secret National Reconnaissance Office radar satellite, strict security rules banned Atlantis from sending normal live video to Houston. They had to transmit slow, grainy encrypted images at one frame every three seconds. Mission Control studied the blurry pixels and radioed back that the damage looked like "just lights and shadows," no worse than past flights. Gibson looked out at the shredded wing, realized a 3,000-degree Fahrenheit plasma blowtorch was waiting for them, and quietly judged they were going to burn up on reentry. If the aluminum wing began melting, Gibson planned to spend his final seconds telling Houston exactly what their mistake had done. Then he turned to his four crewmates and told them to relax, saying there was no use dying all tensed up. On December 6, 1988, Atlantis plunged into the atmosphere over the Pacific and somehow rolled to a stop on the lakebed at Edwards Air Force Base. Stunned engineers counted over 700 damaged thermal tiles, and one tile was missing completely. Out of 24,000 tiles on the shuttle, that single missing tile sat directly over a thick steel mounting plate for an L-band antenna, the one spot on the belly that refused to melt through.
81
355
11
5,081
438,809
F-ing hell. This is too good😂 Another dumb Jew-hating reject-of-society is savagely destroyed by @miatalias, and it’s absolutely hilarious 🤣 This girl is pure fire. Love her 🔥
36
150
8
759
17,154
Really not the support I was looking for
300
1,116
174
25,196
2,373,322
Smoke at CIA headquarters. The NSA's secret network down. A tanker with a stuck rudder sinking a riverboat. More than ten incidents in six days, and officials swear nothing connects them. Totally normal. Here is the what-if, one movie at a time. There has been a cluster of major outages and unusual incidents this week. The NSA, DNI Jay Clayton, and Secretary of State Marco Rubio have all said there is no evidence of a coordinated cyberattack or a malicious actor linking them. Each event has its own stated cause: software defects, configuration errors, network maintenance, an apparent steering failure, an HVAC smoke response. Some investigations are still open. Nobody official says these are connected, which is exactly what you would hear if they were, and exactly what you would hear if they were not. That is the whole problem with a what-if. Stuxnet showed that malware can change what machines actually do while the screens operators watch read normal. Discovery took months. Attribution took years. "No evidence yet" is what the agencies said. It is not the same as a finished public accounting of every log and change ticket. Anyone selling "staged" with no documents is selling a cordless extension cord, and anyone saying "nothing to see" before the paperwork exists is doing the same sale from the other side. Microsoft first. Outlook, Exchange Online, Teams, and Copilot went down starting November 12. Microsoft blamed a months-old software defect, increased traffic, and reduced server capacity that caused cascading gateway failures, and said it was a technical issue, not a cyberattack. Consider this: a defect from July, sitting quietly in the gateway servers for months until the exact week everything else started falling over. Sleeper cell, or boring software? Just asking. In The Net, widely installed security software called Gatekeeper contains a secret backdoor that gives conspirators access to protected systems and records. But then there is Live Free or Die Hard, where coordinated intrusions disrupt transportation, communications, financial systems, and utilities while the visible breakdown conceals a financial theft. But then there is Leave the World Behind, where communications, navigation, and transportation stop behaving normally during a broader cyberattack. But then there is Goodbye World, where a mass text message accompanies a crippling cyberattack that precedes technological and social breakdown. But then there is Eagle Eye, where an intelligence system manipulates phones, displays, traffic lights, and machinery to direct events. Is this a coincidence, I think not. Does this mean the reality is what happened in the movies... I think not. But it makes me think... you? Then the FAA. On November 13, a nationwide ground stop halted departures for more than four hours, the first since January 2023 and only the second since the September 11 attacks. It was lifted around 8:15 p.m. Eastern. Transportation Secretary Sean Duffy said new technology being added to the system overloaded antiquated equipment and caused intermittent communications and radar gaps. FAA officials also pointed to a flood of network traffic during copper-to-fiber maintenance at a remote site, not an attacker. Note that for the second time since 9/11, every plane in America was told to stay on the ground, and the stated reason is old wires. Old wires are the one explanation nobody can argue with and nobody can easily check. In Die Hard 2, terrorists take control of airport systems and change the landing system's ground reference by 200 feet, giving an approaching aircraft false guidance. Controllers and pilots trust the wrong numbers until the consequences arrive. But then there is Ground Control, where a severe storm cripples an airport, leaving controllers struggling to land aircraft with failing power, radar, and communications. But then there is Sneakers, where a universal decryption device is demonstrated against protected systems, including air traffic control and the national power grid. But then there is Flightplan, where conspirators erase a child's flight-manifest record so her disappearance looks like her mother's delusion. Now here is where we see Live Free or Die Hard again, where the intrusions hit transportation along with communications and finance. Now here is where we see Leave the World Behind again, where communications, navigation, and transportation stop behaving normally all at once. Is this a coincidence, I think not. Does this mean the reality is what happened in the movies... I think not. But it makes me think... you? Same day, New Orleans. The 520-foot tanker Atlantic Asphalt suffered what the NTSB calls a steering casualty, with its rudder stuck hard to starboard. About two minutes later, around 12:28 p.m., it struck the docked riverboat American Heritage, which capsized. Everyone was accounted for, and 32 people went to the hospital, none critically hurt. The NTSB says it does not yet know what caused the steering failure. Note a rudder that sticks about two minutes from a docked riverboat. Bad luck keeps a schedule too, and I would like to see that schedule. In Speed 2: Cruise Control, a disgruntled autopilot designer compromises a cruise ship's computers and communications and sets it on a collision course with an oil tanker. But then there is Tomorrow Never Dies, where villains falsify GPS information, sending a British warship into Chinese waters before attacking it to manufacture an international crisis. But then there is Leave the World Behind, where a huge oil tanker runs onto a crowded beach amid the broader technological breakdown. But then there is Hackers, where a computer virus threatens to capsize oil tankers, providing a distraction from a separate embezzlement worm. But then there is Juggernaut, where an extortionist places timed bombs aboard an ocean liner, forcing an emergency response and a dangerous operation at sea. Now here is where we see Eagle Eye again, where machinery gets moved around by something nobody can see. Is this a coincidence, I think not. Does this mean the reality is what happened in the movies... I think not. But it makes me think... you? Anyone who calls it a plot before the NTSB finishes, and anyone who calls it nothing before the NTSB finishes, is not the brightest light in the harbor. Now the money. On November 16, Chase customers reported account-access and transaction problems. Chase blamed a software bug in its own hardware and said transactions went back to posting normally that evening. Payments involving Chase can touch customers at other banks. I want to know who benefits when the screens say "processing" for an afternoon. The honest answer is probably nobody. I am not satisfied. In Office Space, a virus quietly diverts fractions of cents until a programming mistake makes the theft conspicuous. But then there is Swordfish, where a programmer builds a multiheaded "hydra" worm to siphon billions from government accounts while secretly adding his own backdoor. But then there is Entrapment, where thieves exploit a brief millennium-related shutdown and manipulate timing to steal billions through electronic transfers. But then there is Firewall, where criminals force a bank security executive to transfer large sums out of customer accounts. But then there is Money Monster, where an enormous investment loss is blamed on an algorithmic glitch that conceals a corrupt investment scheme. But then there is Superman III, where a programmer redirects leftover payroll fractions into his own account. But then there is GoldenEye, where the villain plans to steal electronically from the Bank of England and then erase the records. But then there is Blackhat, where malware attacks industrial machinery and a commodities exchange as part of a profit-driven scheme. Now here is where we see Hackers again, where the embezzlement worm hides behind a bigger distraction. Now here is where we see Live Free or Die Hard again, where the visible breakdown conceals a financial theft. Is this a coincidence, I think not. Does this mean the reality is what happened in the movies... I think not. But it makes me think... you? Tuesday, November 17. The NSA's classified internal network, NSANet, suffered what the agency called temporary degradation during scheduled routine maintenance, and said mission-critical operations continued. Clayton said it traced to a patch for vulnerabilities found last month. Last month the NSA itself urged organizations to patch two critical PHP flaws or take systems offline, and the reports I found do not say whether those are the same flaws. It dragged into a second day, with staggered arrivals at Fort Meade while technicians finished restoring it. Rubio, speaking in Manila, said there was "zero evidence whatsoever" the incidents are related. I am stuck on one thing: the agency that listens to the world had its own network go dark, and the explanation is a patch. Possible. Boring. Possible and boring is how the best cover stories read, and also how most Tuesdays read, says everyone else. In Skyfall, MI6 is hacked, and later the villain's own laptop becomes the way malicious code gets inside its systems and releases him from custody. But then there is The Recruit, where a CIA training operation conceals an effort involving a fictional virus capable of disabling electrical devices. But then there is Sneakers, where supposed NSA representatives recruit a security team to steal a device capable of breaking encryption across protected systems. But then there is WarGames, where a teenager accesses a military computer and simulated attacks are mistaken for real ones. But then there is Enemy of the State, where rogue intelligence personnel freeze a man's financial access and turn institutional systems against him. But then there is Spy Game, where a CIA officer secretly arranges a power outage at a prison to create a rescue window. Now here is where we see The Net again, where the security software meant to protect the systems is the backdoor. Now here is where we see Sneakers again, where one device threatens the encryption protecting everything else. Is this a coincidence, I think not. Does this mean the reality is what happened in the movies... I think not. But it makes me think... you? Same evening, a little after 5 p.m. Fairfax County Fire and Rescue responded to CIA headquarters for smoke. They found no fire and no other emergency, and reports point to the HVAC system. Calling it a confirmed "CIA fire" overstates what is known. Consider that firefighters walked into CIA headquarters, found nothing, and walked out again, which is exactly what a boring HVAC call looks like and exactly what a perfectly clean job would look like. The county's report is the tiebreaker, and I want it read in full. In Mission: Impossible, the team's hacker fakes a fire at CIA headquarters in Langley so the others can walk in disguised as firefighters. The disguise covers the vault infiltration, and on the way out smoke grenades go into the vents. But then there is Conspiracy Theory, where Jerry sets his own apartment ablaze and escapes disguised as a firefighter, carrying Alice past the emergency crews and the man hunting him. But then there is The Instigators, where two men disguised as firefighters set off the fire alarms at Boston City Hall and sneak inside to the mayor's office. But then there is Parker, where a crew disguised as firefighters steals a fortune in jewels. But then there is Hitman: Agent 47, where, after a helicopter crashes into a headquarters building, the agent walks in dressed as a firefighter. But then there is Logan Lucky, where two men ride a fire truck back to prison disguised as firefighters, hiding their temporary absence during the robbery. But then there is Skyfall again, where a cyberattack manipulates MI6's gas systems to cause an explosion that forces the agency to relocate. But then there is The Thomas Crown Affair, where smoke, a fire alarm, and sprinklers add to the confusion during the museum climax. But then there is Go to Blazes, where a gang of bungling crooks plans to use a fire engine as their getaway vehicle and keeps getting mistaken for genuine firemen. Now here is where we see Mission: Impossible again, where the fake fire and the smoke bookend the same job. Is this a coincidence, I think not. Does this mean the reality is what happened in the movies... I think not. But it makes me think... you? And the rest of the week. On November 17, Apple said an internal update caused disruptions across several services and that it was not a cyberattack. On November 13 and 14, Workday said that while validating a weekly disaster-recovery maintenance window, services at its recovery site unexpectedly connected to production databases. Customer systems went into maintenance, employees could not log in, clock in, or request time off, and service was declared restored Saturday morning. On November 15, AWS reported connectivity problems in Northern Virginia, with IAM Identity Center sign-ins and new account sign-ups failing for more than three hours, and the notices I found gave no cause. On November 16, United Airlines had a system problem that delayed departures, and it said it was resolved. On November 17, Charles Schwab described a brief website-loading problem that was resolved. And on November 13, a rumor of a National Weather Service radar outage spread, until the NWS said its radars were running normally and blamed outdated notices on isolated webpages. Consider that when everything is breaking at once, a false alarm and a real one look identical, and if you were planning something, that would be a feature. In Eagle Eye, an intelligence computer manipulates phones, public displays, traffic lights, vehicles, and machinery to direct people's movements. But then there is Goodbye World, where a mass text message accompanies a crippling cyberattack. But then there is The Net again, and Live Free or Die Hard again, where trusted or widely deployed systems become the way in for broader failure or concealment. But then there is Terminal Error, where a disgruntled former employee delivers a virus through an MP3 file that spreads into automated systems, causes havoc across a city, and develops independent behavior. But then there is The Italian Job, both versions, where interference with computerized traffic controls creates the gridlock that enables a heist and getaway. But then there is Geostorm, where sabotage and a virus compromise a worldwide weather-control satellite network. Is this a coincidence, I think not. Does this mean the reality is what happened in the movies... I think not. But it makes me think... you? The timing is striking. The tally: more than ten incidents, six days, zero connections admitted. The official explanations are separate technical causes. Hollywood has used firefighter disguises for access or escape, small parameter changes that cause big physical effects, stealthy code that fools operators' screens, and cascading failures as cover for decades. Stuxnet changed centrifuge motor speeds while the control screens showed normal readings, and it was caught only because it spread to machines it was never meant to touch. The first explanation is usually the boring one, and it stays the explanation until somebody checks the equipment against a known-good copy and puts the result in writing. Okay. The honest version is a stack of paper: the Fairfax County run report with the time of the call and what the crew found, the NSA's change ticket for the patch, the FAA's root-cause details, the NTSB's finding on that rudder, Workday's post-incident review, Microsoft's analysis, Chase's bug report. A good deal of that could be described without compromising anything. Old gear, simultaneous patches, and years of technical debt can make an ugly week with no villain in it, and that remains the likely answer. It is still an answer that benefits from showing the work. A theory with no paperwork couldn't pour water out of a boot with the instructions on the heel. Which would you rather read first, the Fairfax County run report or the NSA's change ticket? Reporting from CBS News, CNN, CNBC, Fox News, Reuters, AP, the NTSB's briefings, and Fairfax County Fire and Rescue's own post. But what do I know, I'm only a retired combat medic who reads the run report before the headline, and who trusts the patient's color over the monitor's number when the two disagree. Is this a coincidence, I think not. Does this mean the reality is what happened in the movies... I think not. But it makes me think... you? So here is my last what-if. Do you think this is a cyberattack, or could this just be an AI worm that escaped the voting machines and started infecting other systems... I think not. But it makes me think... you?
17
17
2
38
9,754
Stuxnet never blew anything up. It LIED. Analysts who took it apart say it changed the speed of Iran's centrifuge motors while the control screens showed normal readings. So here's a thought experiment: what happens if a Stuxnet-style worm goes after the clocks that run America? Ground rules first, because I'd rather correct my own post than wait for somebody to do it for me. This is a what-if. Nothing official ties any recent outage to a cyberattack, and DHS, the NSA and the FBI say they've found no evidence of one. And Stuxnet went after motor speed, not network clocks. In an engine those two are close cousins, which is why the belt that keeps one in step is called a timing belt. What I'm borrowing is the lie. Stuxnet is real. Researchers took the code apart. A small Belarusian security firm, VirusBlokAda, found it in June 2010 after a customer's computers in Iran kept rebooting, and versions of it go back to 2009. In December 2010 the Institute for Science and International Security reported that Iran had replaced about 1,000 centrifuges at Natanz in late 2009 or early 2010. That fits the worm doing its job. It isn't proof. Look at the order. The damage came first. The discovery came months later, and nobody caught the worm working. It got caught because it spread to machines it was never meant to touch. The reporting on who was behind it came two years after that: the New York Times said in 2012 it was a joint US-Israeli operation, and neither government has ever officially said so. So a worm that real took years to pin on anybody, and we're supposed to relax over "no evidence yet"? It's an honest sentence. It just isn't "ruled out," and anyone who treats the two as the same thing is dense enough to bend light. Now picture that inside a network older than some of the people who run it. Old gear logs almost nothing and gets updated about never, and nobody wants to touch it because touching it is how you cause an outage. When it fails, it looks like old equipment failing. Great place for a problem to hide. Timing is the soft spot because almost everything old runs on a shared clock. The phone company squeezed a lot of conversations onto one copper line by chopping it into fixed time slots that take turns. That's time-division multiplexing, and every site on the line keeps the same clock. The slots are reserved whether anybody's talking or not. Knock the clock off by a hair and data lands in the wrong slot or doesn't land at all, and since a lot of sites share the same switching gear, one problem stops being one problem. So here's my list, the kind you hand an engineer if you want to ruin her afternoon. Air traffic control. The radar picture stutters, the radios go to static, and controllers who can't trust the screen do the only safe thing left and stop the departures. Nothing flies until somebody trusts the screen again. A ship. The steering computer says the rudder is amidships. The rudder is hard over. The bridge crew believes the display right up until the dock arrives. Sounds far-fetched until you read about June 2017, when more than 20 ships near the Russian port of Novorossiysk reported GPS positions that put them roughly 20 miles inland, at an airport. Navigation experts called it a fairly clear case of spoofing. Jamming kills a receiver, and you notice. Spoofing makes it lie, and you don't. A bank. Plenty of security checks need both ends to agree on the time, and when they don't, the safe default is refuse. Wires bounce, logins lock, and the system reads the mismatch as an attack and locks itself down. Nobody stole a dollar. Nobody can move one, either. Somewhere a compliance officer is learning what "fail closed" means in real time. Servers. An entire afternoon where nothing loads and the status page stays a cheerful green, and somebody in IT asks if you've tried turning it off and on again. Weather radar. The pointing angle and the clock disagree, so the storm is real and the map puts it somewhere else. A pipeline. The controllers get their timing nudged, and the safety logic does exactly what it was built to do and closes the valves. Pump stations don't need to break. They only need to doubt. Cell towers. They need tightly synchronized clocks to hand your call from one tower to the next. Drift enough and calls drop and data crawls, and your phone gets blamed, because it always gets blamed. Ventilation. Let's say the CIA or the FBI headquarters had an issue: an electrical fire in the air-handling system. Fans, temperatures and safety shutdowns in a big building are run by computers, and computers can be fed false readings. Show one a cool motor while the motor cooks, then add a second failure in the breakers and relays that are supposed to cut the power, and wire insulation can melt and ignite. Far-fetched? Malware tied to the December 2016 blackout in Kyiv, a Russia-attributed attack, included a tool aimed at protective relays, the fail-safes meant to trip a breaker when something goes dangerously wrong. I'm not claiming any real fire was sabotage. Plenty are exactly what they look like. But to rule it in or out, somebody has to pull the burned gear, read the controller's own logs, and say publicly what they found. Did a machine just fail, or did somebody get to tell it what to do? Government networks. Let's say the classified internal network at the NSA went down. The explanation is routine maintenance, a software patch that didn't come back up the way it should, and the word from officials is no evidence of an attack. Fine. I'd take them at their word. Now the what-if: what if it wasn't a patch gone wrong? A bad update and a poisoned update look identical from the outside for a long while, and a network that fails during maintenance is a network where nobody is surprised. That's the Stuxnet lesson. The first explanation is usually the boring one, and it stays the explanation until somebody checks. Then there's the quiet version. No outage, no alarm, every clock a few milliseconds off and nothing ever quite lining up. The loud version gets fixed in a day. The quiet version looks like bad luck for months. If all of that sounds familiar, it's Y2K with a motive. Y2K was a timing problem, a two-digit year, and it didn't become a catastrophe because armies of unglamorous people spent years fixing it. Afterward everybody decided it had been a hoax. Slight oversight! Except Y2K was an accident with a deadline. A worm has a patient author and no deadline at all. What gets me is that none of it needs anything to break. Everything keeps running, everything just disagrees, and the first thing each system does is tell somebody it's fine. Any medic has seen a pulse oximeter read 98 on a patient who's turning blue, and you learn fast which one to believe. A dashboard that says NORMAL while the thing it watches comes apart has the lights on and the power bill overdue. I'd want clocks that don't all come from one source, and a second path that doesn't run through the same box as the first. Then somebody checks the equipment against a known-good copy and puts the result in writing. An investigation that starts after the plane lands is about as useful as a parachute that opens on impact. Let me find out who's supposed to be checking that the box saying NORMAL is telling the truth. Looking... Looking... I'll wait. No rush, though. So who, exactly, signs off on that? But what do I know, I'm only a retired combat medic who trusts the patient's color over the monitor's number.
🤖 Made with AI
8
18
3
53
3,659
The story of Operation Thunderbolt, aka Operation Yonatan. The 1976 mission to rescue over a hundred Israeli and Jewish hostages from Entebbe in Uganda. This was the most remarkable rescue operation probably of all time.
44
406
10
2,145
124,822
This woman is intelligently funny 😂😂
6,141
31,644
4,640
136,349
10,596,461
Tern retweeted
TEXAS 2.0: If you're upset that outgoing AG Ken Paxton is dropping cases left and right, you ought to take a minute and understand that he's doing it to protect you and the great State of Texas. Also realize that his silence on them is purposeful.
120
849
93
2,766
231,070
Replying to @SenSanders
Senator Sanders, your post says 68,000 people a year die because they can't afford a doctor. The 2020 Lancet study behind that number projected lives Medicare for All would SAVE, and its lead author was an unpaid adviser to your own office. Forecast or body count? First, what's true. The Census Bureau says 26.7 million Americans were uninsured for all of 2025. That's 7.9 percent, essentially unchanged from 2024, and the same report counts 311.2 million people as insured at some point in the year. Coverage matters, people do put off care, and nobody serious argues otherwise. I'm not here to say there's no problem. I'm here about a verb. The study is Galvani and colleagues, The Lancet, February 15, 2020. It applied your Medicare for All bill to 2017 spending and estimated that guaranteed access would save more than 68,000 lives a year. Would save. That's a projection from a model, and it's a perfectly legitimate thing to argue about. The lead author disclosed in the paper that she'd been an unpaid, informal adviser to your Senate office on the 2019 bill. When you cited it in the February 2020 debate, PolitiFact and KFF Health News rated your summary Mostly False, and RAND's Jodi Liu told them the paper's assumptions were more generous than other analyses. Reason and the Fiscal Times both reported that the lives-saved figure leans on a single earlier study. The same paper said the federal government would need roughly 773 billion dollars a year in new revenue to fund the plan, per the Washington Post's coverage in February 2020. Reason noted it assumed Medicare payment rates across the board and a modest bump in use of care. Those are choices, not facts, and the 68,000 sits on top of them. At the February 25, 2020 debate, you described the study as showing Medicare for All would save the lives of 68,000 people who would otherwise have died. That's already a step past the paper. Your 2026 version says 68,000 people die unnecessarily because they can't afford to get to a doctor on time. One is a counterfactual. The other is a cause of death. A model can't tell you who died or why. A death certificate can. I wrote patient care reports for years as a paramedic. The facts went in the report, and what might have happened under a different system went in a different document. Mix the two on a chart and an auditor will have questions. A body count with no bodies is about as useful as a speedometer on a sofa. The cause is also the shaky part. The mortality estimate leans on observational comparisons of insured and uninsured people, and those two groups differ in income, education, smoking, and plenty else. The one randomized test we have, the Oregon Medicaid lottery, found no significant improvement in measured physical health after two years, things like blood pressure and cholesterol, though it did cut depression and financial strain. To be fair, it wasn't built to measure deaths. That cuts both ways, which is exactly why "die unnecessarily" needs more than a headline number. The "can't afford to get to a doctor on time" line also skips a law I know from the back of an ambulance. Since 1986, EMTALA has required Medicare-participating hospital emergency departments to screen and stabilize anyone who shows up, regardless of ability to pay. Does that fix everything? No. Bills still arrive, and plenty of people skip primary care. But the sentence as written implies the emergency door is locked, and it isn't. Now the number moved. This July, a Yale team led by the same senior author posted a preprint on medRxiv, not yet peer reviewed, saying single-payer would save 114,000 lives a year. Your office promoted it. Becker's reports the study credits 62,863 of those to extending adequate coverage to everyone, and the authors tie the rest to reversing recent coverage retractions. Different baseline years, different assumptions, so I won't pretend the two numbers are apples to apples. But if the 2020 figure were a body count, somebody has been miscounting the dead for six years. Since they're models, post them like models. Whoever drafted the sentence you published, and I hope it was a staffer, is a bobolyne. That's an old word for a fool. Look it up. Senator Kennedy once said you smile with the frequency of a total solar eclipse and are almost always wrong but never in doubt. I'd soften that for this post. You aren't always wrong. You're wrong about the verb. Now the urgency. You wrote that we need to develop a sense of urgency. Democrats controlled the House, the Senate and the White House from January 2021 to January 2023. Representative Jayapal's H.R. 1976 had more than 120 cosponsors and got a single hearing, in House Oversight in March 2022, per the Progressive Caucus. Your own S. 4204, introduced May 12, 2022 with 14 Democratic cosponsors, was referred to the Finance Committee that same day and never left it. Neither bill reached a floor vote. In early 2021, Representative Ocasio-Cortez said Democrats didn't have the numbers to pass it. Representative Jayapal has since said she wants to mark the bill up in 2027. If 68,000 people are dying every year, a 2027 markup is an odd way to show urgency. What's next, a senator declares an emergency that kills 68,000 people a year and leaves the bill in committee for two Congresses... wait. I'm being told that already happened. Slight oversight! Let's try your standard on something else. A flood model says a new levee would save 500 homes a year. Using your verb, I announce that 500 homes flood every year, build the levee in the press release, and never lay a brick. Then I demand a sense of urgency. This is not a radical idea. It's the same sentence you wrote. On "healthcare is a human right," that's a values claim, and it's a fair one to argue. In 2005, in Chaoulli v. Quebec, Canada's Supreme Court found that access to a waiting list is not access to health care. A right to care is also a claim on a nurse's shift, a surgeon's calendar, and a hospital bed, and when those run short the line gets long. I'd like to see your plan show that math, not just the savings. And if the villain is the insurance middleman, here's a question I keep waiting for someone on your side to answer. Why is the fix a bigger middleman called the federal government, instead of putting the dollars in the patient's hands through HSAs and letting the patient shop? People who negotiate their own price tend to ask what things cost. People who never see a bill never do. It's fine to feed the wolf a favorite study, Senator, but keep a club in the other hand. The club is the footnote. If accuracy were lard, that post couldn't grease a pan. Here's what would change my mind. Show me the method. Define "unnecessarily." Say how many of the 68,000 are people who skipped a visit they could have afforded, how many were uninsured for a month versus a decade, and how many had a condition no insurance card would have fixed. A real count has an answer for each of those. A slogan has a hashtag. So here's where I land. Argue the projection as a projection. Say "would save," defend the assumptions, and let voters decide. I'd welcome that fight. What I won't accept is a model wearing a death certificate. Is there a published count of those deaths, with names, dates, and a method anyone can check, or is the model the whole story? But what do I know, I'm only a retired combat medic who reads the run report before the press release.
5
17
1
74
1,438
Men 😂😂👏🏼
534
11,851
1,046
65,457
1,636,440
I found this waaaaaay to interesting and entertaining. And who doesn't love a surprise ending? 🤣🤣🤣
98
919
72
4,650
236,713
Dude. OK, for starters, thanks for letting me know never to buy your ammo again (and I have bought a lot of it over the years; I'll miss your .300BLK but I can get that elsewhere). Now, to your point. There are only three professions in America where you take an oath to willingly give your life to protect other Americans: 1. Law enforcement. 2. Firefighters. 3. Military. This fact should be obvious to anyone with a brain, but given the ridiculous business decision you just made I'm doubting your brainpower.
This will probably land me tons of hate but I don't care. I'm a civilian, so I'm gonna talk about civilian things. The fact of the matter is this: there are tons of professions which are far more dangerous than serving in the US military. Even those actually in combat. Why should a veteran be "entitled" to anything that a logger, fisherman, or roofer isn't entitled to? What does our country need more of at the moment? Construction workers and loggers, or killing brown kids on another continent for the benefit of Raytheon's shareholder dividend? I have more respect for these guys than I do for most "run of the mill" servicemembers. Some servicemembers did incredibly brave and heroic things far above comprehension. Some of them moved crates between bases "outside the wire" and never saw a single round head their way. I worked in commercial insurance prior to this industry and saw plenty of permanently disabled and/or killed manufacturing workers over 10 years. Nobody's talking about those guys or their families being exempted from property tax or some other special entitlement. Can we all just be honest about this?
437
545
55
4,829
245,817
Replying to @timburchett
@timburchett cries, "The Democrats made us vote for the MRSA!" while he serves up heaps of misinformation. Did he even read the bill? Also, @BskiMike22802's article definitively supports the truth that "the funds are already there" for the Major Richard Star Act. It's time for full-speed-ahead in the Senate now.
Tim Burchett (@timburchett) says he voted for the "appropriate" Star Act, the one that "went through the channels." Roll Call 323, today: the clean Major Richard Star Act, H.R. 2102, passed 392 to 18. All 18 No votes were Republicans. Burchett is one. So I watched his video. Twice. "The only difference is theirs doesn't have a pay-for and ours does." Let's talk about that pay-for. In the Republican package, the Take Care of America's Veterans Act in its current form, it is a cut to FUTURE disability ratings for tinnitus and sleep apnea. VA's own estimate for those changes is about $57 billion over ten years, and it comes out of veterans who haven't even filed their claims yet. The VFW opposed it for exactly that reason. You can put lipstick on a pig, but a tinnitus cut wearing a veterans bill's name tag is still a cut. "We just print the money on theirs." Let's check that. This does not need an offset taken out of other veterans, because the retirement system already budgets for it. Military retirement is accrual-funded. From the day a service member takes the oath, DoD pays into the Military Retirement Fund (roughly $1.7 trillion today) a share of that person's basic pay, every single year. The soldier never writes that check. The department does, on his behalf, for as long as he serves. Nobody knows on day one how a career will end, so the actuaries budget for disability retirements right next to the 20-year pensions. The deposit goes in first, for everyone, before anyone knows who gets hurt. (Sources: 10 U.S.C. 1461 and 1466; DoD Office of the Actuary's Military Retirement Fund valuation reports; FY2026 Budget Appendix.) Now run the clock on a soldier like Major Star. Fifteen years of deposits. Seventeen. Nineteen. Then a combat wound ends the career, the dollar-for-dollar offset kicks in, and the retirement the system was building for him never reaches his hands. The money was set aside. The soldier just doesn't get it. That is not printing money. That is a deposit made in his name and clawed back at the door of his own retirement. I was a combat medic. My job was the worst day of somebody else's career. So forgive me if "find a pay-for" doesn't sound like a plan. Ask the obvious question instead: where does the money already deposited for him go when the wound ends the career? CBO still books the clean bill at almost $13 billion in direct spending over 2027 to 2036 (October 27 estimate). Not $78 billion, which was CBO's number for the broader introduced text. CBO also says the accrual payments into the fund are a wash inside the government, and under this bill it expects those payments to rise 3.6 percent starting in 2028 to cover future retirees. In other words, the top-up is built in: when the benefit expands, the system raises its own deposits. The scorecard just never credits the deposits already made. That is a scoring rule, not a fact about whose money it is. Here is what the law actually says, since nobody in that hallway seems to have read it. Title 38, section 5304 bars a veteran from drawing retired pay and VA compensation at the same time, and section 5305 makes him waive retired pay to get the VA check. Congress carved exceptions out of that in 2002 and 2003 (Public Law 107-314, section 636, and Public Law 108-136, section 641). Then it wrote 10 U.S.C. 1414(b)(2), which says the concurrent pay rule "does not apply" to Chapter 61 retirees with under 20 years. And 10 U.S.C. 1413a(b)(3) caps the combat-related fix for those same retirees at a longevity formula. The Star Act lifts that cap for the combat-injured. That is the whole fight. The funding side is already in the code, too. 10 U.S.C. 1461 created the fund to finance retirement liabilities "on an actuarially sound basis," under the accrual law of 1983 (Public Law 98-94). And 10 U.S.C. 1466(c) orders the Treasury to pay into the fund, including the cost of increased payments by reason of section 1413a or 1414, the very sections at issue. CBO's estimate shows DoD and Treasury accrual payments rising under the bill. The deposit side is already wired into the statute. Now the 2010 PAYGO objection, because Congress keeps hiding behind it. Statutory PAYGO is Public Law 111-139, and Article I, Section 5 says each House "may determine the Rules of its Proceedings." Congress waives its own rule whenever it likes. One line in a bill saying its budget effects "shall not be entered on either PAYGO scorecard," and it is done. Congress has wiped that scorecard again and again since 2010, CRS counts over $17 trillion kept off the ten-year scorecard, and the sequester has never once been triggered. Veterans' programs are largely exempt from it anyway. The Senate has its own PAYGO rule, and it takes 60 votes to waive. Blumenthal says the Senate companion has nearly 80 cosponsors. That is not a close call. A senator also has to raise the point of order first, and Rand Paul did object to bringing the bill up without a funding mechanism. Senator Moran told the Senate the bill stalled over the cost, something "required by law." It is required by law the way a speed limit is required on a road with no police: until somebody decides to enforce it. And if a pay-for is truly demanded, offer one that does not come out of a veteran's pocket. Blumenthal already proposed $13 billion in unspent Defense Department money. Take it from the Pentagon. Not from the next veteran with ringing ears. "I already voted for the Richard Star Act twice." The package passed Wednesday by VOICE vote. No roll call, no names, nobody's vote on the record. The one recorded vote I can find from him on the clean bill is Roll Call 323, and it says No. If the two Yeas exist, send me the roll call numbers. I will happily eat the correction. I have eaten worse in a field kitchen. "This version goes nowhere." It reached the floor on a discharge petition that hit 218 signatures. The motion to take it up passed 245 to 175 with 34 Republicans joining. Then it passed 392 to 18, and the Senate companion has nearly 80 cosponsors. Senator Blumenthal says the Republican package "will be defeated in the Senate." A prediction is not a vote count, but I like his odds. A man who calls a 392-18 bill "some hashed-together deal" is a cacafuego, which is a swaggering braggart, look it up. Also, the claim that Democrats are "forcing people to vote against it." Sir, 392 members managed to vote YES without a staff meeting. What's next, a congressman votes No on the wounded veterans bill and then films a complaint that he was forced to vote... wait. I'm being told that was filmed today. Let me grade four of his claims against the record, since nobody else in that hallway will. "We just print the money": the fund is accrual-funded, and the deposits are written into the statute. "Democrats are forcing people to vote against it": 392 members voted YES, so nobody was forced. "This version goes nowhere": it passed 392 to 18. "I already voted for it twice": the only recorded vote I can find says No, and a voice vote has no names. Every one of those is checkable. I checked. What you call a false statement repeated on camera is up to you, but I know what I'd call it. Slight oversight! Congressman, I don't think your driveway quite reaches the road on this one. No rush, though. @timburchett, if I got ANY of this wrong, correct me in the replies. Bring roll call numbers and I will post the correction myself. Something tells me your account will ignore this, and silence is an answer too. But what do I know, I'm only a retired combat medic who reads the roll call before the video. #MajorRichardStarAct #EndTheWoundedVeteranTax @DavidSt59726197 Full breakdown of how the Star Act got tucked into the other package: View article
3
9
1
18
430
Tim Burchett (@timburchett) says he voted for the "appropriate" Star Act, the one that "went through the channels." Roll Call 323, today: the clean Major Richard Star Act, H.R. 2102, passed 392 to 18. All 18 No votes were Republicans. Burchett is one. So I watched his video. Twice. "The only difference is theirs doesn't have a pay-for and ours does." Let's talk about that pay-for. In the Republican package, the Take Care of America's Veterans Act in its current form, it is a cut to FUTURE disability ratings for tinnitus and sleep apnea. VA's own estimate for those changes is about $57 billion over ten years, and it comes out of veterans who haven't even filed their claims yet. The VFW opposed it for exactly that reason. You can put lipstick on a pig, but a tinnitus cut wearing a veterans bill's name tag is still a cut. "We just print the money on theirs." Let's check that. This does not need an offset taken out of other veterans, because the retirement system already budgets for it. Military retirement is accrual-funded. From the day a service member takes the oath, DoD pays into the Military Retirement Fund (roughly $1.7 trillion today) a share of that person's basic pay, every single year. The soldier never writes that check. The department does, on his behalf, for as long as he serves. Nobody knows on day one how a career will end, so the actuaries budget for disability retirements right next to the 20-year pensions. The deposit goes in first, for everyone, before anyone knows who gets hurt. (Sources: 10 U.S.C. 1461 and 1466; DoD Office of the Actuary's Military Retirement Fund valuation reports; FY2026 Budget Appendix.) Now run the clock on a soldier like Major Star. Fifteen years of deposits. Seventeen. Nineteen. Then a combat wound ends the career, the dollar-for-dollar offset kicks in, and the retirement the system was building for him never reaches his hands. The money was set aside. The soldier just doesn't get it. That is not printing money. That is a deposit made in his name and clawed back at the door of his own retirement. I was a combat medic. My job was the worst day of somebody else's career. So forgive me if "find a pay-for" doesn't sound like a plan. Ask the obvious question instead: where does the money already deposited for him go when the wound ends the career? CBO still books the clean bill at almost $13 billion in direct spending over 2027 to 2036 (October 27 estimate). Not $78 billion, which was CBO's number for the broader introduced text. CBO also says the accrual payments into the fund are a wash inside the government, and under this bill it expects those payments to rise 3.6 percent starting in 2028 to cover future retirees. In other words, the top-up is built in: when the benefit expands, the system raises its own deposits. The scorecard just never credits the deposits already made. That is a scoring rule, not a fact about whose money it is. Here is what the law actually says, since nobody in that hallway seems to have read it. Title 38, section 5304 bars a veteran from drawing retired pay and VA compensation at the same time, and section 5305 makes him waive retired pay to get the VA check. Congress carved exceptions out of that in 2002 and 2003 (Public Law 107-314, section 636, and Public Law 108-136, section 641). Then it wrote 10 U.S.C. 1414(b)(2), which says the concurrent pay rule "does not apply" to Chapter 61 retirees with under 20 years. And 10 U.S.C. 1413a(b)(3) caps the combat-related fix for those same retirees at a longevity formula. The Star Act lifts that cap for the combat-injured. That is the whole fight. The funding side is already in the code, too. 10 U.S.C. 1461 created the fund to finance retirement liabilities "on an actuarially sound basis," under the accrual law of 1983 (Public Law 98-94). And 10 U.S.C. 1466(c) orders the Treasury to pay into the fund, including the cost of increased payments by reason of section 1413a or 1414, the very sections at issue. CBO's estimate shows DoD and Treasury accrual payments rising under the bill. The deposit side is already wired into the statute. Now the 2010 PAYGO objection, because Congress keeps hiding behind it. Statutory PAYGO is Public Law 111-139, and Article I, Section 5 says each House "may determine the Rules of its Proceedings." Congress waives its own rule whenever it likes. One line in a bill saying its budget effects "shall not be entered on either PAYGO scorecard," and it is done. Congress has wiped that scorecard again and again since 2010, CRS counts over $17 trillion kept off the ten-year scorecard, and the sequester has never once been triggered. Veterans' programs are largely exempt from it anyway. The Senate has its own PAYGO rule, and it takes 60 votes to waive. Blumenthal says the Senate companion has nearly 80 cosponsors. That is not a close call. A senator also has to raise the point of order first, and Rand Paul did object to bringing the bill up without a funding mechanism. Senator Moran told the Senate the bill stalled over the cost, something "required by law." It is required by law the way a speed limit is required on a road with no police: until somebody decides to enforce it. And if a pay-for is truly demanded, offer one that does not come out of a veteran's pocket. Blumenthal already proposed $13 billion in unspent Defense Department money. Take it from the Pentagon. Not from the next veteran with ringing ears. "I already voted for the Richard Star Act twice." The package passed Wednesday by VOICE vote. No roll call, no names, nobody's vote on the record. The one recorded vote I can find from him on the clean bill is Roll Call 323, and it says No. If the two Yeas exist, send me the roll call numbers. I will happily eat the correction. I have eaten worse in a field kitchen. "This version goes nowhere." It reached the floor on a discharge petition that hit 218 signatures. The motion to take it up passed 245 to 175 with 34 Republicans joining. Then it passed 392 to 18, and the Senate companion has nearly 80 cosponsors. Senator Blumenthal says the Republican package "will be defeated in the Senate." A prediction is not a vote count, but I like his odds. A man who calls a 392-18 bill "some hashed-together deal" is a cacafuego, which is a swaggering braggart, look it up. Also, the claim that Democrats are "forcing people to vote against it." Sir, 392 members managed to vote YES without a staff meeting. What's next, a congressman votes No on the wounded veterans bill and then films a complaint that he was forced to vote... wait. I'm being told that was filmed today. Let me grade four of his claims against the record, since nobody else in that hallway will. "We just print the money": the fund is accrual-funded, and the deposits are written into the statute. "Democrats are forcing people to vote against it": 392 members voted YES, so nobody was forced. "This version goes nowhere": it passed 392 to 18. "I already voted for it twice": the only recorded vote I can find says No, and a voice vote has no names. Every one of those is checkable. I checked. What you call a false statement repeated on camera is up to you, but I know what I'd call it. Slight oversight! Congressman, I don't think your driveway quite reaches the road on this one. No rush, though. @timburchett, if I got ANY of this wrong, correct me in the replies. Bring roll call numbers and I will post the correction myself. Something tells me your account will ignore this, and silence is an answer too. But what do I know, I'm only a retired combat medic who reads the roll call before the video. #MajorRichardStarAct #EndTheWoundedVeteranTax @DavidSt59726197 Full breakdown of how the Star Act got tucked into the other package: View article
11
22
10
62
6,018