frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Jensen Huang resigns

https://apnews.com/article/nvidia-megaspeed-china-singapore-huang-5403f152a601cf82ce939f1d24fffa0f
2948•lldb•11h ago•2787 comments

Rust 1.100

https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/
418•mbStavola•7h ago•171 comments

Gemini 4 Hydrogen and Orchestrator

https://antigravity.google/blog/gemini-4-hydrogen-in-google-antigravity/
301•jonbaer•6h ago•72 comments

Show HN: My $300 embroidery machine needed a subscription, so I built my own app

https://github.com/simpsoka/zigzag
336•simpsoka•8h ago•137 comments

Dwarf planet candidate appears which takes roughly 280 years to orbit our sun

https://www.smithsonianmag.com/smart-news/astronomers-found-a-mysterious-object-orbiting-far-beyo...
198•cybermango•6h ago•94 comments

AI is turning Apple's app review process into a nightmare for synth developers

https://synthanatomy.com/2026/11/ai-is-turning-apples-app-review-process-into-a-nightmare-for-dev...
95•anigbrowl•4h ago•80 comments

Foundation Models framework

https://developer.apple.com/foundation-models-framework/
126•kermatt•4h ago•16 comments

Service degradation on Microsoft 365

https://status.cloud.microsoft/
500•dkpk•7h ago•464 comments

Edge0-145B: Frontier AI Capabilities on Your Own Computer

https://edge0.ai/blog/introducing-edge0-145b-frontier-ai-capabilities-on-your-own-computer
36•sroussey•2h ago•12 comments

Turning a 22-year-old Postgres type-confusion primitive into RCE

https://mehmetince.net/part-3-6-how-i-ended-up-turning-a-22-year-old-postgresql-type-confusion-pr...
144•ozirus•7h ago•19 comments

I'm making LLMs work on small and old devices

https://github.com/hyperionaidev/smolmaxxing/
278•mrashad74•10h ago•95 comments

Abandoned Quake 4 expansion finished by modders and now playable

https://www.moddb.com/mods/openq4/downloads/openq4-0141-windows-x64
239•klaussilveira•11h ago•82 comments

Relax: JIT compiler for Rust to reduce build times

https://makepad.github.io/relax/
118•adamnemecek•1d ago•50 comments

Writing correct software is hard and math alone won’t help us (2016)

https://pron.github.io/posts/correctness-and-complexity
358•AriFordsham•15h ago•168 comments

Before Pixels: Speed-Minder

https://unsung.aresluna.org/before-pixels-speed-minder/
14•surprisetalk•1d ago•0 comments

Gemini 4 Hydrogen

https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-hydr...
463•dvaplima•7h ago•296 comments

Talking Zen 6 with Mike Clark at AMD In-Depth

https://chipsandcheese.com/p/talking-zen-6-with-mike-clark-at
187•dverlaeckt80•11h ago•2 comments

Chinese frontier AI models carry the fingerprint of export-controlled GPUs

https://unemploymentlabs.com/checkpoint-forensics
166•firloop•3h ago•46 comments

Anthropic IPO

https://ipo.anthropic.com/us/
819•josephljohnston•13h ago•805 comments

Announcement: Conductor Is Back

https://twitter.com/charlieholtz/status/2120973052024598620
7•jahala•5h ago•1 comments

Chicago schools to Google – we'd rather lose Search than be forced to accept AI

https://www.techspot.com/news/114532-chicago-schools-tell-google-they-can-live-without.html
19•thunderbong•1h ago•2 comments

Show HN: Kapso – Iterative learning from enterprise data

37•alirezamshi•7h ago•9 comments

Safety in Algae Home Experiments

https://chillphysicsenjoyer.substack.com/p/algae-safety-in-home-experiments
27•surprisetalk•2d ago•2 comments

Words of warning about radiocarbon dating medieval human bones

https://www.nature.com/articles/s40494-026-02958-x
55•gumby•1d ago•9 comments

Show HN: AgentRun – open-source, Self-improving Managed Agents

https://github.com/Parcha-ai/agentrun/blob/main/README.md
75•miguelrios•7h ago•16 comments

Distributed Ray Tracer

https://ray.hatchet.run
36•juliusgeo•6h ago•12 comments

Adapting CPython for Yk

https://tratt.net/laurie/blog/2026/adapting_cpython_for_yk.html
42•frostbyte7•12h ago•2 comments

Fortune Telling and Speculative Design

https://maggieappleton.com/fortune-telling
4•saikatsg•2d ago•0 comments

Our software engineering interviews are changing a little

https://blog.janestreet.com/software-engineering-interviews-are-changing-a-little/
170•maitland•11h ago•163 comments

ExcalidrawZ: Local Native Excalidraw on macOS/iOS

https://github.com/chocoford/ExcalidrawZ
107•Qision•10h ago•24 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?