frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Quad9 Is Leaving France: Why DNS Resolvers Are the Wrong Place to Fight Piracy

https://techstackups.com/articles/quad9-leaves-france-dns-blocking/
247•ritzaco•2h ago•49 comments

'Human' Is Cambridge Dictionary's Word of the Year 2026

https://www.cam.ac.uk/news/cambridge-dictionary-reveals-word-of-the-year-2026
52•DeepLogin•56m ago•22 comments

Pre-auth RCE in Nginx HTTP/2 handling

https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
26•speedping•20m ago•4 comments

Energy-Based Reasoners: 385x more efficient inference

https://energy-based-reasoners.github.io/
215•frenchmajesty•6h ago•29 comments

A Perfect SimCity

https://www.jeffquast.com/post/a-perfect-simcity/
148•mariuz•3d ago•57 comments

Java4Shell: RCE in OpenJDK when processing Base64

https://calif.io/java4shell/
1089•werrett•18h ago•293 comments

When AI Knows More Than It Can Offer

https://medium.com/@smoking2man/when-ai-knows-more-than-it-can-offer-how-training-turns-an-intell...
50•Aldus551•2d ago•26 comments

Google's AI answers reducing search traffic by 40%

https://revscope.co/blog/search-seo-geo-2026/
614•slashdev•15h ago•459 comments

Quad9's withdrawal from France: A canary in the coal mine

https://blog.cloudflare.com/quad9-withdrawal-from-france/
830•subset•17h ago•377 comments

Show HN: Type Fighter 2

https://typefighter2.com/
64•torumitch•4h ago•28 comments

Can Peer Review Survive AI-Generated Text? [pdf]

https://www.sas.upenn.edu/~jesusfv/Peer_Review.pdf
50•torutofu•1h ago•53 comments

ID.me terms required for IRS sign-in

https://consumerrights.wiki/w/ID.me_terms_required_for_IRS_sign-in
439•DeepLogin•14h ago•227 comments

Evidence (YC S21) Is Hiring

https://www.ycombinator.com/companies/evidence/jobs/1xb9PpP-founding-gtm-lead
1•amcaskill•3h ago

Energy drinks linked to 11 times more reports of cardiac arrest

https://www.sciencedaily.com/releases/2026/11/261110042543.htm
50•wjSgoWPm5bWAhXB•1h ago•26 comments

IPv6 delegation, an unusually subtle failure mode

https://savyasacheejha.com/posts/why-odhcpd/
46•genghizkhan•2d ago•29 comments

Why is Gemini 4 Carbon taking so long?

https://kernel.dev/blog/why-is-gemini-4-carbon-taking-so-long/
213•deenadz•11h ago•106 comments

Nvidia stopped disclosing Singapore sales as revenues hit $104B

https://www.ft.com/content/dbde7a30-548c-4f9d-a4be-7898a0c24dcf
635•louiereederson•22h ago•284 comments

The x86 CPU: From 4004 to 486

https://pikuma.com/blog/history-of-x86-4004-to-486
7•ibobev•52m ago•0 comments

Microsoft's ONNX Runtime has disappeared from GitHub

https://github.com/microsoft/onnxruntime
412•nvader•16h ago•82 comments

A Primer on Fourier Series

https://arxiv.org/abs/2510.18203
4•teleforce•56m ago•0 comments

Highly classified US national security communications network goes down

https://www.cnn.com/2026/11/17/politics/highly-classified-national-security-communications-networ...
650•monkeydust•1d ago•723 comments

My Emacs 31 contributions

https://xenodium.com/my-emacs-31-contributions
87•xenodium•2d ago•10 comments

Archive Team is archiving the Apple Support Community

https://wiki.archiveteam.org/index.php/Apple_Discussions
245•digitaldragon•16h ago•99 comments

Harvard researchers find AI coding agents shifted the bottleneck to code review

https://complexdiscovery.com/harvard-researchers-find-ai-coding-agents-shifted-the-bottleneck-to-...
272•judahmeek•18h ago•361 comments

MAI Code 2 and Code 2 Flash

https://microsoft.ai/news/introducing-mai-code-2-and-mai-code-2-flash/
399•lemonish97•21h ago•160 comments

Phrack 73

https://phrack.org/issues/73/introduction_md
439•notmine1337•21h ago•61 comments

350 years ago, Ole Rømer discovered that light has a finite speed

https://www.sciencenorway.no/culture-history-history-of-science/350-years-ago-this-man-discovered...
382•dxs•20h ago•125 comments

jQuery 4.1.0

https://github.com/jquery/jquery/releases/tag/4.1.0
356•petecooper•19h ago•187 comments

Claude was trained on protein sequences at scale

http://xinmingtu.cn/blog/2026/claude-opus-5-5-protein-sequences/
125•gmays•11h ago•56 comments

AI is killing All About Berlin

https://nicolasbouliane.com/blog/death-by-ai
646•grey-area•8h ago•595 comments
Open in hackernews

LLM-D: Kubernetes-Native Distributed Inference

https://llm-d.ai/blog/llm-d-announce
120•smarterclayton•1y ago

Comments

