frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Abdominal fat predicts heart disease risk better than BMI

https://www.acc.org/about-acc/press-releases/2026/08/11/14/59/abdominal-fat-predicts-heart-diseas...
65•theanonymousone•1h ago•39 comments

Engineers will do anything to avoid learning from history

https://horn.gg/blog/engineers-will-do-anything-to-avoid-learning-from-history/
46•madrox•1h ago•19 comments

Semaglutide linked to lower predicted dementia risk

https://alz-journals.onlinelibrary.wiley.com/doi/10.1002/dad2.70432
312•randycupertino•7h ago•209 comments

Bede Liu, a digital signal processing pioneer, has died

https://spectrum.ieee.org/digital-signal-processing
23•Jimmc414•1h ago•1 comments

Cultivating a state of mind where new ideas are born (2023)

https://www.henrikkarlsson.xyz/p/good-ideas
48•felixbraun•2h ago•17 comments

AI has access to a vastly larger working memory than the human brain

https://davidepiffer.com/p/ai-isnt-outthinking-mathematicians
353•rzk•4h ago•308 comments

At-home test for infected ticks could improve Lyme Disease diagnosis

https://www.smithsonianmag.com/innovation/the-first-at-home-test-for-infected-ticks-could-improve...
193•gmays•9h ago•64 comments

Tracking down a Zsh history data loss bug

https://michael.stapelberg.ch/posts/2026-08-09-zsh-history-truncation-bug/
14•ingve•1h ago•0 comments

AI in drug discovery – what it is, where we stand and the path forward

https://www.science.org/content/blog-post/so-how-ai-drug-discovery-doing-really
59•AnodicElegy•3h ago•33 comments

RISC-V: They Should Have Known Better

https://dmitry.gr/?r=06.%20Thoughts&proj=12.%20RV
205•dmitrygr•1d ago•286 comments

Auto-research with codex: How I achieved a 232x Faster Kernel

https://sankalp.bearblog.dev/autoresearch/
376•tosh•12h ago•83 comments

Show HN: Live Claude Usage HUD for a $38 Thermalright Trofeo Vision LCD

https://github.com/christensen143/claude-trofeo-hud
10•christensen143•1h ago•1 comments

A spectre is haunting Unicode

https://www.dampfkraft.com/ghost-characters.html
147•sensanaty•8h ago•44 comments

SugarTrack – an offline Android logbook for blood sugar (no account, no cloud)

https://sugartrack-beta.vercel.app/
4•hunzaboy•40m ago•1 comments

Voltair (YC W26) Is Hiring a Test Flight Engineer

https://www.ycombinator.com/companies/voltair/jobs/sSOD2Ox-flight-test-engineer
1•wweissbluth•4h ago

The Government Is Monitoring Anti-Flock TikTok and Instagram Accounts

https://www.404media.co/the-government-is-monitoring-anti-flock-tiktok-and-instagram-accounts/
18•Jimmc414•28m ago•2 comments

Modeling and Verification of Keeta's Consensus [pdf]

https://xescu.re/keeta-consensus.pdf
6•xescure•1h ago•1 comments

The Wow signal was a strong narrowband radio signal detected on August 15, 1977

https://en.wikipedia.org/wiki/Wow!_signal
38•firefax•1h ago•6 comments

Tess's Android Wayland Compositor

https://github.com/wmww/tawc
28•schmorptron•4h ago•1 comments

Working with AI feels more like leadership than coding

https://allen.bargi.org/notes/working-with-ai-feels-like-leadership/
241•allenb•12h ago•166 comments

Humazon

https://hughhowey.com/humazon/
12•herbertl•2h ago•5 comments

Geek Fighter – 2d fighter game

https://geek-fighter.vercel.app/
44•tareqismail•5d ago•21 comments

2D Gaussian Splatting for Bézier Spline Line Art Vectorization

https://studios.disneyresearch.com/2026/07/16/2d-gaussian-splatting-for-bezier-spline-line-art-ve...
54•Jimmc414•22h ago•4 comments

Jaithon 3, a fast programming language with the perfect syntax

https://github.com/abhiramasonny/jaithon
5•AbhiramaVS•3d ago•5 comments

BriskDB

https://github.com/schapman1974/briskdb
40•schapman1974•5h ago•10 comments

Pizza Box Project Stack

https://cblgh.org/posts/2026-07-31-pizza-box-project-stack/
22•surprisetalk•4d ago•3 comments

An image can overflow

https://master.dev/blog/something-nobody-told-you-about-the-image-element-it-can-overflow/
9•ibobev•4d ago•3 comments

Show HN: Eigendrum - Draw any shape and hear what it sounds like as a drum

https://baselashraf81.github.io/eigendrum/
191•BaselAshraf81•5d ago•91 comments

Super El Niño Keeps Growing as New Forecasts Reach Record Territory Ahead Winter

https://www.severe-weather.eu/long-range-2/super-el-nino-growth-accelerating-to-record-strength-f...
19•dgellow•3h ago•3 comments

The mathematical beauty of hyperbezier curves

https://linebender.org/blog/hyperbezier/
177•raphlinus•5d ago•31 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?