frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Scientists reverse brain aging, with a nasal spray

https://stories.tamu.edu/news/2026/04/14/scientists-reverse-brain-aging-with-a-nasal-spray/
135•cybermango•2h ago•48 comments

Command and Conquer Generals natively ported to macOS, iPhone, iPad using Fable

https://github.com/ammaarreshi/Generals-Mac-iOS-iPad/tree/main
359•asronline•6h ago•142 comments

GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance

https://github.com/openai/codex/issues/30364
149•maille•4h ago•45 comments

Google Books (or similar) all book scans – $200k bounty (2025)

https://software.annas-archive.gl/AnnaArchivist/annas-archive/-/work_items/234
343•Cider9986•9h ago•178 comments

Jellyfish can heal wounds in minutes. Scientists want their secrets

https://www.mbl.edu/news/jellyfish-can-heal-wounds-minutes-scientists-want-their-secrets
37•hhs•3h ago•7 comments

Leaking YouTube creators' private videos

https://javoriuski.com/post/youtube
487•javxfps•9h ago•274 comments

Better Models: Worse Tools

https://lucumr.pocoo.org/2026/7/4/better-models-worse-tools/
92•leemoore•5h ago•31 comments

Explanation of everything you can see in htop/top on Linux (2019)

https://peteris.rocks/blog/htop/
397•theanonymousone•14h ago•52 comments

Potential session/cache leakage between workspace instances or consumer accounts

https://github.com/anthropics/claude-code/issues/74066
273•chatmasta•12h ago•128 comments

Zig: All Package Management Functionality Moved from Compiler to Build System

https://ziglang.org/devlog/2026/#2026-06-30
140•tosh•9h ago•27 comments

Verizon is About to Break our Watches

https://www.jefftk.com/p/verizon-is-about-to-break-our-watches
141•jefftk•8h ago•81 comments

Return of the Nigerian Prince Redux: Beware Book Club and Book Review Scams

https://writerbeware.blog/2025/09/19/return-of-the-nigerian-prince-redux-beware-book-club-and-boo...
12•Anon84•1h ago•4 comments

Reflections on the Guillotine

https://theanarchistlibrary.org/library/albert-camus-reflections-on-the-guillotine
19•halperter•2h ago•2 comments

Meta's Un-Stable Signature

https://hackerfactor.com/blog/index.php?/archives/1098-Metas-Un-Stable-Signature.html
13•ementally•3d ago•0 comments

Can you build a recognizable World Map in under 500 bytes?

https://www.experimentlog.com/blog/building-a-world-map-with-only-500-bytes
23•iweczek•3d ago•27 comments

Drone Physics

https://iahmed.me/post/drone-physics/
84•wrxd•4d ago•25 comments

Egg consumption inversely correlated with Alzheimer's

https://pubmed.ncbi.nlm.nih.gov/42002260/
30•natbennett•1h ago•9 comments

Drone Autonomy Crash Course

https://www.cggonzalez.com/blog/index.html
7•cgg1•2h ago•0 comments

Protocol Prying: Vulnerability Research in AirDrop and Quick Share

https://arxiv.org/abs/2606.26967
13•logickkk1•5h ago•1 comments

It's not me, it's the compiler

https://parsa.wtf/cast/
60•SVI•3d ago•11 comments

Windows CE Dreamcast Community Edition (wince-dc)

https://github.com/maximqaxd/wince-dc
93•msephton•11h ago•17 comments

The Vespa at 80

https://www.cbc.ca/news/world/vespa-italy-postwar-design-9.7252641
146•cf100clunk•3d ago•135 comments

Mapping with In-Memory Layers to Reduce LLM Overload

https://ridgetext.com/blog/mapbox-llm-composition
7•Buckwheat469•2h ago•0 comments

Fable created novel 4D splat format

https://adamraudonis.github.io/splats4D/
116•adamraudonis•10h ago•43 comments

BareMetal RAM Dumper – Bare-metal x86 tool for Cold Boot Attack experiments

https://github.com/pIat0n/BareMetal-RAM-Dumper
56•liffik•8h ago•39 comments

CloudsLinker: Move and sync files across 50 cloud services

https://app.cloudslinker.com/login
6•janandonly•2d ago•1 comments

Curveball

https://mightyburger.net/projects/curveball/
51•toilet•9h ago•11 comments

Neural Render Proxies for Interactive and Differentiable Lighting

https://studios.disneyresearch.com/2026/07/01/neural-render-proxies-for-interactive-and-different...
51•tobr•3d ago•8 comments

My AI-built PHP engine in Rust passes 17% of PHP-src tests, renders WordPress

https://ekinertac.com/blog/i-dont-know-rust-my-ai-is-rewriting-php-in-it/
24•ekinertac•4h ago•31 comments

Breaking the Bird Barrier: Scientist Decodes Zebra Finch Language

https://www.freepressjournal.in/education/breaking-the-bird-barrier-scientist-decodes-zebra-finch...
102•yyyk•4d ago•35 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?