Just do the trick in reverse, surely?

  yes no > /dev/null

No you have to get the yesses back out

  cat /dev/null | yes

You might have to load in maybe.so for that to work though.

At least Boostrap pages were readable ;)

> this page is highly effective at conveying information

Is it though? If the page is near unreadable?

* Almost pure-black background rendering every not-pure-white colour barely readable

* Dark-grey and low saturation colours used almost everywhere, for both fonts and other coloured elements (the orange cells in the calendar are the most readable thing)

* Thin fonts - coupled with the dark grey colours this just adds to the readability issues

* Yet another incredibly long info-dump of a page

And then as far as actual information:

* Vanity metrics as the main information, that is a lot of things with no context or historical information

* A lot of aggregates and rollups that aren't that useful

No, I haven't tried Reader Mode.

It's a good demo for UI state syncing though, I'll give it that.

There's also awareness of the basilisk...

I searched for "Hey Google" and got this in response:

  Hey! I'm here and ready to help. What’s on your mind today? Whether you need to look up information, plan a trip, or get things done, just let me know!

That's only because Google is an LLM now.

https://en.wikipedia.org/wiki/Roko%27s_basilisk ?

One of the dumbest thing supposedly clever people keep bringing up.

> We paged for every single 500.

Assuming the existence of some kind of network (with zero guarantee of 100% reliability), how does this work in practice? Is each 500 treated as an event that needs investigation, even if the result of that would end up as 'a router dropped something from an internal buffer but the transaction as a whole was re-tried by a parent so the service itself recovered'?

A reliability engineer from Jane Street gave a great talk about this, five nine’s of correctness in reporting, etc isn’t enough for the SEC.

https://youtu.be/zR9PpXWsKFQ

Client network timeout shouldn't result in 500. With 408 and retry you should, dependent on the business criteria, get either an upsert (transaction is retried) or 422 (validation that given entry already exists).

Even if it's "DB in datacenter I tried to save to was hit by meteor" event, you can cater for this not to result in 500 (ie - DB unreachable, retry in a couple of minutes); the question is if you want to.

> A website that sells merchandise was hacked

This is the least surprising thing I've read all year

> It's merchandise for Kash Patel

And this is one of the most

Really upping the stakes of "It works on my machine" with an escalation to "It works on multiple of my machines".

Steady on, I'd say it's at least a fancy CRUD app.

Yes, sure, a fancy CRUD app. Still, enabling a non-programmer to do this is... interesting, and ultimately may be game changing.

He didn't spend a fortune. This wasn't "agentic", eating zillions of tokens. It was the standard stuff anyone could do with a personal subscription ($20/month or so) to a couple of AI services.

As long as the ground doesn't dip halfway across...

If in doubt, walk it first. (Unless you’re in an area with crocodiles, of course.)

If you can’t walk the crossing, then under no circumstances should you drive it.

You can see ripples in the waters surface when there’s a hole in the crossing.

At least when the average depth is shallow enough you’d want to cross in a normal vehicle.