frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

DeepSeek: DeepSeek v4.1 Flash 1017

https://openrouter.ai/deepseek/deepseek-v4.1-flash-1017
120•theanonymousone•1h ago•9 comments

"Tame" boar and deer are instinctively adapting to the wolf in the Netherlands

https://nos.nl/video/2635315-wildcamera-s-tonen-hoe-zwijnen-en-herten-zich-aanpassen-aan-de-wolf
20•felipevb•1h ago•20 comments

Ultramarine 1 Flash

https://www.paperinstruments.com/ultramarine
248•i_rush_carriers•1d ago•71 comments

Is MCP becoming the common foundation of smart, decentralised search?

https://contextetech.com/en/articles/mcp-protocol-smart-decentralised-search
10•contextetech•1h ago•3 comments

Tesla Roadster

https://www.tesla.com/roadster
1439•shekhar101•1d ago•2515 comments

Show HN: Llmspeed – feel how fast a local LLM runs before you buy the hardware

https://llmspeed.dev/
74•albinstman•5h ago•28 comments

DeepSeek-v4.1-Flash-1017

https://huggingface.co/deepseek-ai/DeepSeek-V4.1-Flash-1017
147•theykk•1h ago•61 comments

Intuitive concurrent programming in any language

https://www.lf-lang.org/
44•mpweiher•1d ago•7 comments

Tell HN: Remember to migrate away from .name domain

39•nikanj•2d ago•19 comments

Llama.cpp on a jailbroken PS5: run any GGUF model natively on the console

https://github.com/cobanov/PS5LM
290•Anon84•15h ago•72 comments

Recipes Are Moving from Maven Central to the Code Genome Project

https://docs.openrewrite.org/reference/latest-versions-of-every-openrewrite-module
6•javahippie•1d ago•1 comments

You could have invented transformers from memory

https://alexwang.ai/posts/associative-memory/
310•speckx•15h ago•72 comments

Claude reveals ECDSA curve origins

https://www.anthropic.com/research/ecdsa-curve-origins
875•ahlCVA•15h ago•325 comments

FLUX 3 Image Klein

https://bfl.ai/blog/flux-3-image-klein
166•gmays•14h ago•47 comments

0/1 Knapsack Problem in PyTorch

https://jedrzej.maczan.pl/2025_11_21_dp_knapsack_sliding_hirschberg
23•yu3zhou4•2d ago•1 comments

Apple ML Research: Muse Spark Open with MLX on Mac Studio

https://machinelearning.apple.com/research/mlx-distributed-inference
320•antipaul•20h ago•161 comments

eBay Restricts Listings of Radio Equipment, but Exempts Ham-Band-Only Gear

https://www.arrl.org/arrlletterissue?issue=2026-10-15#eBay-Restricts-Listings-of-Radio-Equipment_...
222•7402•16h ago•198 comments

Butlerian Jihad

https://dune.fandom.com/wiki/Butlerian_Jihad
230•wetwater•7h ago•124 comments

Designing more efficient quantum circuits with Claude

https://www.anthropic.com/research/designing-efficient-quantum-circuits
142•pretext•16h ago•32 comments

JPEG XL vs. AVIF for web use-cases

https://jakearchibald.com/2026/jpeg-xl-vs-avif/
262•farlight•18h ago•182 comments

I built the RealWorld app in Lean 4

https://leangineer.com/blog/realworld-in-lean/
58•saviorand•2d ago•5 comments

Flexport Is Hiring a Biz Ops Leader in Office of CEO

https://www.flexport.com/company/careers/
1•thedogeye•9h ago

Monte-Carlo Simulations

https://eli.thegreenplace.net/2026/monte-carlo-simulations/
121•ibobev•3d ago•22 comments

90% of US working hours are spent on tasks not covered well by AI benchmarks

https://www.mercor.com/research/labor-index/benchmark-map/
504•speckx•17h ago•427 comments

A story of WiFi secrets, UART lockdowns and a damaged flash memory chip

https://adepts.of0x.cc/eufy-homestation2-firmware/
44•michidk•18h ago•3 comments

Nine-Inch Snails

https://www.theatlantic.com/science/2026/10/giant-african-snails-florida-invasion/688850/
66•zdw•11h ago•33 comments

How the Claude Code team does code review

https://claude.dev/blog/solving-code-review-at-anthropic/
349•pretext•15h ago•329 comments

C++26: The New Debugging Header

https://www.sandordargo.com/blog/2026/09/30/cpp26-debugging
97•jandeboevrie•15h ago•23 comments

Wireless magnetic millirobots that deliver medicine inside the beating heart

https://hub.jhu.edu/2026/10/12/magnetic-millirobots-cardiac-treatment/
95•giuliomagnifico•3d ago•16 comments

Show HN: Gemini 4 Argon plays StarCraft

https://starskirmish.com/bench/v0-2/
222•__cayenne__•19h ago•101 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•1y ago

Comments

balloob•1y ago
Founder Home Assistant here. Want to chime in that I always love to see write ups like these to see the great things what people achieve with Home Assistant.

Not everyone might know, but last year we started the Open Home Foundation[1] as a non-profit in Switzerland and I donated Home Assistant to it[2]. It's fully funded by users. There are no investors involved.

We are fully committed to building out a smart home that focuses on local control and privacy. Yes there are rough edges, but we're actively working on it in the open, with progress being released every month.

~Paulus Founder Home Assistant & President Open Home Foundation https://github.com/balloob

[1]: https://www.openhomefoundation.org [2]: https://www.openhomefoundation.org/blog/announcing-the-open-...

pabs3•1y ago
Discussion for the other article in the series:

https://news.ycombinator.com/item?id=44011381

tomhow•1y ago
Comments moved thither. Thanks!
pabs3•1y ago
They are two different articles, I don't think that was correct.
tomhow•1y ago
The problem is we can’t have two closely-related threads (i.e., threads where there is significant subject/discussion overlap) active at once.

When that happens it just gets confusing, because it’s hard for people know which thread to comment in, if the comment they want to make is somewhere in the overlap. And then whichever one they choose to comment in, people who only see the other thread won’t see that comment. Then sometimes, anticipating this, people will copy and paste their comment in both threads (which happened in this case). But then each one gets different replies.

So each thread ends up being incomplete and duplicated all at once, and it all becomes a big confusing mess.

The fact that these two articles were by the same author, had the same title, were published just a week apart and could easily have been published as one, longer article, says to me that merging the threads was the right thing to do.

The other option would have been to bury the second thread and consider another thread about that second article a few months later, but that didn’t seem like the best option, given how much the two articles are so related and continuous.

Edit: Just thought I'd add that a major factor in deciding to merge the threads was this opening to the second part by the author:

The first article in this series provided an overview of Home Assistant, its community, and its capabilities. It was deliberately short on descriptions of interesting things that can be done with Home Assistant, though — the reasons why one might actually want to use this program. In this closing article, we'll look at how Home Assistant was used to solve some real problems.

To me it makes all the difference that the first part is introductory/high-level whilst the second part goes deeper into usage-scenarios. We'd treat it differently if each part went deeply into different aspects on the project.

pabs3•1y ago
Thanks for the response, guess that makes sense.
pabs3•1y ago
BTW, on lobste.rs, they can merge threads into one, and all the URLs are shown at the top. That might be a useful change to adopt for HN too?