This isn't really security-related. The "AskUserQuestion" hook in question here is not the one that gets used for authorizing actions. That's a completely separate mechanism that is unaffected by this 60-second timer thing.
What this is referring to are those follow-up "here's two plausible alternative ways to do this, which one do you prefer?" questions you sometimes get, and usually at the beginning of a planning session when presumably you're still actively involved in the session. They get exponentially less likely as the turn goes on.
Maybe it's a good default, maybe it's not, I'll wait to pass judgment. But it's not security-related except in contrived scenarios you could construct where one side of an A-or-B UserQuestion has security implications that aren't caught by any other safeguard. I haven't ever really experienced that in practice.
How does that contradict the price increase? iPads still have RAM, yeah? If anything, not increasing the prices on iPads would undermine Macbook marketshare, would it not?
I can’t believe I’m nitpicking this on HN of all places, but the Taurus-Miltank thing is just fan headcanon based on nothing more than the analogy with real-life animals. While it’s true that Tauros is a male-only species and Miltank is female-only, they have separate Pokédex numbers and were introduced in different generations.
They can breed (because they’re in the same egg group) but the offspring can only ever be a Miltank. The only way to breed a Tauros is via ditto, same as with any other male-only species.
I've long maintained that the real indicator that AGI is imminent is that public availability stops being a thing. If you truly believed you had a superhuman, godlike mind in your thrall, renting it out for $20/month would be the last thing you would choose to do with it.
I don't think OP was making a value judgment or anything. It's just weird to say you won't consider Codeberg because you need reliability when Codeberg's uptime is at 100% and Github's is at 90%.
Windows is not public infrastructure. If the government's reliance on it has reached the level of "national importance", then that's the problem that needs to be addressed, not Windows' ownership.
Public infrastructure should be built on open-source, period.
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.
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.
What this is referring to are those follow-up "here's two plausible alternative ways to do this, which one do you prefer?" questions you sometimes get, and usually at the beginning of a planning session when presumably you're still actively involved in the session. They get exponentially less likely as the turn goes on.
Maybe it's a good default, maybe it's not, I'll wait to pass judgment. But it's not security-related except in contrived scenarios you could construct where one side of an A-or-B UserQuestion has security implications that aren't caught by any other safeguard. I haven't ever really experienced that in practice.