Steven Walter

I’m not asking you, I’m telling you. Take a moment and listen to this 81 second response from Victor Glover after being asked if he had any thoughts leading up to Easter. I don’t quite think it can be overstated how perfect this crew is for the job.

WHOA... 10 million wire grill brushers were just recalled. (3 million were recalled last month). I did not anticipate this when we made the Smarter Scrubber to address the problem. We just caught up on production. If you'd like a chain mail grill scrubber that's made in America check out SmarterScrubber.Com

Well. I think I have a new favorite movie. #projecthailmary was a fantastic adoption of the book, specifically Rocky! He was so great! Thank you to everyone who helped make such a unique and wonderful story come to life! @andyweirauthor @RyanGosling

@TeamTwiizers That's wrong. GrapheneOS users can currently use around 9/10 banking apps because most haven't adopted attestation to ban using alternate operating systems. Unified Attestation will encourage broader banning of arbitrary operating systems. It will hurt GrapheneOS and others.

I crunched some numbers for my own curiosity. I have roof-top solar, and it's great. However, it seems like some people have unreasonable ideas about running the grid on 100% renewables. Since I now have real-world data from one year of solar production, I did the math... I won't bury the lede too much: there is an interesting "15/15" rule. That is, you'd need 15x the "nameplate production" in solar, and 15 days of storage if you want to be fully off-grid with no outages. Caveat: this is assuming mid-latitude USA. Further north would be worse, further south better, so this should be a good average. To be a bit more specific about what "15x production" means. Suppose you use 30kWh per day. If the sun were directly above you 24 hours per day (spoiler, it isn't) and there were never clouds and solar panels were 100% efficient, you'd need 1250W of panels. In the real world, you'd need 15x that amount, or ~19kW. Needless to say, if you scaled that up to the entire United States, it would be fantastically expensive. My napkin math says ~$1400/MWh LCOE, or 10x more expensive than nuclear.

@dougcj37 It definitely brings back memories!

@srwalter Fancy! Does it smell like the 80s?

At long last

It came with bling 😂 @commodoreofcl

Can you, the people, “vote your way out of this?” Honestly, not if you get your news from these folks. The swamp has tricks for deceiving the public, and most even work on congressmen. Here’s an example of how Laura and Greg played along as happy tools of the swamp. Please ask yourself why your own congressman has never talked about this. He either hasn’t gotten this far in the game (80% chance), or he likes the way the swamp obscures what’s going on (10% chance), or he dislikes the system but the price he’d pay for telling you is too high (10% chance). If a congressman sees this post and wants to debate me, I accept! The House has rules we adopt at the beginning of each Congress. Honestly we should just use those - some go all the way back to Thomas Jefferson. Some are like Robert’s Rules of Order which branched from House rules a century ago. But we have a rules committee that modifies the rules every week. I served on the rules committee for two years. When I was on the committee, I refused to vote for rules changes if the purpose was to mislead or obscure. Every week, the rules committee bends the rules to suit the Speaker, but you can’t place the blame just on the committee or the Speaker. Every rules change must be approved by the whole House with a majority vote. Rank and file congressmen are told to vote for these rules modifications each week for the sake of party loyalty because the rules are temporarily modified by the majority to keep the minority from using the permanent rules against us. This is partly true, so most congressmen never question beyond this. Typically, every week the rules committee meets before other committees and writes a rules package to protect bills that will come to the floor that week. Then the whole house votes on this rules package early in the week before significant legislation comes to the floor. The vote is typically on party lines. Sometimes a block of congressmen in the majority will take the rules package hostage and withhold their vote to get something else that has nothing to do with the rules. I’m not a big fan of this, but after 13 years, my hands aren’t completely clean of this tactic. The high-road position that I try to maintain is that if the rules package is bad, you shouldn’t vote for the rules package, and in general you shouldn’t withhold your vote from a rules package if there’s nothing wrong with the rules package… even if you disagree with the policy that is enabled to come to the floor by the rules package. There are more details, but that’s all you need to know to understand what I’m going to explain next. This week the Speaker wanted to do two things outside of our base rules, so he put those inside of the rules package that also had the rules for bringing bills like the popular SAVE Act to the floor, knowing members would be afraid to vote against something associated with SAVE. THIS IS INTENTIONAL. The Speaker wanted to circumvent the National Emergencies Act of 1976 to avoid voting on tariffs and he wanted to turn off the ban on bringing a spending bill to the floor the same day it’s introduced. The first rules package that came to the floor this week failed because myself and other republicans objected to it. The rules committee met again, wrote a new rules package without the tariff-trick, and we voted on the second rules package. I voted no but internet goons, like clockwork, characterized this as a vote against the SAVE Act. The swamp used that second rules package to give them authority to pass a bill before anyone could read it. They hid that authority inside the rule for the SAVE act because they knew people like Laura and Greg would help them disparage anyone who didn’t go along. If you fell for Laura and Greg’s slop you were cheering for the Pelosi doctrine that we should pass bills to see what’s in them. If the rules package had failed, the rules committee would have written a better one and SAVE Act would have still come to the floor.

