Compared to getting them nothing, yes. But the OP's point is that this doesn't prevent the child from mentally comparing themselves to peers that have a smartphone, and viewing their Tin Can as a "restriction" imposed by their parents.

Which it is. I don't understand the need to wink-wink-nudge-nudge pretend it's anything else by the others in this thread. Just own it, restrictions aren't bad by default.

Well then clearly you haven't taken a look at https://status.claude.com.

At that 3rd party side GH is currently noticeable worse then claude ...

Like they are down to one 9 availability and very very close to losing that to (90.2x%).

This also fit more closely to my personal experience, then the 99.900-99.989 range the article indicates...

Through honestly 99.9% means 8.76h downtime a year, if we say no more then 20min down time per 3 hours (sliding window), and no more then 1h a day, and >50% downtime being (localized) off-working hours (e.g. night, Sat,Sun) then 99.9% is something you can work with. Sure it would sometimes be slightly annoying. But should not cause any real issues.

On the other hand 90.21%... That is 35.73h outage a year. Probably still fine if for each location the working hour availability is 99.95% and the previous constraints are there. But uh, wtf. that just isn't right for a company of that size.

You may have fumbled the calculator at one point. 20Min per 3 hours is 88.8% uptime. 99.9% uptime is 11 seconds down.

what I meant is having both at the same time

- at most 20min per 3 hour

- and 99.9% uptime on a yearly basis

as in your yearly budged of outage is ~8.76h but that budged shouldn't happen all at once and if there is an outage it at most delays works by 20min at a time, and not directly again after you had a downtime

but I did fumble the 90.21% part, which is ~35.73 days i.e. over 857 hours....

> On the other hand 90.21%... That is 35.73h outage a year.

Days, not hours.

This is ... surprisingly honest? The one above is "missing" status page; and most status pages would legally have to be filed in the "fiction" section of the library.

I get the email notifications from Anthropic’s status monitor, and I think they might be my most frequent emailer these days.

If this was an Apple TV app, I think it would be the default mode in my household.

Improves outputs relative to what? Compared to previous contexts of 1M, it improves outputs by allowing them to exist (because previously you couldn't exceed 200K). Compared to contexts of <200K, it degrades outputs rather than improves them, but that's what you'd expect from longer contexts. It's still better than compaction, which was previously the alternative.

I don't think they're claiming "no degradation at scale", are they? They still report a 91.9->78.3 drop. That's just a better drop than everyone else (is the claim).

Those sorts of volume discounts are what you do when you're trying to incentivize more consumption. Anthropic already has more demand then they're logistically able to serve, at the moment (look at their uptime chart, it's barely even 1 9 of reliability). For them, 1 user consuming 5 units of compute is less attractive than 5 users consuming 1 unit.

They would probably implement _diminishing_-value pricing if pure pricing efficiency was their only concern.

Diametrically opposite to tokens beyond 200K being literally free? As in, you only pay for the first 200K tokens and the remaining 800K cost $0.00?

I don't think that's a fair reading of the original post at all, obviously what they meant by "no cost" was "no increase in the cost".

I can see that's what they mean now that I've read the replies, but when I first read that top comment I too parsed it as meaning 201k would cost the same as 999k (which admittedly did seem strange, hence I read the replies to confirm and sure enough that's not actually the case!)

What percentage of the overall code was written primarily by agents?

Amazing-looking UX. My biggest feature suggestion: implement support for SSH jump hosts. I suspect having a single SSH gateway in your homelab that you configure all other hosts with ProxyJump in .ssh/config is a super-common setup amongst your target audience.

Why would a knife be a problem in a checked bag, even if it hadn't been sealed in the original package?

I've asked TSA people similar questions when they checked my bag. He said that the item was blocking view of what was underneath it.

I'd guess it's not the packaging, but a big piece of steel blocking the xray view.

The x-ray machine aren't 360?

If 360, I wonder does the operator perhaps not trust it?

CT baggage inspection is (fairly) new and only used in some places like carry-on screening. This was probably a behind-the-scenes belt x-ray planar image where the giant chunk of metal blocked everything underneath, so they kicked the bag out for a quick look somewhere along the line.

It’s not too unsurprising to see bags routinely get re-xrayed in the belt system when they come off of flights back stage.

probably different fidelity of scanner, I'd guess. This was in 2018-2019