frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Servo is now available on crates.io

https://servo.org/blog/2026/04/13/servo-0.1.0-release/
113•ffin•2h ago•25 comments

Android now stops you sharing your location in photos

https://shkspr.mobi/blog/2026/04/android-now-stops-you-sharing-your-location-in-photos/
191•edent•3h ago•122 comments

All elementary functions from a single binary operator

https://arxiv.org/abs/2603.21852
618•pizza•13h ago•174 comments

The economics of software teams: Why most engineering orgs are flying blind

https://www.viktorcessan.com/the-economics-of-software-teams/
288•kiyanwang•9h ago•152 comments

Mark Zuckerberg is reportedly building an AI clone to replace him in meetings

https://www.theverge.com/tech/910990/meta-ceo-mark-zuckerberg-ai-clone
28•temphaaa•30m ago•31 comments

Michigan 'digital age' bills pulled after privacy concerns raised

https://www.thecentersquare.com/michigan/article_7ca4e268-4a68-42fb-9042-f9d8604ebd7f.html
73•iamnothere•2h ago•30 comments

I went to America's worst national parks so you don't have to

https://substack.com/home/post/p-193626949
162•surprisetalk•2h ago•106 comments

US appeals court declares 158-year-old home distilling ban unconstitutional

https://nypost.com/2026/04/11/us-news/us-appeals-court-declares-158-year-old-home-distilling-ban-...
56•t-3•1h ago•5 comments

Taking on CUDA with ROCm: 'One Step After Another'

https://www.eetimes.com/taking-on-cuda-with-rocm-one-step-after-another/
219•mindcrime•16h ago•162 comments

AI could be the end of the digital wave, not the next big thing

https://thenextwavefutures.wordpress.com/2026/04/07/ai-end-digital-wave-technology-innovation-perez/
130•surprisetalk•2h ago•137 comments

DIY Soft Drinks

https://blinry.org/diy-soft-drinks/
574•_Microft•22h ago•175 comments

Bring Back Idiomatic Design (2023)

https://essays.johnloeber.com/p/4-bring-back-idiomatic-design
615•phil294•1d ago•347 comments

Show HN: boringBar – a taskbar-style dock replacement for macOS

https://boringbar.app/
433•a-ve•21h ago•244 comments

Microsoft isn't removing Copilot from Windows 11, it's just renaming it

https://www.neowin.net/opinions/microsoft-isnt-removing-copilot-from-windows-11-its-just-renaming...
9•bundie•1h ago•3 comments

Most people can't juggle one ball

https://www.lesswrong.com/posts/jTGbKKGqs5EdyYoRc/most-people-can-t-juggle-one-ball
430•surprisetalk•4d ago•147 comments

Ask HN: What Are You Working On? (April 2026)

273•david927•22h ago•880 comments

Point Cloud Allemansrätten

https://digitalflapjack.com/weeknotes/point-cloud-allemansr%C3%A4tten/
30•ColinWright•3h ago•2 comments

A perfectable programming language

https://alok.github.io/lean-pages/perfectable-lean/
171•yuppiemephisto•17h ago•75 comments

The hottest college major [Computer Science] hit a wall. What happened?

https://www.washingtonpost.com/technology/2026/04/13/computer-science-major-ai/
27•1vuio0pswjnm7•2h ago•25 comments

Show HN: I built a social media management tool in 3 weeks with Claude and Codex

https://github.com/brightbeanxyz/brightbean-studio
129•JanSchu•5h ago•85 comments

I gave every train in New York an instrument

https://www.trainjazz.com/
339•joshuawolk•2d ago•67 comments

They See Your Photos

https://theyseeyourphotos.com/
101•cyberlurker•1h ago•91 comments

Tell HN: Docker pull fails in Spain due to football Cloudflare block

1034•littlecranky67•1d ago•378 comments

We have a 99% email reputation, but Gmail disagrees

https://blogfontawesome.wpcomstaging.com/we-have-a-99-email-reputation-gmail-disagrees/
307•em-bee•1d ago•270 comments

I ran Gemma 4 as a local model in Codex CLI

https://blog.danielvaughan.com/i-ran-gemma-4-as-a-local-model-in-codex-cli-7fda754dc0d4
147•dvaughan•18h ago•67 comments

Apple's accidental moat: How the "AI Loser" may end up winning

https://adlrocha.substack.com/p/adlrocha-how-the-ai-loser-may-end
325•walterbell•11h ago•280 comments

Show HN: Oberon System 3 runs natively on Raspberry Pi 3 (with ready SD card)

https://github.com/rochus-keller/OberonSystem3Native/releases
215•Rochus•1d ago•63 comments

Is math big or small?

https://chessapig.github.io/talks/Big-Small
66•robinhouston•1d ago•25 comments

Exploiting the most prominent AI agent benchmarks

https://rdi.berkeley.edu/blog/trustworthy-benchmarks-cont/
549•Anon84•1d ago•134 comments

Optimization of 32-bit Unsigned Division by Constants on 64-bit Targets

https://arxiv.org/abs/2604.07902
101•mpweiher•1d ago•13 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•10mo ago
Thanks for the response, guess that makes sense.
pabs3•10mo 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?