After a reboot, I traced it back to a folder in `Library/Application Support` which included a `config.json` that mentioned gulf[.]moneroocean[.]stream, so I knew I'd been popped. Cleanup was easy enough (the files themselves, plus the launch daemon), but it's annoying.

I don't do dev work on that machine (it's really just for plex & stuff) so it must have been some sort of vulnerability in Plex (but not the one described in OP) or macOS itself. Interestingly, I was up to date on my Plex install, but my macOS version was behind what was apparently an important security update related to an RCE (Sequoia 15.8).

It's also a beautiful property complete with a ecologically important bird sanctuary. Just a fascinating day!

I hate ads, but mentioning other first party services feels very different than selling parts of the system UI like a billboard.

These service upsells should be dismissible but they seem fairly inoffensive. The App Store ads, on the other hand, are just atrocious

I wanted the Prusa to be just as good, which is why I started with it. I wanted to support the open ecosystem, but not at the expense of not getting to do what I actually set out to (print things nicely). It's a shame! Maybe I was holding it wrong (but again, with the Bambu, I didn't have to worry about it).

- https://po-ru.com/2026/07/29/it-doesnt-matter-whether-matz-i...

- https://blogs.gnome.org/alatiera/2025/11/06/dhh-and-omarchy-...

Now, because supply is so constrained relative to demand, there's no limit. More is always better, which leads to a crazy amount of construction (as its negative effects).

Maybe we are using different tools (or we've set it up wrong) but I'm consistently surprised at how slow Go's linting is (using golangci-lint). Takes nearly 5 minutes on our codebase after any change (which means I just don't run it locally or in-editor). It's remarkable how poor the experience is after using tools like Python's Ruff (instant) or Rust's Clippy. I'd have expected a fast, default setup that I could tune.

Event JS's Eslint, which runs in actual JS, takes 21 seconds for a full sweep (which I don't normally run, since the in-editor hints are so fast)

It's surprising, because so many of Go's dev tools are so well thought out!

Best case scenario it keeps working without totally jacking up the prices. But also starting to think about long-term alternatives. BaseRow seems reasonable, as does spinning all of my many bases into a single big Django monolith (something I've had in the back of my head for while anyway). But it's been nice not having to micro manage this service. Pretty good mobile app, too. Enjoyed it while it lasted, I guess!

We're looking for a senior-level Go developer who can design and ship idiomatic code our users love to work with. We can all write Go that compiles, but don't always know what best practices for 3rd party code are (in the Go ecosystem specifically). Ideal candidates are a part of the Go community / ecosystem and know what the current best practices are. They also probably have TypeScript experience (most of our tooling is TS) and in a perfect world, Ruby/PHP ecosystem knowledge (the other languages we're currently seeking expertise in). But, if we get a Go expert who's willing to learn a bunch of TypeScript, that probably works!

JD and application: https://stripe.com/careers/listing/backend-engineer-develope...

The best way to apply is to go through the form on the site. Happy to answer questions here though! It's a fairly unique role.

This is a wild claim because it's trivially provable. There's been tons of reporting around the effect they have on the immediate vicinity, and that's without even getting into the unknown long-term effects.

Here's a decent piece, but there's plenty more out there if you look at all: https://www.youtube.com/watch?v=t-8TDOFqkQA

Is every single mad person doing investigative reporting and / or living next to a data center? No. But something doesn't have to personally affect me to know it's harmful.

One of my favorites!

https://www.reddit.com/r/calvinandhobbes/comments/u3dqja/how...