Announcing the RoboTorq Reserve System — a physics-backed, robotic-labor-minted, post-quantum, proto-UBD monetary system.
Built solo so far. Now I need experts:
Rust, dstbd systems, security, robotics.
If the idea of “Watts > Wall Street” resonates, clone now 🔗⬇️
@mattyp thank you so much for the work you and your team do. Grok @bot is ushering in a @Linux Golden Age! I have similar stories with a few extensions now. I've even had my bot build two new ones to make my computer work how I want it to without sacrificing work or family time.
A bug that had been open for months now has a proper workaround that doesn't mute other features. I got the seamless multitasking and gestures I wanted, and it happened while I was working, instead of losing money bug-hunting. Tomorrow I'll send a PR upstream.
Armed with this, Linus wrote a brief for me to send to Cursor. Grok 4.7 made a logging debug mode in a new fork. The windows were resizing themselves by about 1.75 px per focus change, nearly the same as my text scaling! Tiling Shell didn't snap them back. Grok wrote a patch.
So yesterday Linus dug a bit deeper. It found a comment on a related bug report: it started after they bumped up the system font size. I tested and sure enough this was the issue, but using the standard font size on a 40" extra-wide monitor isn't viable either.
When I picked up a Magic Trackpad last week (my deal-hunter bot found it 40% off), I found I couldn't use pinch-zoom or smooth-scrolling in the X11 windows. It was time for a real fix.
A while back, I asked my Linux expert bot, Linus, to investigate: the online chatter said opening the offending apps in X11 instead of Wayland "fixed" the issue. It worked, and I went on with my life happy to not be resizing windows constantly. BUT...
Grok Bot Win: The Tiling Shell extension for GNOME is great, but my tiled windows would grow by about a pixel down and right every time I moved my mouse and focus changed, until they'd spill over other tiles. (Thread)
Yes, the green flame is caused by burning copper from depleting fuel in the regenerative cooling circuit and going oxygen-rich (closer to stoichiometric temperature) in the main combustion chamber.
Slight underperformance of engines on this flight is the reason. The booster is meant to land with tiny residuals, so the solution is to improve engine performance and performance consistency (underway with Raptor V3.2), as well as adjust flight software to do MECO1 about one second earlier to ensure enough propellant for boostback and landing (tiny change).
These early ships and boosters are already outdated by improved designs in production or on the test stand, so this booster loss does not change our timeline to reach high volume, fully reusable Starship flights.
My 1:100 model is done juts in time for the next flight… I can hardly wait for Flight 15. Maybe it’s caught, maybe not. But it’s sure the be a hell of show either way.
With Grok @bot and Build out, there's never been a better time to switch to Linux. The ability to customize GNOME extensions in a matter of minutes to fit your needs is incredible.
Grok @bot + Linux is an amazing combination.
I plugged in a 10 year old scroll wheel and told GB how I want it work: it wrote a custom daemon and the wheel just started working within about 30 seconds.
I feel like Giordi talking to Enterprise!
Saying you think we should pause progress on AI is a weird way to admit you don’t understand Game Theory. Why would anyone rather compete with China on the battlefield before even attempting to compete in the marketplace? Only 2 options, folks.