frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Meta’s AI smart glasses and data privacy concerns

https://www.svd.se/a/K8nrV4/metas-ai-smart-glasses-and-data-privacy-concerns-workers-say-we-see-e...
1041•sandbach•10h ago•590 comments

Arm's Cortex X925: Reaching Desktop Performance

https://chipsandcheese.com/p/arms-cortex-x925-reaching-desktop
42•ingve•1h ago•1 comments

British Columbia is permanently adopting daylight time

https://www.cbc.ca/news/canada/british-columbia/b-c-adopting-year-round-daylight-time-9.7111657
782•ireflect•12h ago•391 comments

Ars Technica fires reporter after AI controversy involving fabricated quotes

https://futurism.com/artificial-intelligence/ars-technica-fires-reporter-ai-quotes
256•danso•7h ago•153 comments

Simple screw counter

https://mitxela.com/projects/screwcounter
121•jk_tech•2d ago•30 comments

I built a pint-sized Macintosh

https://www.jeffgeerling.com/blog/2026/pint-sized-macintosh-pico-micro-mac/
24•ingve•1h ago•6 comments

Show HN: I built a sub-500ms latency voice agent from scratch

https://www.ntik.me/posts/voice-agent
387•nicktikhonov•11h ago•110 comments

Buckle Up for Bumpier Skies

https://www.newyorker.com/magazine/2026/03/09/buckle-up-for-bumpier-skies
30•littlexsparkee•3h ago•7 comments

DOS Memory Management

https://www.os2museum.com/wp/dos-memory-management/
42•ingve•2d ago•1 comments

New iPad Air, powered by M4

https://www.apple.com/newsroom/2026/03/apple-introduces-the-new-ipad-air-powered-by-m4/
387•Garbage•18h ago•609 comments

Physicists developing a quantum computer that’s entirely open source

https://physics.aps.org/articles/v19/24
97•tzury•9h ago•22 comments

First in-utero stem cell therapy for fetal spina bifida repair is safe: study

https://health.ucdavis.edu/news/headlines/first-ever-in-utero-stem-cell-therapy-for-fetal-spina-b...
295•gmays•18h ago•51 comments

Guilty Displeasures

https://www.hopefulmons.com/p/what-are-your-guilty-displeasures
63•aregue•2d ago•65 comments

Launch HN: OctaPulse (YC W26) – Robotics and computer vision for fish farming

99•rohxnsxngh•16h ago•34 comments

Seed of Might Color Correction Process (2023) [pdf]

https://andrewvanner.github.io/som/SoM_CC_Process_Day.pdf
86•haunter•10h ago•21 comments

Motorola announces a partnership with GrapheneOS

https://motorolanews.com/motorola-three-new-b2b-solutions-at-mwc-2026/
2184•km•1d ago•799 comments

Elevated Errors in Claude.ai

https://status.claude.com/incidents/yf48hzysrvl5
109•LostMyLogin•5h ago•98 comments

iPhone 17e

https://www.apple.com/newsroom/2026/03/apple-introduces-iphone-17e/
266•meetpateltech•19h ago•385 comments

We Built a Video Rendering Engine by Lying to the Browser About What Time It Is

https://blog.replit.com/browsers-dont-want-to-be-cameras
4•darshkpatel•2d ago•0 comments

The Cathode Ray Tube site

https://www.crtsite.com/didactic-crt.html
45•joebig•1d ago•7 comments

Show HN: Govbase – Follow a bill from source text to news bias to social posts

https://govbase.com
190•foxfoxx•15h ago•76 comments

Guido van Rossum Interviews Thomas Wouters (Python Core Dev)

https://gvanrossum.github.io/interviews/Thomas.html
28•azhenley•1d ago•1 comments

Daily Driving GrapheneOS

https://blog.matthewbrunelle.com/8-4-months-of-daily-driving-grapheneos/
92•zdw•3h ago•83 comments

Inside the M4 Apple Neural Engine, Part 1: Reverse Engineering

https://maderix.substack.com/p/inside-the-m4-apple-neural-engine
330•zdw•1d ago•95 comments

RCade: Building a Community Arcade Cabinet

https://www.frankchiarulli.com/blog/building-the-rcade/
82•evakhoury•4d ago•14 comments

Against Query Based Compilers

https://matklad.github.io/2026/02/25/against-query-based-compilers.html
61•surprisetalk•1d ago•34 comments

Ask HN: Who is hiring? (March 2026)

209•whoishiring•17h ago•246 comments

The 185-Microsecond Type Hint

https://blog.sturdystatistics.com/posts/type_hint/
67•kianN•10h ago•8 comments

Programmable Cryptography (2024)

https://0xparc.org/writings/programmable-cryptography-1
69•fi-le•2d ago•40 comments

Ask HN: Who wants to be hired? (March 2026)

98•whoishiring•17h ago•228 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?