Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. When did Google get so weird? (sancho.bearblog.dev)
    146comments
  2. Ember-1 (fireworks.ai)
    132comments
  3. Alan Kay's answer to "Did the ENIAC have a BIOS"? (quora.com)
    16comments
  4. Lunar Terminator Paradox (secretsauce.net)
    —discuss
  5. Show HN: Lofi Cities – Pixel-art city nights with browser-generated lofi (loficities.com)
    33comments
  6. The state of SIMD in Rust in 2026 (shnatsel.github.io)
    12comments
  7. In an $80 motel room, a discovery to shed light on the origins of life (nytimes.com)
    67comments
  8. Imp is a full port of DSPy to the BEAM (github.com/deepfates)
    4comments
  9. What I did at Recurse Center (thill.me)
    6comments
  10. Oral history of John Chowning, inventor of FM synthesis [video] (youtube.com)
    5comments
  11. Don't couple your Go code to GitHub (iain.rocks)
    37comments
  12. There is more to code review than (automatable) detection (adaptivecapacitylabs.com)
    1comments
  13. Writing Efficient C++ Code (2013) (asawicki.info)
    73comments
  14. Replacing the old battery on rechargeable bike lights (jvns.ca)
    59comments
  15. Show HN: TinyAIArena watch AI agents battle it out (tinyaiarena.com)
    36comments
  16. Fragment of oldest known peace treaty found in Turkey (livescience.com)
    6comments
  17. The Cartesian Hand: In-Hand Manipulation with All-Linear Fingers (generalroboticslab.com)
    7comments
  18. The Normalization of Inexplicable Failures (ihatethefuture.com)
    85comments
  19. Previously unheard recordings of John Coltrane, captured by Frank Tiberi (jazzwise.com)
    9comments
  20. Flip Fluid on Flip Dots (mitxela.com)
    22comments
  21. Fakecloud: Local AWS cloud emulator for integration tests (fakecloud.dev)
    46comments
  22. Faster prompt lookup drafting in llama.cpp (jadidbourbaki.github.io)
    9comments
  23. KICKI: a DECsystem1060 (icm.museum)
    2comments
  24. On caring for user data: NeoVim caused Vim undo files to be deleted (aresluna.org)
    284comments
  25. Video CDs Break Windows Explorer (clydesnotes.blogspot.com)
    27comments
  26. Wiki Deep dive into Standard diving dress (wikipedia.org)
    1comments
  27. Allegations of US interference in Quebec election (globalnews.ca)
    9comments
  28. Improving site performance by shipping more CSS (github.blog)
    60comments
  29. C's Flexible Integer Sizes Were Not a Design Mistake (pikuma.com)
    101comments
  30. Go Concurrency Distilled (antonz.org)
    166comments

Faster prompt lookup drafting in llama.cpp

54 pointsby 1d agojadidbourbaki.github.io
9 comments
18h agoHN ↗

Btw, if anyone has experience with the open source community in general and llama.cpp in specific, I would greatly appreciate some advice. I’m facing a bit of an interpersonal issue that I really hope is resolved without any ill will. Here is the context:

https://www.reddit.com/r/LocalLLaMA/comments/1wr5ylm/comment...

Any advice for what I can do? Due to this, I cannot create a PR or issue in the llama.cpp repository. However, I am worried about bothering the maintainers on other channels in case it aggravates them further. Thank you for your help!

2h agoHN ↗

hopefully someone on the team sees this and fixes the situation, otherwise, if it's good, i'm sure somebody else will open the PR. thanks for your contribution.

1h agoHN ↗

I understand this repository must be under siege effectively with how popular it is, but the team needs to come up with a decent way to handle this. The current climate with Nvidia buying Hugging Face who effectively owns the llama.cpp team there’s a lot of discourse around their control of the team that’s negative.

1h agoHN ↗

Just hard fork the project. Frankly, llama.cpp is so badly written that these kind of speedups are trivial, and a hard fork (or a total rewrite) has been needed for the longest time.

19m agoHN ↗

Any advice for what I can do?

Email that author (email can usually be found via GitHub, or contact via other private way they've shared somewhere) and explain the situation, don't lambast them publicly on social media or similar ways. If that doesn't work, do the same but for another maintainer. Don't spam all of them straight up, wait a week or something before contacting someone else.

1h agoHN ↗

So, instead of resolving it privately like you were asked, you come here and complain? Was the bot posts on Reddit not enough for you? Pro tip: There is a right way and a wrong way to approach these things and you are MOST certainly approaching this the wrong way. And before you go accusing me of anything: I am NOT associated with that project, but I DID see what happened. You are acting like a damned child and should be ashamed of yourself.

1h agoHN ↗

Is there some missing context here? Where was the author asked to resolve issues in private? And what 'private' channels would be available to them?