frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

AI financial advice is surprisingly good if you ask the right questions

https://mitsloan.mit.edu/ideas-made-to-matter/ai-financial-advice-surprisingly-good-especially-if...
61•foxtrot8672•1h ago•40 comments

Diátaxis

https://diataxis.fr/
126•ryanseys•3h ago•20 comments

Seedance 2.5

https://seed.bytedance.com/en/blog/one-take-creation-flexible-referencing-introducing-seedance-2-5
83•njaremko•2h ago•28 comments

Stop fucking around with database commits and transactions

https://www.droppedasbaby.com/posts/db-commits/
9•offbyone42•20m ago•1 comments

Postmortem for Kernel Soundness Bug #14576

https://leodemoura.github.io/blog/2026-8-1-postmortem-for-kernel-soundness-bug-14576/
104•juhopitk•5h ago•37 comments

Unraveling the mysteries of habit formation

https://www.kyoto-u.ac.jp/en/research-news/2026-07-28
8•hhs•44m ago•5 comments

But can your calculator run Linux?

https://raymii.org/s/articles/But_can_your_calculator_run_Linux.html
48•jandeboevrie•3h ago•3 comments

Morph (YC S23) Is Hiring Member of Technical Stuff

https://www.ycombinator.com/companies/morph/jobs/0Z8vI3K-member-of-technical-staff
1•bhaktatejas922•47m ago

CISA Alert: Water Sector PLC Targeting

https://censys.com/blog/cisa-alert-water-tower-plc-targeting/
49•speckx•4h ago•33 comments

The Art of 64-bit Assembly

https://nostarch.com/art-64-bit-assembly-v2
171•0x54MUR41•9h ago•81 comments

How Google helped destroy adoption of RSS feeds (2023)

https://openrss.org/blog/how-google-helped-destroy-adoption-of-rss-feeds
337•pudgywalsh•5h ago•109 comments

Just because a game is on disc doesn't mean it will work in the future

https://arstechnica.com/gaming/2026/07/the-disc-is-not-the-game-physical-releases-increasingly-re...
80•rbanffy•1d ago•66 comments

Nyctography: A substituton cypher by Lewis Carroll

https://en.wikipedia.org/wiki/Nyctography
42•nanna•4d ago•3 comments

NetBSD 11.0

https://blog.netbsd.org/tnf/entry/netbsd_11_0_released
192•jaypatelani•5h ago•81 comments

RipGrep musl binaries occasionally segfault during very-large searches

https://github.com/BurntSushi/ripgrep/issues/3494
241•throwaway2037•11h ago•162 comments

Beltrunner: Game Design Postmortem

https://blog.gingerbeardman.com/2026/07/30/beltrunner-game-design-postmortem/
8•tobr•1d ago•3 comments

Explorative modeling: Train on the best of K guesses

https://alexiglad.github.io/blog/2026/explorative_modeling/
75•DSemba•8h ago•21 comments

Glyphs 4 – the leading Mac font editor

https://glyphsapp.com
43•microflash•4d ago•8 comments

Pgtestdb's template cloning approach to testing is fast

https://brandur.org/fragments/pgtestdb
60•brandur•7h ago•36 comments

Kenji/Serious Eats – 30-Min Pressure Cooker Pho Ga

https://www.seriouseats.com/30-minute-pressure-cooker-pho-ga-recipe
71•stasomatic•7h ago•52 comments

Kaisel – Routes as Values. Dart 3 Native Router for Flutter

https://kaisel.dev/
49•TheWiggles•6h ago•7 comments

Show HN: Legionlinuxtui – Control Lenovo legion laptops in the terminal

https://github.com/nooneknowspeter/legionlinuxtui
4•nooneknowspeter•2d ago•0 comments

Linux on ESP32

https://github.com/GrieferPig/esp32-s31-linux
91•boveyking•4d ago•33 comments

A Surveillance Treaty in Disguise: Canada Signs UN Cybercrime Convention

https://www.michaelgeist.ca/2026/07/a-surveillance-treaty-in-disguise-the-trouble-with-canadas-qu...
253•iamnothere•9h ago•137 comments

RamenHaus

https://ramen.haus/
216•oler•14h ago•105 comments

Cursor removed cost information from the usage page and CSV export

https://forum.cursor.com/t/usage-page-to-token-amount-what/167153
291•EugeneOZ•8h ago•125 comments

The Burau representation of the braid group is faithful for n = 4

https://arxiv.org/abs/2607.05283
40•wglb•4d ago•18 comments

Flint: A Visualization Language for the AI Era

https://microsoft.github.io/flint-chart/
246•vinhnx•20h ago•66 comments

Anime User Interfaces

https://animeuserinterface.tumblr.com
13•akyuu•52m ago•1 comments

Register deprivation: spills and runtime under forced register scarcity

https://rjp.io/blog/2026-07-19-register-deprivation
23•surprisetalk•2d ago•4 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?