frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

How to make almost anything

https://pub.cba.mit.edu/863.26/site/
155•o4c•2h ago•26 comments

Universal XSS in uBlock Origin from website-driven element picker

https://iter.ca/post/ubo-uxss/
301•zaik•5h ago•84 comments

Qwen4-Max

https://qwen.ai/blog?id=qwen4-max
417•ilreb•5h ago•153 comments

Old Bitly links are being hijacked

https://ransomnews.com/burger-king-tweet-bitly-link-hijack-2026/
261•hspeiser•9h ago•138 comments

What's Next for Nvidia?

https://steveblank.com/2026/11/15/whats-next-for-nvidia/
215•zdw•8h ago•283 comments

Tor Project Issues Rapid-Response DoS-Defense Fix Amid Sustained DDoS Attack

https://forum.torproject.org/t/security-release-0-4-9-17/22454
131•aillia•7h ago•30 comments

Stop Filming in Log

https://digitalfilms.wordpress.com/2026/11/15/stop-filming-in-log/
39•dabinat•3h ago•24 comments

Protomaps: Self-hosting map tiles has gotten cheap and easy

https://bruceroettgers.eu/blog/protomaps/
294•bcye•12h ago•54 comments

Preserving 30 years of Salon journalism

https://blog.archive.org/2026/11/12/preserving-30-years-of-salon-journalism/
138•CharlesW•9h ago•38 comments

A short explainer on how El Niño works [video]

https://www.youtube.com/watch?v=7_JF3etiAv8
225•nharada•13h ago•97 comments

Handwriting, as a Font

https://ductus.sorenblank.com
245•coinfused•12h ago•46 comments

Do we still have to denormalize? Have your schema and search it too

https://www.paradedb.com/blog/joins
65•philippemnoel•2d ago•8 comments

The Miracle Cure: In 1977, a drug rejected by doctors became a sensation

https://slate.com/technology/2026/11/doctor-medicine-cancer-cure-pill-history.html
45•mutexjp•3d ago•32 comments

The MacBook Pro's OLED PWM problem

https://macanorak.com/the-macbook-pros-oled-pwm-problem-when-a-better-display-becomes-worse-to-use/
472•MacAnorak•18h ago•259 comments

Crows make decisions faster than we can

https://www.nytimes.com/2026/11/15/science/birdbrain-crows-birds-research-decision.html
226•gumby•14h ago•151 comments

Claude Code and Codex reverse engineered my 1994 Jeep's ECU over a $3 Arduino [video]

https://www.youtube.com/watch?v=WPj3aQ-xxpI
422•envoked•4d ago•197 comments

Debian Becomes Unresponsive after 6.1.0-55 Kernel Update

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1154101
66•artooro•3h ago•12 comments

WebGL Flight Simulator with seed generated terrain

https://baron.by.dai.studio/
130•ranger_danger•11h ago•25 comments

Researchers track whole body movement with just a smartwatch

https://news.cornell.edu/stories/2026/11/researchers-track-whole-body-movement-just-smartwatch
3•PaulHoule•2d ago•0 comments

The Lasting Influence of John Berger

https://www.newyorker.com/magazine/2026/11/16/john-berger-a-life-tom-overton-book-review
6•prismatic•4d ago•0 comments

Simple 8085 Computer

https://www.hackster.io/mit41301/simple-8085-computer-9fe156
24•AlexeyBrin•3d ago•2 comments

Mini.nvim Is Now on Tangled

https://tangled.org/nvim-mini.org/mini.nvim
60•nerdypepper•8h ago•14 comments

Things That Turbo Pascal Is Smaller Than (2011)

https://prog21.dadgum.com/116.html
232•ksec•18h ago•125 comments

Artificial Intelligence for the Z80

https://www.dfsantos.com/en/libro-ia-z80
31•AlexeyBrin•2d ago•4 comments

Skydio's asymmetrical F10 Lightrunner solves a problem with fixed-wing drones

https://spectrum.ieee.org/skydio-f10-lightrunner-asymmetrical-drone
34•Gaishan•8h ago•2 comments

A quest to create the perfect whiskey glass

https://www.nytimes.com/2026/11/13/dining/drinks/kurt-josef-zalto-whiskey-glass.html
62•Kaibeezy•2d ago•63 comments

Microsoft 365 outage leads to chlorine gas poisoning of 15 hotel guests

https://www1.wdr.de/nrw/rheinland/rhein-erft-kreis/technischer-defekt-chlor-phantasialand-100.html
506•DeepLogin•13h ago•219 comments

Clice v1.0 Released: Welcome to Modern C++

https://ykiko.me/en/articles/2105384023094834022/
141•molenzwiebel•14h ago•78 comments

Eclipse Mosquitto – An open source MQTT broker

https://github.com/eclipse-mosquitto/mosquitto
88•gregsadetsky•13h ago•30 comments

Coles hit by a cybersecurity incident

https://www.colesgroup.com.au/updates/
95•sagunsh•6h ago•74 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.