frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Adoption of EVs tied to real-world reductions in air pollution: study

https://keck.usc.edu/news/adoption-of-electric-vehicles-tied-to-real-world-reductions-in-air-poll...
90•hhs•2h ago•31 comments

BirdyChat becomes first European chat app that is interoperable with WhatsApp

https://www.birdy.chat/blog/first-to-interoperate-with-whatsapp
418•joooscha•7h ago•275 comments

We X-Rayed a Suspicious FTDI USB Cable

https://eclypsium.com/blog/xray-counterfeit-usb-cable/
71•aa_is_op•2h ago•22 comments

Postmortem: Our first VLEO satellite mission (with imagery and flight data)

https://albedo.com/post/clarity-1-what-worked-and-where-we-go-next
129•topherhaddad•6h ago•47 comments

Two Weeks Until Tapeout

https://essenceia.github.io/projects/two_weeks_until_tapeout/
22•client4•1h ago•0 comments

Raspberry Pi Drag Race: Pi 1 to Pi 5 – Performance Comparison

https://the-diy-life.com/raspberry-pi-drag-race-pi-1-to-pi-5-performance-comparison/
131•verginer•8h ago•70 comments

Claude Code's new hidden feature: Swarms

https://twitter.com/NicerInPerson/status/2014989679796347375
312•AffableSpatula•12h ago•230 comments

Draig, a Welsh Programming Language

https://raku.land/zef:l10n/L10N::CY
11•librasteve•2d ago•6 comments

High-bandwidth flash progress and future

https://blocksandfiles.com/2026/01/19/a-window-into-hbf-progress/
16•tanelpoder•4d ago•4 comments

How I estimate work

https://www.seangoedecke.com/how-i-estimate-work/
416•mattjhall•16h ago•253 comments

Memory layout in Zig with formulas

https://raymondtana.github.io/math/programming/2026/01/23/zig-alignment-and-sizing.html
83•raymondtana•10h ago•22 comments

Poland's energy grid was targeted by never-before-seen wiper malware

https://arstechnica.com/security/2026/01/wiper-malware-targeted-poland-energy-grid-but-failed-to-...
150•Bender•5h ago•41 comments

Small Kafka: Tansu and SQLite on a free t3.micro

https://blog.tansu.io/articles/broker-aws-free-tier
60•rmoff•4d ago•5 comments

I added a Bluesky comment section to my blog

https://micahcantor.com/blog/bluesky-comment-section.html
215•hydroxideOH-•6h ago•78 comments

Agent orchestration for the timid

https://substack.com/inbox/post/185649875
75•markferree•7h ago•19 comments

Typography on Pencils (2023)

https://www.presentandcorrect.com/blogs/blog/typography-on-pencils-1-5
12•NaOH•4d ago•0 comments

Ask HN: Gmail spam filtering suddenly marking everything as spam?

138•goopthink•10h ago•94 comments

First Design Engineer Hire – Build Games at Gym Class (YC W22)

https://www.ycombinator.com/companies/gym-class-by-irl-studios/jobs/ywXHGBv-design-engineer-senio...
1•hackerews•5h ago

Shared Claude: A website controlled by the public

https://sharedclaude.com/
46•reasonableklout•18h ago•18 comments

Maze Algorithms (2017)

http://www.jamisbuck.org/mazes/
99•surprisetalk•1d ago•26 comments

Understanding Rust Closures

https://antoine.vandecreme.net/blog/rust-closures/
38•avandecreme•8h ago•16 comments

Europe wants to end its dangerous reliance on US internet technology

https://theconversation.com/europe-wants-to-end-its-dangerous-reliance-on-us-internet-technology-...
159•DyslexicAtheist•3h ago•124 comments

Show HN: StormWatch – Weather emergency dashboard with prep checklists

https://jeisey.github.io/stormwatch/
29•lotusxblack•7h ago•6 comments

The Kept and the Killed (2022)

https://publicdomainreview.org/essay/the-kept-and-the-killed/
32•nomagicbullet•11h ago•3 comments

MS confirms it will give the FBI your Windows PC data encryption key if asked

https://www.windowscentral.com/microsoft/windows-11/microsoft-bitlocker-encryption-keys-give-fbi-...
455•blacktulip•13h ago•283 comments

JSON-render: LLM-based JSON-to-UI tool

https://json-render.dev/
58•rickcarlino•7h ago•14 comments

Show HN: Open-source Figma design to code

https://github.com/vibeflowing-inc/vibe_figma
33•alepeak•20h ago•8 comments

KAOS – The Kubernetes Agent Orchestration System

https://github.com/axsaucedo/kaos
14•axsaucedo•4d ago•4 comments

Doing gigabit Ethernet over my British phone wires

https://thehftguy.com/2026/01/22/doing-gigabit-ethernet-over-my-british-phone-wires/
430•user5994461•16h ago•245 comments

The Concatative Language XY

http://www.nsl.com/k/xy/xy.txt
41•ofalkaed•7h ago•15 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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