my futurelock talk from #tokioconf is up! check it out, enjoy the story of a nightmare bug we saw at @oxide.computer

I know this is (supposed to be) marketing. But all that is true. I think it’s gotten significantly better but the amount of oddities in the stack you will have to own is long. And I am not even talking about the BMC, but whatever runs on switches, routers to flashing fiber optics etc.. painful af.

I mean I had certain games crash the computer just cause the microcode being out of date. I wish I could have an Oxide Rack for Home Use

I spent longer than I’d like to admit chasing firmware on my homelab cluster. Updated the BIOS to get network issues sorted for a couple nodes, then discover the fan controller were corrupted. every fix was its own incantation of deprecated installers 🫠

Having spent a good amount of time on a team managing k8s on bare metal, this tracks. Most of the time the issues were failures between k8s components and the underlying compute/network/storage, not in k8s itself, which is a lot harder to google for.

Kubernetes on bare-metal is rough. However, I love that my team gets to build Kubernetes integrations for Oxide on top of such an amazing product. Our goal is to make it a no-brainer to choose Oxide.

We have all Kubernetes on bare metal on our home network, and this is all true. Luckily it's not a production environment though!

I endorse this message.

I feel like this post is directed straight at me and my previous team at $EMPLOYER.

Can't I just build my own cloud computer? FAQ Friday #47

Last week, @bcantrill.bsky.social were joined again by the founders of the @oaklandballers.bsky.social--that's right, another baseball episode! @oxide.computer is excited to announce both our sponsorship of the Ballers and our upcoming joint, baseball/tech hackathon!

One of the things I love about Oxide is our Demo Friday, where some of us demo good error messages and get hoots and hollers. Demos, generally speaking, are usually of the happy path

The thing I'd add is I think this also represents our empathy for datacenter technicians: the people who have to deal with the unnecessarily loud fans every day, and who get to enjoy a that much quieter environment as a result of our tighter design

bryan says it's more about the power efficiency but we all know it's so we can put oxide racks in our bedrooms and still sleep at night

My personal website now runs on Oxide Computer Company by dogfooding my team's Kubernetes integrations. Let's talk architecture.

Why do we talk about fan noise so much? FAQ Friday #46

Trust good ol' 31na22fxs6fszqooqlgpqydistfu to come to our defense in the face of burgerking's predictable slander...

at oxide we have, straight up, the best openapi generation and management tooling in the world

Learning about @oxide.computer's Hubris RTOS has been an incredible exercise in how different systems can be. In some sense, it has essentially made the polar opposite choice to everything I've done with embassy, async, and ergot over the past 3-5 years. Neither are *wrong*, they're just different.

Today, Paul Freedman and Bryan Carmel from the @oaklandballers.bsky.social return to Oxide and Friends, joining @ahl.bsky.social, @sdtuck.bsky.social and me to reveal some exciting collaborations with @oxide.computer! Join us, 5p Pacific today: discord.gg/QrcKGTTPrF?e...

CI/CD is so much better on ephemeral @oxide.computer instances.

We’re ramping up manufacturing at @oxide.computer; part of that is efficiently validating the cabled backplane and network switches. On Monday @bcantrill.bsky.social and I spoke with colleagues about “Reverso”—a huge boon to manufacturing… with one bizarre bug to fix first

@oxide.computer CLI keyring

Yeah I got it running (not well) on an old laptop with some tweaks. It definitely needed more resources but it did mostly work. @matthewsanabria.com later posted his guide, which is probably a good place to start if you want to take stab at it: www.youtube.com/watch?v=qwXt...

I've been in California for six whole hours and I've already been roped into doing a podcast

Today on Oxide and Friends, @ahl.bsky.social and I will be joined by our colleagues to tell the tale of Reverso, an interesting (and deceptively simple!) piece of hardware that has proved essential to scaling manufacturing. Join us today, 5p Pacific! discord.gg/QrcKGTTPrF?e...

Brogrammer Garry Tan has been boasting about "writing" tens of thousands of lines of code each day as the paragon of productivity. Last week, @bcantrill.bsky.social and I were joined by @gregore.in to take a closer look at what Tan was generating. Is this really the right way to build system?

Last week, @bcantrill.bsky.social and I were joined by members of the Oxide mechanical engineering team to talk the mechanical challenges of building a rack-scale computer, and--in particular--of scaling manufacturing from just a few racks to hundreds.

3 podcast episodes in a week--smoke the whole pack, Oxide and Friends listeners! share.transistor.fm/s/31855e83

try this. I dare you

Web 3d explorer for @oxide.computer. Built in three.js/r3f. Tonnes of little interactions and details in this. Poke around, and take a look at the guided tours. explorer.oxide.computer

AI is an existential topic for all aspects of education--for none more so than Computer Science. @bcantrill.bsky.social and I were joined by @kfisler.bsky.social and @shriram.bsky.social to discuss their agentic intro course. What do students take away from their "smoke the whole pack" approach?

Can I reuse my existing servers with Oxide? FAQ Friday #44

New eye candy coming soon from the impeccable @oxide.computer design team

making really good progress on the new raytracer – this is with caustics and subsurface scattering turned on

LLMs are changing every aspect of higher ed, but perhaps none more so than CS. Today, @ahl.bsky.social and I will be joined by profs @shriram.bsky.social and @kfisler.bsky.social to talk about their experiences enabling students with agentic AI. Join us, 5p Pacific today! discord.gg/QrcKGTTPrF?e...

What's THE differentiator for Oxide Computer Company? FAQ Friday #43

On Monday's episode, @ahl.bsky.social and I will be joined by @oxide.computer's mechanical engineering team to talk about their work on the manufacturability, reliability, serviceability, and (yes!) safety of the Oxide rack. Join us, at a special time of 3p Pacific Monday discord.gg/QrcKGTTPrF?e...

How does the Oxide Cloud Computer's power shelf work? FAQ Friday #42

some really cool work from my colleagues Andrew Stone and Finch Foner went into making Trust Quorum a reality — their podcast episode on the subject is definitely worth a listen!

Release 19 is now LIVE & you're going to want to check out Trust Quorum. How do we truly attest to the security of a system distributed across many physical hosts that will be swapped out over the system's lifetime? Read the full release notes here: buff.ly/cobURMz

Can Oxide run across an air gap? FAQ Friday #41

The @oxide.computer rack contains within it a distributed system that needs to trust itself. But how is this trust built? This week, @bcantrill.bsky.social and I were joined by colleagues Andrew and Finch to explore how Trust Quorum was designed, built, and verified.

maybe the biggest question everyone has been asking about Oxide, finally answered!

Amongst other things, I am MUCH better at coding and making software having worked with David all this time.

Interactive 3d explorer with React Three Fiber. Worked with an artist to fix the topology and reduce the size of the CAD model. Custom LUT to more closely match the colour grade of the renders.

Why the obsession with Diet Coke? FAQ Wednesday #1

I was struggling to get a full height hero to work here until I realised I could dynamically change the number of racks on screen. From the latest @oxide.computer (oxide.computer) refresh.

Debugging an issue for work and I forgot how powerful it is to return json from a DTrace probe. This is tracking a virtio-socket packet flow between guest and host.