frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

F-Droid 2.0

https://f-droid.org/2026/09/24/f-droid-2.0-a-new-chapter-for-android-freedom.html
1007•daveoc64•12h ago•275 comments

Show HN: Make cursed fonts like Times New Bastard

https://bastardica.mitpit.com
525•MitPitt•1d ago•76 comments

Show HN: Whiteboard (YC W26) – An open-source IDE for thoughtful software design

https://github.com/devdotfast/whiteboard
227•sidharthkmenon•10h ago•85 comments

Why is the liver so weirdly regenerative?

https://dynomight.substack.com/p/liver
300•jbotz•11h ago•165 comments

2DWillNeverDie

https://2dwillneverdie.com/
143•surprisetalk•2d ago•14 comments

Fearless SIMD v1.0

https://linebender.org/blog/fearless-simd-1-0/
205•verdagon•2d ago•32 comments

Rails World 2026 Opening Keynote [video]

https://www.youtube.com/watch?v=vDjW_dRyKXY
270•an0malous•1d ago•284 comments

Toyota is taking the Corolla electric

https://electrek.co/2026/09/23/toyota-best-selling-corolla-electric/
256•cisc•1d ago•426 comments

Using LLMs to trace alchemical knowledge and decode 17th century letters

https://resobscura.substack.com/p/ai-labs-need-to-start-funding-historical
93•benbreen•8h ago•14 comments

My weird new hobby: Wandering around Tokyo on Google Maps

https://ahmedhossamdev.com/writing/my-weird-new-hobby-wandering-around-tokyo/
250•ahmedhossamdev•2d ago•106 comments

Writing Parquet files using Haskell

https://www.datahaskell.org/blog/2026/09/18/writing-parquet-files-using-haskell.html
32•cosmic_quanta•2d ago•3 comments

Google’s Project Suncatcher to put ML infrastructure in space

https://blog.google/innovation-and-ai/models-and-research/google-research/google-project-suncatch...
137•xnx•13h ago•244 comments

Two-tier encryption in the UK

https://macanorak.com/two-tier-encryption-in-the-uk/
394•ReturnoftheHack•17h ago•380 comments

The Bayeux Tapestry: Woven by the Victors

https://www.historytoday.com/archive/out-margins/bayeux-tapestry-woven-victors
16•prismatic•1d ago•0 comments

The Board Game of the Alpha Nerds (2014)

https://grantland.com/features/diplomacy-the-board-game-of-the-alpha-nerds/
64•neonate•6h ago•25 comments

Book review: Is parallel programming hard, and, if so, what can you do about it?

https://ahelwer.ca/post/2026-09-21-concurrency-textbook/
100•ahelwer•3d ago•30 comments

California is chasing wealth that has feet

https://blog.landeconomics.org/p/california-is-chasing-wealth-that
166•idbnstra•7h ago•467 comments

Show HN: Air-gapped file encryption as self-decrypting HTML page

https://cms-sfx-demo.apeleg.com/
43•emurlin•20h ago•14 comments

Show HN: Koi.rest – watch some fish and regain your balance

https://koi.rest
144•hxii•6h ago•38 comments

Sourcehut account takeover via build logs (XSS in ansi2html)

https://blog.arusekk.pl/posts/srht-account-takeover/
87•arusekk•7h ago•12 comments

Opus 5.5 is good at explainer videos

https://launchvideo.io
159•iacguy•7h ago•97 comments

Security auditing in the age of (good enough) AI

https://blog.trailofbits.com/2026/09/18/auditing-in-the-age-of-good-enough-ai/
76•aray07•3d ago•8 comments

Stable (YC W20) Is Hiring Product Engineers

https://www.usestable.com/careers/product-engineer
1•collinpham•9h ago

The forgotten battle of East Lansing

https://eastlansinginfo.news/the-forgotten-battle-of-east-lansing/
88•rmason•3d ago•14 comments

Forging 1024-bit RSA signatures in nearly SNFS time [pdf]

https://eprint.iacr.org/2026/2131.pdf
56•int0x29•13h ago•9 comments

Geothermal heat map of US hot springs

https://www.soakingsprings.com/hot-springs/geothermal-map
94•armenarmen•1d ago•37 comments

WaveDigger: Dig into wireless signals to discover their physical locations

https://github.com/christianrowlands/wavedigger
97•882542F3884314B•1d ago•19 comments

Tutoring company tells parents to save their money and 'use AI instead'

https://www.afr.com/policy/health-and-education/tutoring-company-tell-parents-to-save-their-money...
90•theanonymousone•12h ago•154 comments

Motor Characterization for Small Running Robots (2016)

https://robot-daycare.com/posts/2016-01-06-motor-characterization-for-small-running-robots/
32•loughnane•3d ago•1 comments

Nokia Design Archive (2025)

https://repo.aalto.fi/index.php?name=SO_b66a9391-dcf8-4399-8e87-611f84c3fc4c
211•pillars•17h ago•118 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?