frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Kimi K3: Open Frontier Intelligence

https://www.kimi.com/blog/kimi-k3
1203•vincent_s•11h ago•748 comments

Microsoft Comic Chat is now open source

https://opensource.microsoft.com/blog/2026/07/16/microsoft-comic-chat-is-now-open-source/
553•jervant•10h ago•121 comments

LM Studio Bionic: the AI agent for open models

https://lmstudio.ai/blog/introducing-lm-studio-bionic
164•minimaxir•6h ago•64 comments

Decoy Font

https://www.mixfont.com/experiments/decoy-font
419•ray__•10h ago•100 comments

M 3.9 Experimental Explosion – 147 Km ENE of Ponce Inlet, Florida

https://earthquake.usgs.gov/earthquakes/eventpage/us7000t13l/executive
30•hnburnsy•1h ago•8 comments

$100 AI Music Video: Claude Fable 5 vs. GPT-5.6 Sol

https://www.tryai.dev/blog/ai-music-video-arena-claude-vs-gpt-5.6
143•hershyb_•6h ago•147 comments

The Little Book of Reinforcement Learning

https://github.com/alxndrTL/little-book-rl/
59•mustaphah•3h ago•10 comments

NotebookLM is now Gemini Notebook

https://blog.google/innovation-and-ai/products/gemini-notebook/notebooklm-gemini-notebook/
249•xnx•10h ago•127 comments

Solod: Go can be a better C

https://solod.dev
40•koeng•3d ago•12 comments

'Likweli': A new monkey species discovered in the Congo Basin

https://news.yale.edu/2026/07/15/meet-likweli-new-monkey-species-discovered-congo-basin
50•gmays•4h ago•6 comments

Mathematics of Data Science

https://arxiv.org/abs/2607.11938
100•Anon84•5h ago•3 comments

Detecting LLM-Generated Texts with “Classical” Machine Learning

https://blog.lyc8503.net/en/post/llm-classifier/
162•uneven9434•9h ago•107 comments

Helium escaping from atmosphere of nearby rocky exoplanet in a habitable zone

https://www.science.org/doi/10.1126/science.aea9708
69•anyonecancode•6h ago•17 comments

Ring-Zero: Scaling Zero RL to a Trillion Parameters for Emergent Reasoning

https://arxiv.org/abs/2607.12395
37•binyu•4h ago•13 comments

Simulating everything, sort of: The promise and limits of world models

https://arstechnica.com/ai/2026/07/simulating-everything-sort-of-the-promise-and-limits-of-world-...
6•LorenDB•3d ago•1 comments

Immersive Linear Algebra Book with Interactive Figures (2015)

https://immersivemath.com/ila/
174•srean•10h ago•26 comments

How Our Rust-to-Zig Rewrite Is Going

https://rtfeldman.com/rust-to-zig
415•jorangreef•14h ago•228 comments

Show HN: Mojibake – A low-level Unicode library written in C

https://mojibake.zaerl.com/
39•program•3h ago•6 comments

Show HN: Clx – Compile Lua to Native Executables Through C++20

https://github.com/samyeyo/clx
88•_samt_•5d ago•4 comments

The Human-in-the-Loop Is Tired

https://pydantic.dev/articles/the-human-in-the-loop-is-tired
10•haritha1313•2h ago•4 comments

CVE-2026-25089: FortiSandbox unauthenticated command injection added to CISA KEV

https://hellorecon.com/blog/cve-2026-25089
23•slvnx•4h ago•0 comments

The privacy problems hidden in your period tracker

https://www.bbc.com/future/article/20260715-how-period-trackers-share-womens-private-details
74•tchalla•6h ago•42 comments

Abstracting Effects with Continuations

https://crowdhailer.me/2026-07-15/abstracting-effects-with-continuations/
37•crowdhailer•15h ago•0 comments

Launch HN: Traceforce (YC S26) – Company-wide security monitoring for AI apps

38•XiaHua•9h ago•17 comments

Adaptional (YC S25) Is Hiring

https://www.ycombinator.com/companies/adaptional/jobs
1•acesohc•9h ago

Pseudpocalypse

https://dynomight.net/pseudpocalypse/
81•surprisetalk•2d ago•49 comments

How to Train a Gen AI Kick Drum Model on Your Old Linux Desktop with 6GB VRAM

https://www.zhinit.dev/blog/training-a-kick-drum-diffusion-model
100•zhinit•11h ago•55 comments

Goes-19 weather satellite enters Safe Hold mode

https://www.spaceweather.gov/news/goes-19-safe-hold
150•yabones•12h ago•75 comments

Lingbot-map: A 3D foundation model for reconstructing scenes from streaming data

https://github.com/Robbyant/lingbot-map
5•olalonde•2h ago•0 comments

CD sales growth outpaced vinyl in the first half of 2026

https://consequence.net/2026/07/the-cd-revival-is-getting-hard-to-ignore/
63•speckx•9h ago•75 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?