This is the most common ploy of the anti-@RepThomasMassie politico and punditry folks. To claim he voted against a bill’s seductively titled cover page, when it’s the unconstitutional crap jammed behind the title page that he votes against. Typically, those very things your favorite GOP politician also campaigned against … but knew you’d also fall for the title page misdirection while they stuff the bill with everything you voted against in the last election cycle.

I'd be curious to hear your thoughts on how closed AI models and the open source ethos interact. One of the reasons I haven't investigated LLM-assisted coding more heavily is that I'm uncomfortable with being dependent on a proprietary service in order to write code. Apologies if you've written on it before!

A possibly interesting report of a current experience with ChatGPT 5.2. TL;DR: it makes translation of complex C code into Golang practical. I maintain a program called cvs-fast-export that does what it says on the tin - generates a Git fast import stream capturing the state of a CVS repository. Internally it's pretty horrible. About 12 KLOC full of malloc/free fuckery and algorithms that are kind of like the old joke about the Schleswig-Holstein controversy: Keith Packard, who wrote them in order to lift the X repositories back in 2006, no longer understands them, and I have spent significant portions of the last decade trying to understand them and failing. One of the things I've gotten really tired of dealing with over the years is heap-corruption bugs in this code. Accordingly, I have been wistful about moving it to a more memory-safe language. But until recently I rejected this project as just too hard. Two things changed my mind: our robot friends, and the fact that somebody else wrote a Go library that parses RCS master files. This is one of the two nastiest complexity hotspots in the code, mainly because of the hair involved in integrating RCS change deltas into complete file states. (The other nasty part is the collation algorithm that merges CVS per-file changes into Git changesets. That's the deep magic that nobody understands.) At 0930 yesterday morning I started talking ChatGPT 5.2 through the process of porting the code. I did it right, developing a detailed action plan first and having it analyze the magic collation algorithm from the C code. Then I started it writing code, walking it through the steps to go from skeleton to working program and reviewing each step. It's now almost 24 hours later. I did sleep a little, but I'd say I've put in about 18 hours of work on this. The Go version of the code is running and passes 37 of its 56 regression tests. The 19 that are still failing are mostly down to a nasty hard core where it's uncertain if the C code was doing the right thing then or the Go code is doing the right thing now, due to almost philosophical issues about the mismatch between the CVS model of revisions and tags versus Git's. Pretty damn good for 18 hours of work from a cold start. It strongly suggests that other projects requiring code translation at scale are now practical. With significant applications for the defect rate of those codebases; whatever else goes wrong with it, the Go port of cvs-fast-export well at least never have a heap corruption or both buffer overrun error ever again.

@dougcj37 🤣

New York Wants to Ctrl+Alt+Delete Your 3D Printer New York’s budget bill proposes mandatory file-scanning “blocking” software for 3D printers and CNC tools. It targets general-purpose tools instead of criminal acts — and puts educators, open source, and small makers on the hook first. 🗽🖨️ blog.adafruit.com/2026/02/03/new… #3dprinting #opensource

@courtneyknill If you have a 3D printer (or know someone who does) you can print one for pennies. I'll never pay for a phone case again

I need to replace my phone case, but why is it $55 😭

@naeriface Now that's medium rare 😁

O Christmas tree, o cosmic tree 🎄 Located about 2,500 light-years from Earth, NGC 2264 is a cluster of young stars between one and five million years old. The stars appear as blue and white lights surrounded by swirls of gas—the “pine needles” of the tree—with green representing light in the visible spectrum. Learn more:go.nasa.gov/3MN1xdX

“Good night, good luck, a Merry Christmas, and God bless all of you, all of you on the good Earth.” Frank Borman, Commander of Apollo 8, transmitted from lunar orbit 55 years ago this evening.

The Teacher’s Union fought phonics-based instruction bc it was mundanely effective at teaching kids to read and didn’t let the teachers feel like selfless martyrs. This is Munchausen syndrome by proxy and the Union should be nuked from orbit.

@naeriface Nice cut of meat. Personally I'd have cooked it a bit less. I nice a nice medium-rare. How about you?