frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Qwen3.6-Max-Preview: Smarter, Sharper, Still Evolving

https://qwen.ai/blog?id=qwen3.6-max-preview
205•mfiguiere•2h ago•115 comments

Deezer says 44% of songs uploaded to its platform daily are AI-generated

https://techcrunch.com/2026/04/20/deezer-says-44-of-songs-uploaded-to-its-platform-daily-are-ai-g...
56•FiddlerClamp•1h ago•34 comments

Atlassian Enables Default Data Collection to Train AI

https://letsdatascience.com/news/atlassian-enables-default-data-collection-to-train-ai-f71343d8
260•kevcampb•4h ago•64 comments

GitHub's Fake Star Economy

https://awesomeagents.ai/news/github-fake-stars-investigation/
483•Liriel•8h ago•267 comments

ggsql: A Grammar of Graphics for SQL

https://opensource.posit.co/blog/2026-04-20_ggsql_alpha_release/
170•thomasp85•3h ago•43 comments

All phones sold in the EU to have replaceable batteries from 2027

https://www.theolivepress.es/spain-news/2026/04/20/eu-to-force-replaceable-batteries-in-phones-an...
503•ramonga•3h ago•342 comments

I prompted ChatGPT, Claude, Perplexity, and Gemini and watched my Nginx logs

https://surfacedby.com/blog/nginx-logs-ai-traffic-vs-referral-traffic
75•startages•1h ago•12 comments

10 years ago, someone wrote a test for servo that included an expiry in 2026

https://mastodon.social/@jdm_/116429380667467307
92•luu•21h ago•58 comments

M 7.4 earthquake – 100 km ENE of Miyako, Japan

https://earthquake.usgs.gov/earthquakes/eventpage/us6000sri7/
182•Someone•6h ago•76 comments

Sauna effect on heart rate

https://tryterra.co/research/sauna-effect-on-heart-rate
230•kyriakosel•3h ago•132 comments

WebUSB Extension for Firefox

https://github.com/ArcaneNibble/awawausb
94•tuananh•4h ago•69 comments

We Accepted Surveillance as Default

https://vivianvoss.net/blog/why-we-accepted-surveillance
7•speckx•13m ago•0 comments

Chernobyl's last wedding: The couple who married as a nuclear disaster unfolded

https://www.bbc.com/news/articles/c0q92lx8q75o
13•1659447091•1d ago•1 comments

Kimi K2.6: Advancing Open-Source Coding

https://www.kimi.com/blog/kimi-k2-6
143•meetpateltech•1h ago•46 comments

Palantir Wants to Reinstate the Draft

https://reason.com/2026/04/20/this-big-tech-firm-wants-to-reinstate-the-draft/
50•tcp_handshaker•29m ago•17 comments

OpenClaw isn't fooling me. I remember MS-DOS

https://www.flyingpenguin.com/build-an-openclaw-free-secure-always-on-local-ai-agent/
184•feigewalnuss•8h ago•222 comments

I'm never buying another Kindle, and neither should you

https://www.androidauthority.com/amazon-kindle-2026-3657863/
46•mikhael•1h ago•27 comments

Ask HN: How to solve the cold start problem for a two-sided marketplace?

77•alegd•3h ago•79 comments

Focused microwaves allow 3D printers to fuse circuits onto almost anything

https://newatlas.com/electronics/meta-nfc-focused-microwaves-circuits/
110•breve•2d ago•19 comments

NSA is using Anthropic's Mythos despite blacklist

https://www.axios.com/2026/04/19/nsa-anthropic-mythos-pentagon
334•Palmik•6h ago•251 comments

Up to 8M Bees Are Living in an Underground Network Beneath This Cemetery

https://www.discovermagazine.com/up-to-8-million-bees-are-living-in-an-underground-network-beneat...
139•janandonly•2d ago•22 comments

What if database branching was easy?

https://xata.io/blog/what-if-database-branching-was-easy
52•tee-es-gee•2d ago•30 comments

IPC medley: message-queue peeking, io_uring, and bus1

https://lwn.net/Articles/1065490/
22•signa11•3d ago•0 comments

SDF Public Access Unix System

https://sdf.org/?ssh
149•neehao•1d ago•72 comments

I Made the "Next-Level" Camera and I love it

https://thelibre.news/i-made-the-next-level-camera-and-i-love-it/
177•ndr•3d ago•61 comments

Show HN: Alien – Self-hosting with remote management (written in Rust)

13•alongub•1h ago•0 comments

Claude Token Counter, now with model comparisons

https://simonwillison.net/2026/Apr/20/claude-token-counts/
182•twapi•15h ago•72 comments

NASA Artemis Posters

https://www.nasa.gov/gallery/artemis/
79•bookofjoe•4h ago•9 comments

Zero-copy protobuf and ConnectRPC for Rust

https://medium.com/@iainmcgin/zero-copy-protobuf-and-connectrpc-for-rust-69bda8ac0f02
113•PaulHoule•3d ago•31 comments

Epicycles All the Way Down (2025)

https://www.strangeloopcanon.com/p/epicycles-all-the-way-down
27•surprisetalk•4d 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•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?