frio

Even on the 120Hz displays, you can choose to cap them to 60Hz in settings.

The default setup is to configure an Internet accessible DB. So yes — the credentials leak has also likely compromised many databases too. They are still obscuring the impact.

I also want to briefly note that communicating, from the outset, "this is a significant incident, your keys are compromised, the attack is ongoing and you cannot enter new keys as _those too will be compromised_" is a better response than leaving people to figure out the unfortunate combo endpoint of "my keys are compromised, I have rotated them, this has broken my site but I have new keys, and oh surprise, I can't deploy". The full story needed to be communicated more clearly; the email just said "revoke your keys", which I urgently did... and then remembered/found out that changing environment variables requires a deploy.

I would rather have known earlier that I should put a notice on my site, or my own social media, or notify my own customers ASAP and disable some functionality (or make my own choice about porting somewhere else as a mitigation) than get caught out like this after the horse has bolted and it turns out you've been desperately trying to get it back into the paddock for days.

> and although we have been up for days on end- I don't blame you if you don't have sympathy for us.

From my timezone, this started last night and is ongoing into today. Has this been going for longer than the status page and email indicated? If so, why was notification delayed so long?

I love your product, have an incredible amount of sympathy for you as humans (having been in similar sleep-consuming nightmares) and was willing to forgive the GCP-triggered outage as an understandable teething pain, but sadly this response has really knocked my confidence.

I understand the hard reality of security issues -- "urgently rotate your keys, they're already compromised" is an important message to share -- but "sorry, that will also require your site going down because we've blocked deploys" (presumably as a response to the incident...) is an incredibly frustrating situation to find ourselves in.

Yep. What an incredibly frustrating notice. I like Railway and I guess their hands are tied here, but wow.

I'd love a Tangara, it's a pity they can't be ordered any more.

Not so bad, New Zealanders won't get it at all :(.

In that case, sorry for getting it wrong and throwing shade.

> The honest tradeoff

> That’s not a hypothetical cost - it’s

> But that’s exactly the

These are strong tells for an AI authored article. I know we're all tired of people saying "this is AI" as it's harmful to discussing the content of an article, but articles about AI, (seemingly!) written by AI, extolling the virtues of AI -- don't really seem to drive the discussion forward to me either.

It’s real VMs, firecracker style.

I work remotely, and when trying to discuss concepts with others, I frequently doodle things out with pen and paper (just like I used to on a whiteboard in an office). Having a Supernote means I can share my diagrams live on the call, just like a real whiteboard, which in turn makes it easier to communicate with my coworkers.

I've used all kinds of drawing apps on the web previously, and the extra impedance of the mouse/canvas/tool selection/whatever frustrates the whole process.

I’m not excited about using Opus 5, mainly because the way that I work atm — essentially peer programming — means I sandbox the agents and work with them closely. Opus 4.x encounters the sandbox and moves on with its day; Fable becomes increasingly fixated on it and does less and less of the actual task, focussing more and more on the limit it reached. I worry that, from your description, Opus 5 will do the same.

Even well-supported, well-documented projects. I'm in the middle of a Spring Boot upgrade, which includes a collection of Hibernate updates. These are well-supported projects with -- theoretically -- fantastic documentation. But when something goes wrong, trawling them for what's happened is tedious and doesn't teach me much; you end up chasing down uncommon threads. The death of StackOverflow doesn't help much either. Previously, web searches might have found a commiserator, but that's all gone now.

A concrete example: during one of the updates, previously working code started throwing an OptimisticLockingException. Only in one place, annoyingly. My thought was that Hibernate was more strict about something it had previously been lenient about. I went down two or three false threads in the docs; I debugged the old version and the new version and read the guts of Hibernate but couldn't figure out why the persistence path had changed so significantly (or why it'd throw an OptimisticLock, it was saving a brand new row!). I was really struggling.

I set Opus on it, and it found the relevant section of the docs and zeroed in on the issue in the code: we were generating and setting an ID on a class that had an annotated @GeneratedValue. Old Hibernate said "whatever"; new Hibernate changed the persistence code so in this situation it calls `merge` instead of `save` (update rather than create AFAICT); there was no existing entity with the generated ID (of course, it's a new entity!); it fails.

While my hypothesis was broadly right, that _particular_ issue would've taken me days to chase down -- but the LLM correctly diagnosed in minutes with links to relevant documentation.

I vaguely hate LLMs, but this one saved me from a days long side quest that would've held up delivering the actual value of the project. I hope this doesn't sound like my brain is no longer functioning.

(edit -- reading it back I'm starting to write like one of the fucking things, which is probably the part of them I hate the absolute most)