Live data from Hacker News

Kimi-K3 Technical Report [pdf]

github.com

111–120 of 199 posts

Re: Kimi-K3 Technical Report [pdf]

#111

Earlier quoted context omitted.

the longer i read this comment the wronger it gets

Don't make me add more of my thoughts to the comment, I can still edit it. Deeply fun "care about improving people's lives" quote on your user page :p

how is 2025 two years ago? GPT-120b is not even close to the biggest recent American release, etc. etc.

Re: Kimi-K3 Technical Report [pdf]

#112

It's funny that we've finally returned to tanh activation functions, time is a circle.

From the paper (page 6 with a comparison to GLU and SwiGLU) they are not using tanh directly (i.e. f(x) = tanh(x)) but:

    f_gate(b,x) = b * tanh(x / b) * sigmoid(x)

    f_up(b,x) = b * tanh(x / b)
Looking at the graph I wonder if this is to try and get the best of both GLU (better representation at higher values of x >~ 5) and SwiGLU (the value bump just before 0).

Re: Kimi-K3 Technical Report [pdf]

#113
post #112

It's funny that we've finally returned to tanh activation functions, time is a circle.

From the paper (page 6 with a comparison to GLU and SwiGLU) they are not using tanh directly (i.e. f(x) = tanh(x)) but: f_gate(b,x) = b * tanh(x / b) * sigmoid(x) f_up(b,x) = b * tanh(x / b) Looking at the graph I wonder if this is to try and get the best of both GLU (better representation at higher values of x >~ 5) and SwiGLU (the value bump just before 0).

Still more of a tanh than I've seen in years

Re: Kimi-K3 Technical Report [pdf]

#114
post #86

Earlier quoted context omitted.

I think the licensing that would likely apply to a company that's able to afford ~$6M rack and the associated infrastructure muddies this somewhat

I think internal use is allowed at any scale in the license? > 4. The requirements set forth in Sections 2 and 3 do not apply to: (a) internal use of the Software, defined as any use that does not make the Software, its outputs, or its underlying capabilities available to third parties; [...]

It's very hard to make sure none of the outputs are ever made available to third parties. Source code can end up widely distributed (e.g. client-side js, open source). Prose will frequently get shared across organization boundaries (e.g. emails, websites, documents).

Re: Kimi-K3 Technical Report [pdf]

#115
post #67
post #5

Also open sourced a bunch of infra to go with it. Anyone who claims open source and open weights models are "decel" needs to get their head checked https://github.com/MoonshotAI/MoonEP https://github.com/kvcache-ai/AgentEnv https://github.com/MoonshotAI/FlashKDA

To me its clear that it is decel the only reason other labs can catch up is because the frontier labs can be distilled, and they siphon a % of the labs' revenue to reinvest into the next iteration full accel would mean nationalizing the big 2 labs and locking in manhattan project style until RSI (Edit: some great counterpoints in the replies. my view has definitely been changed!)

OpenAI's head of strategic futures publicly stated that you can't explain the quality of the newest Kimi via distillation.

Further, you can just read the papers released alongside most open models. Plenty of hugely influential research results published that drive the frontier forward. It's not like these models are just existing architectures downloaded from Huggingface and trained on frontier lab APIs.

Re: Kimi-K3 Technical Report [pdf]

#116

License: https://huggingface.co/moonshotai/Kimi-K3/blob/main/LICENSE > If the Licensee or any of its affiliates operates a Model as a Service business, and the aggregate revenue of the Licensee and its affiliates exceeds 20 million US dollars (or the equivalent in other currencies) in total over any consecutive 12 months, the Licensee must enter into a separate agreement with Moonshot AI before using the Software or…

I wonder how they'll figure out who to target for litigation when this license is violated.

They have certainly trained in some secret call/response pairs that would uniquely identify Kimi serving.

Re: Kimi-K3 Technical Report [pdf]

#117
post #99
post #20

