frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

AirSnitch: Demystifying and breaking client isolation in Wi-Fi networks [pdf]

https://www.ndss-symposium.org/wp-content/uploads/2026-f1282-paper.pdf
217•DamnInteresting•3h ago•110 comments

I baked a pie every day for a year and it changed my life

https://www.theguardian.com/lifeandstyle/2026/feb/22/a-new-start-after-60-i-baked-a-pie-every-day...
71•NaOH•2d ago•39 comments

Palm OS User Interface Guidelines (2003) [pdf]

https://cs.uml.edu/~fredm/courses/91.308-spr05/files/palmdocs/uiguidelines.pdf
73•spiffytech•2h ago•29 comments

Will vibe coding end like the maker movement?

https://read.technically.dev/p/vibe-coding-and-the-maker-movement
105•itunpredictable•3h ago•118 comments

Launch HN: Cardboard (YC W26) – Agentic video editor

https://www.usecardboard.com/
15•sxmawl•1h ago•3 comments

Nano Banana 2: Google's latest AI image generation model

https://blog.google/innovation-and-ai/technology/ai/nano-banana-2/
340•davidbarker•3h ago•323 comments

Show HN: Rev-dep – 20x faster knip.dev alternative build in Go

https://github.com/jayu/rev-dep
12•jayu_dev•52m ago•3 comments

Google Street View in 2026

https://tech.marksblogg.com/google-street-view-coverage.html
77•marklit•2h ago•55 comments

Show HN: Deff – side-by-side Git diff review in your terminal

https://github.com/flamestro/deff
25•flamestro•1h ago•10 comments

Show HN: Hacker Smacker – spot great (and terrible) HN commenters at a glance

https://hackersmacker.org
38•conesus•2d ago•24 comments

Bild AI (YC W25) Is Hiring Interns to Make Housing Affordable

https://www.workatastartup.com/jobs/80596
1•rooppal•2h ago

Google API keys weren't secrets, but then Gemini changed the rules

https://trufflesecurity.com/blog/google-api-keys-werent-secrets-but-then-gemini-changed-the-rules
1113•hiisthisthingon•23h ago•265 comments

BuildKit: Docker's Hidden Gem That Can Build Almost Anything

https://tuananh.net/2026/02/25/buildkit-docker-hidden-gem/
94•jasonpeacock•5h ago•27 comments

Show HN: Beehive – Multi-Workspace Agent Orchestrator

https://storozhenko98.github.io/beehive/
20•mst98•2d ago•9 comments

Show HN: Terminal Phone – E2EE Walkie Talkie from the Command Line

https://gitlab.com/here_forawhile/terminalphone
245•smalltorch•8h ago•59 comments

Show HN: Linex – A daily challenge: placing pieces on a board that fights back

https://www.playlinex.com/
17•Humanista75•1d ago•9 comments

The Wolfram S Combinator Challenge

https://www.combinatorprize.org/
19•paraschopra•3d ago•0 comments

Steering interpretable language models with concept algebra

https://www.guidelabs.ai/post/steerling-steering-8b/
22•luulinh90s•19h ago•1 comments

iPhone and iPad approved to handle classified NATO information

https://www.apple.com/newsroom/2026/02/iphone-and-ipad-approved-to-handle-classified-nato-informa...
49•throwfaraway4•1h ago•24 comments

just-bash: Bash for Agents

https://github.com/vercel-labs/just-bash
78•tosh•6h ago•43 comments

Show HN: Mission Control – Open-source task management for AI agents

https://github.com/MeisnerDan/mission-control
13•meisnerd•6h ago•2 comments

OsmAnd's Faster Offline Navigation

https://osmand.net/blog/fast-routing/
8•todsacerdoti•1h ago•4 comments

He saw an abandoned trailer. Then, uncovered a surveillance network

https://calmatters.org/justice/2026/02/alpr-border-patrol-caltrans/
39•Element_•1h ago•14 comments

Open Source Endowment – new funding source for open source maintainers

https://endowment.dev/
132•kvinogradov•3h ago•93 comments

What Claude Code Chooses

https://amplifying.ai/research/claude-code-picks
9•tin7in•1h ago•0 comments

Tell HN: YC companies scrape GitHub activity, send spam emails to users

484•miki123211•10h ago•171 comments

Jimi Hendrix was a systems engineer

https://spectrum.ieee.org/jimi-hendrix-systems-engineer
626•tintinnabula•23h ago•216 comments

Banned in California

https://www.bannedincalifornia.org/
443•pie_flavor•20h ago•518 comments

This time is different

https://shkspr.mobi/blog/2026/02/this-time-is-different/
42•speckx•6h ago•43 comments

How will OpenAI compete?

https://www.ben-evans.com/benedictevans/2026/2/19/how-will-openai-compete-nkg2x
429•iamskeole•21h ago•592 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?