Live data from Hacker News

Viewing profile — ekojs

ekojs

HN member
Joined
Tue, Oct 04, 2022, 8:35 AM UTC
HN karma
186
Public activity
49 items

About ekojs

No profile information was provided.

Recent public activity

  1. comment
    Comment #48936044

    I copied that from https://platform.kimi.ai/docs/guide/kimi-k3-quickstart but it seems they updated the page to remove the benchmark score now.

  2. comment
    Comment #48935992

    Yeah, bad wording it seems. Though a charitable interpretation is that Fable 5 and GPT 5.6 Sol are joint 1st place in the measurement.

  3. comment
    Comment #48935831

    > In our evaluations, Kimi K3 delivers frontier-level performance. Among the models tested, its overall intelligence ranks second only to Claude Fable 5 and GPT-5.6 Sol. For the co…

  4. comment
    Comment #48197450

    Seems like the only good thing about 3.5 Flash is its speed. Not cost-competitive or benchmark-leading by any means.

  5. comment
    Comment #48169604

    Not disagreeing with your argument, but: > If you want a good dense model, use qwen3.6 27B instead, speed will be up, and if you don't take my word for it being smarter, take openr…

  6. comment
    Comment #48059655

    > HTTP is just not a good transport for streaming LLM tokens and for building async agentic applications I don't know if I agree if this is a problem with SSE or HTTP. Something li…

  7. comment
    Comment #47865572

    > You cannot run these models at 8-bit on a 32GB card because you need space for context You probably can actually. Not saying that it would be ideal but it can fit entirely in VRA…

  8. comment
    Comment #47865464

    Yeah, figure the 'nearly lossless' claim is the most controversial thing. But in my defense, ~97% recovery in benchmarks is what I consider 'nearly lossless'. When quantized with c…

  9. comment
    Comment #47865281

    Not at all, I actually run ~30B dense models for production and have tested out 5090/3090 for that. There are gotchas of course, but the speed/quality claims should be roughly ther…

  10. comment
    Comment #47865195

    As this is a dense model and it's pretty sizable, 4-bit quantization can be nearly lossless. With that, you can run this on a 3090/4090/5090. You can probably even go FP8 with 5090…

  11. story
  12. story
  13. comment
    Comment #45012504

    Seems pretty widespread. We got mistakenly charged for ~$800 over the weekend. Other Sources: [0]: https://aistudio.google.com/status [1]: https://www.reddit.com/r/GeminiAI/comment…

  14. story
  15. comment
    Comment #44637877

    > Btw as an aside, we didn’t announce on Friday because we respected the IMO Board's original request that all AI labs share their results only after the official results had been …

  16. comment
    Comment #44595532

    Maybe not a popular sentiment here on HN but I cancelled my Kagi subscription (9+ months) just recently. Increasingly, most of my queries/search have been through LLMs and Google s…

  17. comment
    Comment #44261594

    https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1S... > Multiple GCP products are experiencing impact due to Identity and Access Management Service Issue IAM issue huh. T…

  18. comment
    Comment #44261170

    Super duper frustrating having the status page being green. Why can't Google do this properly?

  19. comment
    Comment #44256118

    I share the sentiment. I think we will only be using Next.js for static sites/prebuilt SPA in the future.

  20. comment
    Comment #43623925

    I think it's most illustrative to see the sample battles (H2H) that LMArena released [1]. The outputs of Meta's model is too verbose and too 'yappy' IMO. And looking at the verdict…

  21. comment
    Comment #43473644

    > This will mark the first experimental model with higher rate limits + billing. Excited for this to land and for folks to really put the model through the paces! From https://x.co…

  22. comment
    Comment #43417256

    > The bottleneck then becomes how to self-host the finetuned model in a way that's cost-effective and scalable It's not actually that expensive and hard. For narrow usecases, you c…

  23. comment
    Comment #43306968

    Normally, yes. But there's a couple rendering modes with these frameworks. In this case, the rendering is most likely 'hybrid'. Some routes are statically pre-rendered, some are se…

  24. comment
    Comment #43306524

    Interesting. My hunch is that Next.js is not optimized for the dockerized Node server deployment. I would say that you could get much greater prerendering performance from Next.js …

  25. comment
    Comment #43197977

    > Because of this, we’re evaluating whether to continue serving it in the API long-term as we balance supporting current capabilities with building future models. Seems like it's n…