Really? I thought you could only do that with open source models. Can you teach me how to checkpoint the current version of Claude Code so I can keep it as-is forever?
Stack overflow was useful with a fairly sanitized search like “mysql error 1095”. Agentic LLMs do there best work when able to access your entire repository or network environment for context, which is impossible to sanitize. For a season, private environments will continue to be able to use SO. But as LLMs capture all the good questions and keep them private, public SO will become less and less relevant. It’s sad to see a resource of this class go.
Somewhere out there, there's an alternate universe in which the Stackoverflow community was so friendly, welcoming, helpful, and knowledgeable that this seems like a tragedy and motivates people to try to save it.
But in this universe, most people's reaction is just "lol".
If a nonstandard X header becomes widely used and then adopted as the standard, there is a surprisingly lengthy and difficult transition period to the new name.
Both clients and servers have to support both the X name and the regular name for decades, and servers have to deal with questions like "What if both are present but different?"
If both are present but different the unprefixed version should be favoured. That seems uncontroversial & not complex to implement.
Sending two headers seems fine in most cases.
These are certainly downsides but hardly dealbreakers. On the other side, not prefixing has its own pros & cons, which seem more difficult to work around:
1. The obvious clash issue. If two pieces of software implement entirely different X-Value: headers, the standardisation effort clarifies the signal in the form of an unprefixed version. If both competing software applications start out unprefixed, the signal will always be ambiguous.
2. Implementation changes. If any lessons are learnt during initial use of a prefixed header, these can be applied by standardising on a slightly improved unprefixed version.
Smuggling is a general concern whenever two headers have functionality that interact - it's not specific to prefix masking & given how implementation-based it is, it's not even likely to occur to any arbitrary prefix mask.
That's not a reason not to consider it a threat vector when implementing, but no more than when implementing any header (that interacts with another)
But isn't the problem with X- headers that if they ever get standardised, they necessarily create this smuggling issue? Whereas if you start with an unprefixed header and standardise it under the same name, you avoid this issue.
You could also solve the problem by standardising the header with the X- prefix, but this is more confusing to users and violates the idea that X- always means "not standardised", at which point the prefix is useless anyway.
> That's not a reason not to consider it a threat vector when implementing, but no more than when implementing any header (that interacts with another)
But the header wouldn't have interacted with another header if we hadn't decided to do this X-prefix nonsense!
> And when I finally—finally—tried to test online play, Minecraft told me I would need to loosen the parental controls (it did not say which) and create a Nintendo Switch Online account for my son.
I'm a bit confused by this section. It seems to me that the author
1. Turned off online.
2. Bought a game that could be played in single-player or online
3. Got mad that online didn't work because it was turned off
4. Turned online back on
5. Got mad that online was turned on.
6. Dealt with this anger by yelling at his children
I actually don't understand what the author was trying to accomplish here
Vinyl was infamous for degrading during use to the point where you could identify whether an album had been played more than a dozen times by the reduction in sound quality.
this is perhaps a language barrier, but I'd call "measurement of getting worse during use" *durability*, while degradation is exactly about not-in-use deterioration...
reply