Aereo - Wikipedia

And a service which let you rent an antenna (over the internet) was sued out of business: en.wikipedia.org/wiki/Aereo

The ugly truth: I don't update all that often, so it's somewhat of a production, which makes the taking of snapshots a key part of the ritual.

I've long had kernel and kernel-headers marked with IgnorePkg, so that they require an explicit sync to be updated. It avoids a similar mess when OpenZFS support for the latest kernel version has not caught up.

This is a BIG one that enables our customers to expand the types of workloads they land on the Cloud Computer.
Read more here: buff.ly/4EGrUq6

Deep Blue We coined a new term on the Oxide and Friends podcast last month (primary credit to Adam Leventhal) covering the sense of psychological ennui leading into existential dread that many …

On the @oxide.computer and friends podcast last month we (primary credit @ahl.bsky.social) coined the term "Deep Blue" for the sense of psychological ennui leading into existential dread that many software developers are feeling thanks to LLMs right now simonwillison.net/2026/Feb/15/...

Oxide plans new rack attack with Zen 5 CPUs, DDR5 : Oxide says AMD’s Turin EPYCs are coming, switch revamp under review, more open hardware in the works

We raised a $200M Series C, now we're putting it to work.

New compute sleds with the latest AMD EPYC CPUs are coming. We're also working with Xsight Labs on next-gen switch silicon with a fully open instruction set architecture (ISA).

The Register has the details: buff.ly/6ghM2b6

If you have ever struggled with a server whose bios won't netboot because there's a misconfiguration on the switch, or the Ethernet cable is not coded right for the speed of the server's card (because your vendor silently "upgraded" you to 25 Gbit because they were out of 10 Gbit cards), and then when it does boot, it is thermally throttled because it's tiny fans happen to be blowing in the one spot where your electrician tied a bundle of electric cables 10 cm thick, and then once you get the thermal throttling problem solved, you find out your version of IPMItool is incompatible with some stupid extension your server vendor defaulted to "on",, then you might understand why Oxide is a good deal. If you idea of installing a server is "terraform", you're not going to get it.

this guy gets it

Our $200M Series C / Oxide Raising our Series C round of financing

Our $200M Series C
oxide.computer/blog/our-200...

> Better known for other work

Great work. Thank you

GitHub - pfmooney/ad2cfp: ACME-DNS to Cloudflare Proxy ACME-DNS to Cloudflare Proxy. Contribute to pfmooney/ad2cfp development by creating an account on GitHub.

I wanted to explore LLM coding capabilities, and had a low-stakes personal project in mind: github.com/pfmooney/ad2...

obsessions like this come with trade-offs

9 days in 2025 when I didn't bike outside or on the trainer, each one of them painful in their own way

In case you're wondering if he's the real deal, Brewster often rushes down in a power event to personally power up servers on notifications from the staff.

Yeah, I'd be interested to see convincing justification for such silent unlocks. I find it hard to imagine a situation where that's the right thing to do.

In the mean time, I'm just wrapping Mutex (and Condvar, etc) to get the infallible-by-default behavior.

Provided they can provide a `--fix` helper when crossing an edition boundary like that, it would be a pretty painless (and nice!) change.

100%

Making Mutex::lock() panic on a poisoned lock, and pushing those who need it to try_lock() or something like fallibly_lock() would have made things easier for what I have to believe is 99+% of the time.

My feelings on the matter are mixed, when it comes to Rust. Making Mutex::lock() fallible, despite being congruous with the rest of std, and Rust's error handling ethos in general, does seem rather unfortunate. I appreciate that it _can_ be handled at runtime, but it's a pain in the common case.

Launching the 2025 State of Rust Survey | Rust Blog Empowering everyone to build reliable and efficient software.

It's time for the State of Rust Survey!

The Rust Project invites you to take this year’s survey, whether you have just begun using Rust, you consider yourself an intermediate to advanced user, or you have not yet used Rust but intend to one day 🦀

The genre twist in the 3rd act is (IMO) its weakest aspect, but it remains a banger despite that

Drivin' the high line (US-2)

Every time I see physical attacks on TEEs, I wish someone would put out a position paper on @hdevalence.bsky.social 's "guy with a glock" model
x.com/hdevalence/s...

rust-analyzer now fully uses the new trait solver! 🎉🎉 rust-analyzer.github.io/thisweek/202...

Drink enough and you can see through time.

Being able to seamlessly fall back to doing "normal" git things definitely makes the transition easier, without (IMO) losing many of the jj benefits.

Working in a large (illumos-gate, an entire OS) repo has been mostly fine, given that I disabled auto-tracking of files. Having to manually add new files to be tracked closely matched my tendencies with git anyways.

Grosse Pointe Blank - 10 years YouTube video by Peter Ghosh

www.youtube.com/watch?v=WWOn...

Proposal: any product from a vendor who's going to DMCA you for doing fun things with their product needs a sticker on the box saying that