frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Ghostty is leaving GitHub

https://mitchellh.com/writing/ghostty-leaving-github
2224•WadeGrimridge•11h ago•668 comments

Bugs Rust won't catch

https://corrode.dev/blog/bugs-rust-wont-catch/
148•lwhsiao•4h ago•50 comments

How ChatGPT serves ads

https://www.buchodi.com/how-chatgpt-serves-ads-heres-the-full-attribution-loop/
258•lmbbuchodi•6h ago•161 comments

Before GitHub

https://lucumr.pocoo.org/2026/4/28/before-github/
385•mlex•9h ago•116 comments

Show HN: Auto-Architecture: Karpathy's Loop, pointed at a CPU

https://github.com/FeSens/auto-arch-tournament/blob/main/docs/auto-arch-tournament-blog-post.md
88•fesens•13h ago•19 comments

Withnail's Coat and I

https://ontherow.substack.com/p/withnails-coat-and-i
18•apollinaire•1d ago•0 comments

OpenAI models coming to Amazon Bedrock: Interview with OpenAI and AWS CEOs

https://stratechery.com/2026/an-interview-with-openai-ceo-sam-altman-and-aws-ceo-matt-garman-abou...
227•translocator•11h ago•79 comments

We still don't have a more precise value for "Big G"

https://arstechnica.com/science/2026/04/we-still-dont-have-a-more-precise-value-for-big-g/
33•rbanffy•1d ago•15 comments

Regression: malware reminder on every read still causes subagent refusals

https://github.com/anthropics/claude-code/issues/49363
194•thomashobohm•6h ago•86 comments

Apple CMF (Color-Matching Functions) 2026

https://www.lttlabs.com/articles/2026/04/11/apple-studio-display-xdr-display-testing-results
43•HeyMeco•7h ago•1 comments

I won a championship that doesn't exist

https://ron.stoner.com/How_I_Won_a_Championship_That_Doesnt_Exist/
125•SEJeff•10h ago•71 comments

GitHub RCE Vulnerability: CVE-2026-3854 Breakdown

https://www.wiz.io/blog/github-rce-vulnerability-cve-2026-3854
308•bo0tzz•14h ago•73 comments

Behavioral timescale synaptic plasticity rewires the brain after an experience

https://www.quantamagazine.org/a-new-type-of-neuroplasticity-rewires-the-brain-after-a-single-exp...
86•ibobev•1d ago•1 comments

Intel Arc Pro B70 Review

https://www.pugetsystems.com/labs/articles/intel-arc-pro-b70-review/
139•zdw•5d ago•82 comments

Who owns the code Claude Code wrote?

https://legallayer.substack.com/p/who-owns-the-claude-code-wrote
339•senaevren•19h ago•342 comments

When the Internet Was a Place

https://www.frontporchrepublic.com/2025/09/when-the-internet-was-a-place/
31•herbertl•5h ago•4 comments

Your phone is about to stop being yours

https://keepandroidopen.org/en/
1228•doener•15h ago•569 comments

Gallium oxide electronics withstand extreme cold

https://discovery.kaust.edu.sa/en/article/26858/gallium-oxide-electronics-withstand-extreme-cold/
9•giuliomagnifico•1d ago•0 comments

Nonlinearity Affects a Pendulum

https://www.johndcook.com/blog/2026/04/24/nonlinear-pendulum/
25•ibobev•1d ago•4 comments

Warp is now open-source

https://www.warp.dev/blog/warp-is-now-open-source
223•meetpateltech•14h ago•65 comments

Talkie: a 13B vintage language model from 1930

https://talkie-lm.com/introducing-talkie
664•jekude•1d ago•272 comments

We decreased our LLM costs with Opus

https://www.mendral.com/blog/frontier-model-lower-costs
80•shad42•5h ago•26 comments

Show HN: Drive any macOS app in the background without stealing the cursor

https://github.com/trycua/cua
88•frabonacci•14h ago•26 comments

Localsend: An open-source cross-platform alternative to AirDrop

https://github.com/localsend/localsend
790•bilsbie•18h ago•240 comments

Claude for Creative Work

https://www.anthropic.com/news/claude-for-creative-work
104•elsewhen•7h ago•77 comments

CJIT: C, Just in Time

https://dyne.org/cjit/
109•smartmic•11h ago•29 comments

I have officially retired from Emacs

https://nullprogram.com/blog/2026/04/26/
201•Fudgel•3d ago•144 comments

An update on GitHub availability

https://github.blog/news-insights/company-news/an-update-on-github-availability/
353•salkahfi•20h ago•225 comments

UAE to leave OPEC

https://www.ft.com/content/8c354f2d-3e66-47f1-aad4-9b4aa30e386d
392•bazzmt•17h ago•531 comments

VibeVoice: Open-source frontier voice AI

https://github.com/microsoft/VibeVoice
346•tosh•18h ago•169 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?