frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Google Plans to Invest Up to $40B in Anthropic

https://www.bloomberg.com/news/articles/2026-04-24/google-plans-to-invest-up-to-40-billion-in-ant...
162•elffjs•6h ago•244 comments

My audio interface has SSH enabled by default

https://hhh.hn/rodecaster-duo-fw/
110•hhh•3h ago•19 comments

Iliad fragment found in Roman-era mummy

https://www.thehistoryblog.com/archives/75877
60•wise_blood•2d ago•4 comments

The Classic American Diner

https://blogs.loc.gov/picturethis/2026/04/the-classic-american-diner/
116•NaOH•3h ago•58 comments

Sabotaging projects by overthinking, scope creep, and structural diffing

https://kevinlynagh.com/newsletter/2026_04_overthinking/
336•alcazar•8h ago•82 comments

Show HN: I've built a nice home server OS

https://lightwhale.asklandd.dk/
21•Zta77•1h ago•6 comments

Tell HN: Claude 4.7 is ignoring stop hooks

51•LatencyKills•3h ago•39 comments

FusionCore: ROS 2 sensor fusion (IMU and GPS and encoders)

https://github.com/manankharwar/fusioncore
5•kharwarm•20m ago•0 comments

Google Flow Music

https://www.flowmusic.app/
27•hmokiguess•1h ago•14 comments

Work with the garage door up

https://notes.andymatuschak.org/Work_with_the_garage_door_up
84•jxmorris12•3d ago•73 comments

There Will Be a Scientific Theory of Deep Learning

https://arxiv.org/abs/2604.21691
81•jamie-simon•4h ago•23 comments

Diatec, known for its mechanical keyboard brand FILCO, has ceased operations

https://gigazine.net/gsc_news/en/20260424-filco-diatec/
80•gslin•6h ago•23 comments

How to be anti-social – a guide to incoherent and isolating social experiences

https://nate.leaflet.pub/3mk4xkaxobc2p
283•calcifer•12h ago•277 comments

Email could have been X.400 times better

https://buttondown.com/blog/x400-vs-smtp-email
99•maguay•1d ago•90 comments

SFO Quiet Airport (2025)

https://viewfromthewing.com/san-francisco-airport-removed-90-minutes-of-daily-noise-travelers-say...
109•CaliforniaKarl•4h ago•57 comments

Spinel: Ruby AOT Native Compiler

https://github.com/matz/spinel
294•dluan•14h ago•80 comments

I cancelled Claude: Token issues, declining quality, and poor support

https://nickyreinert.de/en/2026/2026-04-24-claude-critics/
723•y42•6h ago•425 comments

MacBook Neo and how the iPad should be

https://craigmod.com/essays/ipad_neo/
169•jen729w•1d ago•98 comments

CC-Canary: Detect early signs of regressions in Claude Code

https://github.com/delta-hq/cc-canary
30•tejpalv•5h ago•16 comments

I'm done making desktop applications (2009)

https://www.kalzumeus.com/2009/09/05/desktop-aps-versus-web-apps/
132•claxo•7h ago•151 comments

OpenAI releases GPT-5.5 and GPT-5.5 Pro in the API

https://developers.openai.com/api/docs/changelog
178•arabicalories•4h ago•106 comments

SDL Now Supports DOS

https://github.com/libsdl-org/SDL/pull/15377
202•Jayschwa•6h ago•71 comments

TIPSv2: Advancing Vision-Language Pretraining with Enhanced Patch-Text Alignment

https://gdm-tipsv2.github.io/
15•gmays•3h ago•1 comments

DeepSeek v4

https://api-docs.deepseek.com/
1768•impact_sy•19h ago•1362 comments

Different Language Models Learn Similar Number Representations

https://arxiv.org/abs/2604.20817
86•Anon84•8h ago•35 comments

CSS as a Query Language

https://evdc.me/blog/css-query
51•evnc•5h ago•16 comments

Show HN: Browser Harness – Gives LLM freedom to complete any browser task

https://github.com/browser-use/browser-harness
66•gregpr07•8h ago•28 comments

Physicists revive 1990s laser concept to propose a next-generation atomic clock

https://phys.org/news/2026-04-physicists-revive-1990s-laser-concept.html
48•wglb•22h ago•7 comments

Redesigning the Recurse Center application to inspire curious programmers

https://www.recurse.com/blog/192-redesigning-the-recurse-center-application
50•nicholasjbs•6h ago•9 comments

ML supports existence of unrecognized transient astronomical phenomena

https://arxiv.org/abs/2604.18799
60•solarist•8h ago•48 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•11mo ago

Comments

balloob•11mo 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•11mo ago
Discussion for the other article in the series:

https://news.ycombinator.com/item?id=44011381

tomhow•11mo ago
Comments moved thither. Thanks!
pabs3•11mo ago
They are two different articles, I don't think that was correct.
tomhow•11mo 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•11mo ago
Thanks for the response, guess that makes sense.
pabs3•11mo 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?