frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

France confirms data breach at government agency that manages citizens' IDs

https://techcrunch.com/2026/04/22/france-confirms-data-breach-at-government-agency-that-manages-c...
213•robtherobber•1h ago•70 comments

Bitwarden CLI Compromised in Ongoing Checkmarx Supply Chain Campaign

https://socket.dev/blog/bitwarden-cli-compromised
319•tosh•3h ago•155 comments

'Hairdryer used to trick weather sensor' to win $34,000 Polymarket bet

https://www.telegraph.co.uk/business/2026/04/23/hairdryer-used-trick-weather-sensor-34000-polymar...
31•zdw•28m ago•23 comments

Incident with Multple GitHub Services

https://www.githubstatus.com/incidents/myrbk7jvvs6p
60•bwannasek•1h ago•34 comments

A DIY Watch You Can Actually Wear

https://www.hackster.io/news/a-diy-watch-you-can-actually-wear-8f91c2dac682
44•sarusso•2d ago•17 comments

I am building a cloud

https://crawshaw.io/blog/building-a-cloud
822•bumbledraven•12h ago•421 comments

Show HN: Honker – Postgres NOTIFY/LISTEN Semantics for SQLite

https://github.com/russellromney/honker
161•russellthehippo•5h ago•25 comments

Your hex editor should color-code bytes

https://simonomi.dev/blog/color-code-your-bytes/
385•tobr•2d ago•113 comments

Alberta startup sells no-tech tractors for half price

https://wheelfront.com/this-alberta-startup-sells-no-tech-tractors-for-half-price/
2045•Kaibeezy•1d ago•699 comments

To Protect and Swerve: NYPD Cop Has 547 Speeding Tickets

https://nyc.streetsblog.org/2026/04/23/to-protect-and-swerve-nypd-cop-has-527-speeding-tickets-ye...
109•greedo•2h ago•73 comments

Apple fixes bug that cops used to extract deleted chat messages from iPhones

https://techcrunch.com/2026/04/22/apple-fixes-bug-that-cops-used-to-extract-deleted-chat-messages...
780•cdrnsf•21h ago•177 comments

Investigation uncovers two sophisticated telecom surveillance campaigns

https://techcrunch.com/2026/04/23/surveillance-vendors-caught-abusing-access-to-telcos-to-track-p...
316•mentalgear•5h ago•110 comments

MeshCore development team splits over trademark dispute and AI-generated code

https://blog.meshcore.io/2026/04/23/the-split
8•wielebny•34m ago•1 comments

Writing a C Compiler, in Zig (2025)

https://ar-ms.me/thoughts/c-compiler-1-zig/
90•tosh•8h ago•28 comments

The Ferrari of Espresso Machines Is Fueling a Hot Resale Market

https://www.nytimes.com/2026/04/20/dining/la-marzocco-espresso-machine.html
11•mitchbob•2d ago•2 comments

We found a stable Firefox identifier linking all your private Tor identities

https://fingerprint.com/blog/firefox-tor-indexeddb-privacy-vulnerability/
852•danpinto•23h ago•255 comments

Jiga (YC W21) Is Hiring

https://jiga.io/about-us/
1•grmmph•5h ago

A Renaissance gambling dispute spawned probability theory

https://www.scientificamerican.com/article/how-a-renaissance-gambling-dispute-spawned-probability...
63•sohkamyung•2d ago•9 comments

Isopods of the world

https://isopod.site/
102•debesyla•2d ago•42 comments

Arch Linux Now Has a Bit-for-Bit Reproducible Docker Image

https://antiz.fr/blog/archlinux-now-has-a-reproducible-docker-image/
217•maxloh•15h ago•76 comments

5x5 Pixel font for tiny screens

https://maurycyz.com/projects/mcufont/
756•zdw•4d ago•151 comments

Our newsroom AI policy

https://arstechnica.com/staff/2026/04/our-newsroom-ai-policy/
152•zdw•12h ago•105 comments

Raylib v6.0

https://github.com/raysan5/raylib/releases/tag/6.0
148•rydgel•5h ago•20 comments

A History of Erasures Learning to Write Like Leylâ Erbil

https://thepointmag.com/criticism/a-history-of-erasures/
20•lermontov•2d ago•0 comments

A True Life Hack: What Physical 'Life Force' Turns Biology's Wheels?

https://www.quantamagazine.org/what-physical-life-force-turns-biologys-wheels-20260420/
160•Prof_Sigmund•2d ago•32 comments

An amateur historian's favorite books about the Silk Road

https://bookdna.com/best-books/silk-road
69•bwb•2d ago•28 comments

The end of responsive images

https://piccalil.li/blog/the-end-of-responsive-images/
23•OuterVale•4h ago•15 comments

Website streamed live directly from a model

https://flipbook.page/
392•sethbannon•23h ago•103 comments

Over-editing refers to a model modifying code beyond what is necessary

https://nrehiew.github.io/blog/minimal_editing/
401•pella•23h ago•234 comments

Highlights from Git 2.54

https://github.blog/open-source/git/highlights-from-git-2-54/
121•ingve•2d ago•68 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?