Can someone explain what are teachers in Multi-Teacher On-Policy Distillation? I can imagine math, coding and other verifiable domains, but they also have biology? Is it where distillation from bigger models come in?

They reference https://thinkingmachines.ai/blog/on-policy-distillation/ If I understand correctly, it's distillation via having a teacher model score each of the student's tokens for a problem based on their own probabilities of generating that token at each step in the sequence. The reward/loss is then applied as RL. The multi-teacher bit seems to imply they're distilling from multiple models. It's light on the deta…

It's not that light on the details. I read the paper and they train several different models in parallel over a few different domains and then they distill from their own models to get the final model.

Re: Kimi-K3 Technical Report [pdf]

#118
post #50

Earlier quoted context omitted.

This comment would be much better without the second line

I know it's a hard ask on this site, but I need you to start parsing content and not tone. It was a helpful bit of context, even if it was a bit vitriolic.

It depends on if we expect posters to be informative and include nuance.

Re: Kimi-K3 Technical Report [pdf]

#119

License: https://huggingface.co/moonshotai/Kimi-K3/blob/main/LICENSE > If the Licensee or any of its affiliates operates a Model as a Service business, and the aggregate revenue of the Licensee and its affiliates exceeds 20 million US dollars (or the equivalent in other currencies) in total over any consecutive 12 months, the Licensee must enter into a separate agreement with Moonshot AI before using the Software or…

It's worth noting that the weights of machine learning models are not subject to copyright in the United States as they are the product of an automated optimization process (e.g., stochastic gradient descent, expectation maximization, genetic algorithms) rather than human authorship. Granted, this has yet to be fully tested in court and going to court is expensive, so it's likely that your employer would prefer to err on the side of caution and respect such attempts at model licensing anyway. Nonetheless, this was partially tested last year in Thaler v. Perlmutter which affirmed that copyright requires human authorship, reading the Copyright Act's provisions on ownership, duration, and transferability as presupposing a human author[1].

If you want to assess the position of the U.S. Copyright Office for yourself, the relevant text can be found in the Compendium of U.S. Copyright Office Practices § 313.2, "Works That Lack Human Authorship"[2], which states:

> […] the Copyright Act protects “original works of authorship.” 17 U.S.C. § 102(a) (emphasis added). To qualify as a work of “authorship” a work must be created by a human being. See Burrow-Giles Lithographic Co., 111 U.S. at 58. Works that do not satisfy this requirement are not copyrightable.

> […] the Office will not register works produced by a machine or mere mechanical process that operates randomly or automatically without any creative input or intervention from a human author. The crucial question is “whether the ‘work’ is basically one of human authorship, with the computer [or other device] merely being an assisting instrument, or whether the traditional elements of authorship in the work (literary, artistic, or musical expression or elements of selection, arrangement, etc.) were actually conceived and executed not by man but by a machine.” U.S. COPYRIGHT OFFICE, REPORT TO THE LIBRARIAN OF CONGRESS BY THE REGISTER OF COPYRIGHTS 5 (1965).

Oh, and there's also a bit in the following Section 313.3, "Works That Do Not Constitute Copyrightable Subject Matter"[2], which explicitly excludes mathematical principles, formulas, algorithms, and equations, along with DNA sequences and other genetic or chemical compounds, regardless of whether they are produced by humans or by nature. If one takes the perspective that machine learning models are algorithms, the conclusions on copyrightability are pretty clear.

[1] https://media.cadc.uscourts.gov/opinions/docs/2025/03/23-523...

[2] https://www.copyright.gov/comp3/chap300/ch300-copyrightable-...

Re: Kimi-K3 Technical Report [pdf]

#120
post #104

Earlier quoted context omitted.

Yes but zero is not enough and where do you get a fraction of a competent dev op from?

From the other dev-op work you’re doing.

Understood but sharing your existing devops resources with this will soon become a bottleneck especially when any major downtime will keep several engineers (and long-running agents) blocked from any meaningful work until availability improves.
Post reply on HN