Live data from Hacker News

Claude Code's source code has been leaked via a map file in their NPM registry

twitter.com

331–340 of 1001 posts

Re: Claude Code's source code has been leaked via a map file in their NPM registry

#332
post #84

They have an interesting regex for detecting negative sentiment in users prompt which is then logged (explicit content): https://github.com/chatgptprojects/claude-code/blob/642c7f94... I guess these words are to be avoided...

I don't know about avoided, this kind of represents the WTF per minute code quality measurement. When I write WTF as a response to Claude, I would actually love if an Antrhopic engineer would take a look at what mess Claude has created.

WTF per minute strongly correlates to an increased token spending.

It may be decided at Anthropic at some moment to increase wtf/min metric, not decrease.

Re: Claude Code's source code has been leaked via a map file in their NPM registry

#333
post #286

Earlier quoted context omitted.

It's how people resisted CGI back in the day. What people dislike is low quality. There is a loud subset who are really against it on principle like we also have people who insist on analog music but regular people are much more practical but they don't post about this all day on the internet.

I think literally everyone could agree CGI has been detrimental to the quality of films.

Not just in the obvious ways either, even good CGI has been detrimental to the film (and TV) making process.

I was watching some behind the scenes footage from something recently, and the thing that struck me most was just how they wouldn't bother with the location shoot now and just green-screen it all for the convenience.

Even good CGI is changing not just how films are made, but what kinds of films get shot and what kind of stories get told.

Regardless of the quality of the output, there's a creativeness in film-making that is lost as CGI gets better and cheaper to do.

Re: Claude Code's source code has been leaked via a map file in their NPM registry

#334
post #84

They have an interesting regex for detecting negative sentiment in users prompt which is then logged (explicit content): https://github.com/chatgptprojects/claude-code/blob/642c7f94... I guess these words are to be avoided...

Everyone is commenting how this regex is actually a master optimization move by Anthropic When in reality this is just what their LLM coding agent came up with when some engineer told it to "log user frustration"

>Everyone is commenting how this regex is actually a master optimization move by Anthropic

No? I'd say not even 50% of the comments are positive right now.

Re: Claude Code's source code has been leaked via a map file in their NPM registry

#335
post #84

They have an interesting regex for detecting negative sentiment in users prompt which is then logged (explicit content): https://github.com/chatgptprojects/claude-code/blob/642c7f94... I guess these words are to be avoided...

An LLM company using regexes for sentiment analysis? That's like a truck company using horses to transport parts. Weird choice.

[deleted]

Re: Claude Code's source code has been leaked via a map file in their NPM registry

#336
post #84

They have an interesting regex for detecting negative sentiment in users prompt which is then logged (explicit content): https://github.com/chatgptprojects/claude-code/blob/642c7f94... I guess these words are to be avoided...

Curiously "clanker" is not on the list

Re: Claude Code's source code has been leaked via a map file in their NPM registry

#337
/*

* Check if 1M context is disabled via environment variable.

* Used by C4E admins to disable 1M context for HIPAA compliance.

*/ export function is1mContextDisabled(): boolean {

  return 
isEnvTruthy(process.env.CLAUDE_CODE_DISABLE_1M_CONTEXT)

}

Interesting, how is that relevant to HIPAA compliance?

Re: Claude Code's source code has been leaked via a map file in their NPM registry

#340
post #199
post #185

Earlier quoted context omitted.

Because they actually want it to work 100% of the time and cost nothing.

Then they made it wrong. For example, "What the actual fuck?" is not getting flagged, neither is "What the *fuck*".

They evidently ran a statistical analysis and determined that virtually no one uses those phrases as a quick retort to a model's unsatisfying answer... so they don't need to optimize for them.
Post reply on HN