frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Motorola GrapheneOS devices will be bootloader unlockable/relockable

https://grapheneos.social/@GrapheneOS/116160393783585567
575•pabs3•7h ago•157 comments

RFC 9849. TLS Encrypted Client Hello

https://www.rfc-editor.org/rfc/rfc9849.html
33•P_qRs•1h ago•3 comments

Agentic Engineering Patterns

https://simonwillison.net/guides/agentic-engineering-patterns/
94•r4um•3h ago•15 comments

Better JIT for Postgres

https://github.com/vladich/pg_jitter
38•vladich•2h ago•7 comments

TikTok will not introduce end-to-end encryption, saying it makes users less safe

https://www.bbc.com/news/articles/cly2m5e5ke4o
214•1659447091•7h ago•145 comments

A CPU that runs entirely on GPU

https://github.com/robertcprice/nCPU
68•cypres•4h ago•23 comments

MacBook Pro with M5 Pro and M5 Max

https://www.apple.com/newsroom/2026/03/apple-introduces-macbook-pro-with-all-new-m5-pro-and-m5-max/
773•scrlk•18h ago•799 comments

Graphics Programming Resources

https://develop--gpvm-website.netlify.app/resources/
84•abetusk•6h ago•10 comments

Weave – A language aware merge algorithm based on entities

https://github.com/Ataraxy-Labs/weave
117•rs545837•7h ago•67 comments

On the Design of Programming Languages (1974) [pdf]

https://web.cs.ucdavis.edu/~su/teaching/ecs240-w17/readings/PLHistoryGoodDesign.PDF
33•jruohonen•2d ago•1 comments

Claude's Cycles [pdf]

https://www-cs-faculty.stanford.edu/~knuth/papers/claude-cycles.pdf
617•fs123•21h ago•248 comments

Speculative Speculative Decoding (SSD)

https://arxiv.org/abs/2603.03251
40•E-Reverance•5h ago•6 comments

Show HN: Rust compiler in PHP emitting x86-64 executables

https://github.com/mrconter1/rustc-php
17•mrconter11•2d ago•17 comments

Reverse-Engineering the Wetware: Spiking Networks and the End of Matrix Math

https://metaduck.com/reverse-engineering-the-wetware-spiking-networks-td-errors-and-the-end-of-ma...
17•pgte•2d ago•4 comments

Voxile: A ray-traced game made in its own engine and programming language

https://elbowgreasegames.substack.com/p/voxray-games-pushes-major-update
186•spacemarine1•11h ago•50 comments

My spicy take on vibe coding for PMs

https://www.ddmckinnon.com/2026/02/11/my-%f0%9f%8c%b6-take-on-vibe-coding-for-pms/
84•dmckinno•9h ago•81 comments

Textadept

https://orbitalquark.github.io/textadept/
126•giancarlostoro•3d ago•21 comments

Mount Mayhem at Netflix: Scaling Containers on Modern CPUs

https://netflixtechblog.com/mount-mayhem-at-netflix-scaling-containers-on-modern-cpus-f3b09b68beac
49•vquemener•3d ago•24 comments

You can use newline characters in URLs

https://lemire.me/blog/2026/02/28/you-can-use-newline-characters-in-urls/
66•chmaynard•3d ago•32 comments

Welcoming Elizabeth Barron as the New Executive Director of the PHP Foundation

https://thephp.foundation/blog/2026/02/27/welcoming-elizabeth-barron-new-executive-director/
26•ulrischa•2d ago•12 comments

Indefinite Book Club Hiatus

https://whatever.scalzi.com/2026/03/03/indefinite-book-club-hiatus/
11•cdrnsf•4h ago•4 comments

When AI writes the software, who verifies it?

https://leodemoura.github.io/blog/2026/02/28/when-ai-writes-the-worlds-software.html
219•todsacerdoti•16h ago•222 comments

Circle Games (2019)

https://srconstantin.wordpress.com/2019/06/06/circle-games/
6•surprisetalk•2d ago•0 comments

An Interactive Intro to CRDTs (2023)

https://jakelazaroff.com/words/an-interactive-intro-to-crdts/
138•evakhoury•13h ago•23 comments

The largest acidic geyser has been putting on quite a show

https://www.usgs.gov/observatories/yvo/news/echinus-geyser-back-action-now
48•1659447091•7h ago•1 comments

Launch HN: Cekura (YC F24) – Testing and monitoring for voice and chat AI agents

81•atarus•18h ago•20 comments

Number Research Inc

https://numberresearch.xyz/
31•eieio•6h ago•16 comments

California's Digital Age Assurance Act, and FOSS

https://runxiyu.org/comp/ab1043/
93•todsacerdoti•5h ago•72 comments

GPT‑5.3 Instant

https://openai.com/index/gpt-5-3-instant/
342•meetpateltech•14h ago•266 comments

Mac external displays for designers and developers, part 2 (2022)

https://bjango.com/articles/macexternaldisplays2/
41•fragmede•6h ago•24 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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