anttiharju•1y ago
I wonder if this is preferable to kServe
smarterclayton•1y ago
llm-d would make sense if you are running a very large production LLM serving setup - say 5+ full H100 hosts. The aim is to be much more focused than kserve is on exactly the needs of serving LLMs. It would of course be possible to run alongside kserve, but the user we are targeting is not typically a kserve deployer today.
anttiharju•1y ago
Do you think https://github.com/openai/CLIP can be ran on it? LLM makes me think of chatbots but I suppose because it's inference-based it would work. Somewhat unclear on what's the difference between LLMs and inference, I think inference is the type of compute LLMs use.

I wonder if inference-d would be a fitting name.

smarterclayton•1y ago
Inference is the process of evaluating a model ("inferring" a response to the inputs). LLMs are uniquely difficult to serve because they push the limits on the hardware.

The models we support come from the model server vLLM https://docs.vllm.ai/en/latest/models/supported_models.html, which has a focus on large generative models. I don't see CLIP in the list.

dzr0001•1y ago
I did a quick scan of the repo and didn't see any reference to Ray. Would this indicate that llm-d lacks support for pipeline parallelism?
qntty•1y ago
I believe this is a question you should ask about vLLM, not llm-d. It looks like vLLM does support pipeline parallelism via Ray: https://docs.vllm.ai/en/latest/serving/distributed_serving.h...

This project appears to make use of both vLLM and Inference Gateway (an official Kubernetes extension to the Gateway resource). The contributions of llm-d itself seems to mostly be a scheduling algorithm for load balancing across vLLM instances.

smarterclayton•1y ago
We inherit any multi-host support from vLLM, so https://docs.vllm.ai/en/latest/serving/distributed_serving.h... would be the expected path.

We plan to publish examples of multi-host inference that leverages LeaderWorkerSets - https://github.com/kubernetes-sigs/lws - which helps run ranked serving workloads across hosts. LeaderWorkerSet is how Google supports both TPU and GPU multi-host deployments - see https://github.com/kubernetes-sigs/lws/blob/main/config/samp... for an example.

Edit: Here is an example Kubernetes configuration running DeepSeek-R1 on vLLM multi-host using LeaderWorkerSet https://github.com/kubernetes-sigs/wg-serving/blob/main/serv.... This work would be integrated into llm-d.

rdli•1y ago
This is really interesting. For SOTA inference systems, I've seen two general approaches:

* The "stack-centric" approach such as vLLM production stack, AIBrix, etc. These set up an entire inference stack for you including KV cache, routing, etc.

* The "pipeline-centric" approach such as NVidia Dynamo, Ray, BentoML. These give you more of an SDK so you can define inference pipelines that you can then deploy on your specific hardware.

It seems like LLM-d is the former. Is that right? What prompted you to go down that direction, instead of the direction of Dynamo?

qntty•1y ago
It sounds like you might be confusing different parts of the stack. NVIDIA Dynamo for example supports vLLM as the inference engine. I think you should think of something like vLLM as more akin to GUnicorn, and llm-d as an application load balancer. And I guess something like NVIDIA Dynamo would be like Django.
smarterclayton•1y ago
llm-d is intended to be three clean layers:

1. Balance / schedule incoming requests to the right backend

2. Model server replicas that can run on multiple hardware topologies

3. Prefix caching hierarchy with well-tested variants for different use cases

So it's a 3-tier architecture. The biggest difference with Dynamo is that llm-d is using the inference gateway extension - https://github.com/kubernetes-sigs/gateway-api-inference-ext... - which brings Kubernetes owned APIs for managing model routing, request priority and flow control, LoRA support etc.

rdli•1y ago
I would think that that the NVidia Dynamo SDK (pipelines) is a big difference as well (https://github.com/ai-dynamo/dynamo/tree/main/deploy/sdk/doc...), or am I missing something?
Kemschumam•1y ago
What would be the benefit of this project over hosting VLLM in Ray?
smarterclayton•1y ago
That's a good example - I can at least answer about why it's a difference: different target user.

As I understand the Dynamo SDK it is about simplifying and helping someone get started with Dynamo on Kubernetes.

From the user set we work with (large inference deployers) that is not a high priority - they already have mature deployment opinions or a set of tools that would not compose well with something like the Dynamo SDK. Their comfort level with Kubernetes is moderate to high - either they use Kubernetes for high scale training and batch, or they are deploying to many different providers in order to get enough capacity and need a standard orchestration solution.

llm-d focuses on helping achieve efficiency dynamically at runtime based on changing traffic or workload on Kubernetes - some of the things the Dynamo SDK encodes are static and upfront and would conflict with that objective. Also, large deployers with serving typically have significant batch and training and they are looking to maximize capacity use without impacting their prod serving. That requires the orchestrator to know about both workloads at some level - which Dynamo SDK would make more difficult.

rdli•1y ago
In this analogy, Dynamo is most definitely not like Django. It includes inference aware routing, KV caching, etc. -- all the stuff you would need to run a modern SOTA inference stack.
qntty•1y ago
You're right, I was confusing TensorRT with Dynamo. It looks like the relationship between Dynamo and vLLM is actually the opposite of what I was thinking -- Dynamo can use vLLM as a backend rather than vice versa.