frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Toyota, Nissan, and Honda to standardize parts to lower costs

https://www.caranddriver.com/news/a74490092/toyota-nissan-honda-standardize-parts-lower-costs/
491•zdw•6h ago•292 comments

Pill to treat pancreatic cancer hailed as 'biggest breakthrough in decades'

https://www.theguardian.com/society/2026/nov/20/pill-pancreatic-cancer-breakthrough-daraxonrasib
1004•rafaelc•1d ago•218 comments

Lean verification of the Riemann Hypothesis

https://leanprover-community.github.io/blog/posts/riemann-hypothesis/
1035•g-b-r•19h ago•860 comments

Show HN: The Riemann Proof Handbook

https://github.com/tamnd/riemann-handbook
48•tamnd•4h ago•17 comments

Sandwich Simulator

https://stulle.app/
245•subdomain•10h ago•83 comments

Inkling-2-Mini in 5.4 GB Memory

https://github.com/ShinMegamiBoson/lookatmyquant
463•k__•16h ago•117 comments

Data Processing Incidents on Inference Providers

https://openrouter.ai/blog/announcements/data-processing-incidents-on-inference-providers/
148•sdko•8h ago•57 comments

Notes on the discrete Fourier transform (DFT)

https://eli.thegreenplace.net/2026/notes-on-the-discrete-fourier-transform-dft/
29•kouosi•3h ago•4 comments

Detonating a pile of lead azide

https://www.science.org/content/blog-post/detonating-huge-pile-lead-azide-really
612•beginning_end•21h ago•387 comments

If tiny 'primordial' black holes exist

https://phys.org/news/2026-11-tiny-primordial-black-holes.html
34•wglb•2d ago•2 comments

Getting the mind to steer the body to steer you

https://notnottalmud.substack.com/p/getting-the-mind-to-steer-the-body
277•jger15•1d ago•92 comments

My monitor was cutting my download speed by 75%

https://blog.tymscar.com/posts/studiodisplayethernet/
589•soheilpro•23h ago•274 comments

PcapAnalyzer – self-hosted pcap analyzer with 27 problem detectors

https://github.com/sebaandrada-cell/PcapAnalyzer
118•sebaandrada•12h ago•14 comments

Is 'fork' missing operation in sandboxes?

https://avrea.com/blog/avrea-sandboxes-computers-should-be-forkable
6•damezumari•2d ago•5 comments

The Mythology of Conscious AI

https://www.noemamag.com/the-mythology-of-conscious-ai/
67•Anon84•8h ago•129 comments

A real Linux kernel, compiled to WebAssembly

https://github.com/pithings/unkernel
3•DonAtimator•4d ago•0 comments

Fast-Anything: Don't rewrite it in Rust. Rewrite the 5% that's slow

https://github.com/EL4CTEO/fast-anything
31•BaselAshraf81•6h ago•21 comments

Reversing the Next-Page Prefetcher in Skylake-X

https://devsh0.github.io/microarchitecture,/intel,/computer-architecture/2026/11/17/reversing-the...
10•todsacerdoti•3d ago•0 comments

87% of the Anthropic power will come from gas and 11% from coal in 2028

https://betterdatacenterproject.com/2026/11/16/how-ai-is-powered-a-breakdown-of-byop-and-grid-power/
91•happosai•1h ago•103 comments

Split Radiance Cascades

https://www.jacktollenaar.top/articles/split-rc.html
34•ibobev•2d ago•0 comments

Pandex – Official European Law for AI Agents, over MCP

https://www.pandex.io
94•vasie•13h ago•21 comments

Advice for the next 100 Rust GUIs

https://linebender.org/blog/next-100-guis/
166•raphlinus•13h ago•66 comments

Upload2Shell (CVE-2026-125396)

https://pwn.ai/upload2shell
119•f311a•15h ago•57 comments

Show HN: Compile the same source for GPUs and CPUs

https://github.com/ThrudTheBarbarian/xc
13•spacedcowboy•1w ago•1 comments

LLMs can read and write executables byte by byte from a hex dump

https://sgiannopoulos.github.io/blog/machine-code-programming/
245•fortran77•3d ago•158 comments

GnuPG Security Advisory for GPGME

https://lists.gnupg.org/pipermail/gnupg-announce/2026q4/000517.html
254•gdgghhhhh•1d ago•101 comments

Hurried Announcement: Alessandro Masullo GRH

https://math216.wordpress.com/2026/11/20/hurried-announcement-alessandro-masullo-grh/
2420•jasondavies•1d ago•1175 comments

Reaktiv Workbook – A spreadsheet where every cell is Python

https://workbook.bui.app/
20•buibuibui•3d ago•3 comments

Pion Interceptor: WebRTC for Hackers

https://pion.ly/blog/pion-interceptor-webrtc-for-hackers/
13•Sean-Der•3d ago•1 comments

Tasklet (YC P26) Is Hiring Product and Agent Infra Engineers

https://tasklet.ai/careers
1•mayop100•13h ago
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?