frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Asus Bike Booster

https://www.asus.com/accessories/bike-booster/asus-oxiis/oxiis-intelligent-bike-booster/
245•wiradikusuma•3d ago•132 comments

Asynchronous I/O in DuckDB: Work, Thread, Work

https://duckdb.org/2026/07/31/asynchronous-io
92•pdet•5d ago•7 comments

The quirky personal homepages of programming language creators

https://breck.lol/plMakers.html
39•cjlm•1h ago•10 comments

Semaglutide linked to lower predicted dementia risk

https://alz-journals.onlinelibrary.wiley.com/doi/10.1002/dad2.70432
393•randycupertino•13h ago•274 comments

Patterns and problems in emerging multi-agent systems

https://www.anthropic.com/research/multiagent-systems
30•maxutility•3h ago•7 comments

Show HN: Mic Drop, a real-time multiplayer karaoke game

https://www.micdrop.gg/
41•johnsillings•4h ago•15 comments

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

https://www.henrikkarlsson.xyz/p/good-ideas
125•felixbraun•8h ago•31 comments

Guiding Ships with Moire Patterns

https://tinkerings.org/2018/03/28/guiding-ships-with-moire-patterns/
23•Eridanus2•4h ago•7 comments

Software Engineering fundamentals matter more

https://rhonabwy.com/2026/08/15/software-engineering-fundamentals-matter-more-than-ever/
60•ingve•7h ago•6 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...
244•gmays•15h ago•84 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
121•AnodicElegy•10h ago•61 comments

Numba in the Browser: Unlocking a New Scientific Python Stack in JupyterLite

https://notebook.link/blog/numba-in-the-browser/
18•xalfotis•3d ago•4 comments

Zapping Rocks Unlocks Stimulated Geologic Hydrogen

https://spectrum.ieee.org/stimulated-geologic-hydrogen
12•adm4•3h ago•3 comments

Tea5767-Radio-Tuner

https://github.com/turtushig22-blip/tea5767-radio-tuner
34•turtushig22•5h ago•1 comments

RISC-V: They Should Have Known Better

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

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...
214•theanonymousone•8h ago•157 comments

A fortuitous decade as an indie software developer

https://lapcatsoftware.com/articles/2026/8/3.html
59•frizlab•5d ago•9 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...
143•dgellow•10h ago•89 comments

Tracking down a Zsh history data loss bug

https://michael.stapelberg.ch/posts/2026-08-09-zsh-history-truncation-bug/
55•ingve•8h ago•18 comments

Program with Paint Brushes, Not Pencils

https://blog.pickcode.io/program-with-paint-brushes-not-pencils/
6•skadamat•4d ago•1 comments

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

https://davidepiffer.com/p/ai-isnt-outthinking-mathematicians
458•rzk•11h ago•396 comments

A spectre is haunting Unicode

https://www.dampfkraft.com/ghost-characters.html
202•sensanaty•15h ago•69 comments

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

https://sugartrack-beta.vercel.app/
35•hunzaboy•7h ago•10 comments

Show HN: Fixing optical computing jitter via fluid dynamics in GPU registers

https://github.com/PJHkorea/photonic-mesh-fng-router
3•PJHkorea•1w ago•2 comments

Show HN: Bribes.fyi – Compare bribes statistics department wise

https://bribes.fyi/compare
30•neverenderr•7h ago•13 comments

Targeted marine cloud brightening weakens subsequent El Niño

https://www.science.org/doi/10.1126/sciadv.adx3012
6•musha68k•2h ago•0 comments

Voltair (YC W26) Is Hiring a Test Flight Engineer

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

AI-Assisted GPU Porting of a 250k Line Legacy Weather Simulation Code

https://arxiv.org/abs/2608.13122
19•Jimmc414•7h ago•2 comments

ProofRun – a local verification receipt for AI coding agents

https://github.com/yebiguo/ProofRun
5•yebiguo•2h ago•0 comments

Tess's Android Wayland Compositor

https://github.com/wmww/tawc
59•schmorptron•11h ago•5 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?