frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Zig Creator Calls Spade a Spade, Anthropic Blows Smoke

https://raymyers.org/post/zed-creator-calls-spade-a-spade/
180•crowdhailer•1h ago•102 comments

Interrail: 6,379Km and 13 Countries over 7 weeks

https://shkspr.mobi/blog/2026/07/another-ridiculous-interrail-holiday-6379km-and-13-countries-ove...
51•coinfused•2h ago•39 comments

The social physics of conversation: Communication patterns matter

https://andiroberts.com/citizenship/the-social-physics-of-conversation-citizenship-leadership
41•kiyanwang•5d ago•6 comments

GhostLock, a stack-UAF that has existed in all Linux distributions for 15 years

https://nebusec.ai/research/ionstack-part-2/
272•ranger_danger•4d ago•114 comments

Beavis Ultrasound PnP ISA Sound Card Replica

https://github.com/schlae/BeavisUltrasound
61•mariuz•4h ago•22 comments

Cyberpunk Comics, Manga and Graphic Novels

https://shellzine.net/cyberpunk-comics/
190•zdw•11h ago•64 comments

Tiny Emulators

https://floooh.github.io/tiny8bit-preview/index.html
257•naves•13h ago•22 comments

The Graph That Should Be Front-Page News

https://www.lyrebirddreaming.com/post/the-graph-that-should-be-front-page-news
58•rakel_rakel•4h ago•23 comments

Frieve Vinyl Explained – Microscopic stylus/groove physics simulation

https://frieve-a.github.io/sound_toolbox/vinyl_explained/vinyl_explained.html
14•XzetaU8•3d ago•1 comments

So you want to learn physics (second edition, 2021)

https://www.susanrigetti.com/physics
225•azhenley•5d ago•40 comments

Backtrack-Free Cursive

https://mmapped.blog/posts/52-backtrack-free-cursive
86•dmit•4h ago•40 comments

Designing and assembling my first PCB

https://vilkeliskis.com/b/2026/0711.html
113•tadasv•11h ago•51 comments

Guy took Jupiter photo with Game Boy Camera, giant telescope, publishes tutorial

https://www.engadget.com/2211886/guy-who-took-photo-of-jupiter-with-a-game-boy-camera-and-giant-t...
52•thunderbong•2d ago•23 comments

How to read more books

https://scotto.me/blog/2026-07-12-how-to-read-more-books/
370•silcoon•18h ago•195 comments

Ask HN: Add flag for AI-generated articles

684•levkk•8h ago•310 comments

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

160•david927•12h ago•508 comments

Berkshire's $397B Bet Against an Overheated Market

https://www.disruptionbanking.com/2026/07/13/inside-berkshires-397-billion-bet-against-an-overhea...
28•emsidisii•1h ago•15 comments

Are you telling me a readonly property is wrecking my performance?

https://shub.club/writings/2026/july/check-your-scrollheight/
38•forthwall•3d ago•17 comments

Sam Neill has died

https://www.theguardian.com/film/2026/jul/13/sam-neill-death-actor-dies-aged-78
148•j4mie•4h ago•36 comments

LARP – Revenue infrastructure for serious founders

https://www.larp.website/
244•BerislavLopac•17h ago•50 comments

Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper

https://ploy.ai/blog/migrating-a-production-ai-agent-to-gpt-5-6
210•brryant•17h ago•88 comments

The console wars have been lost

https://xeiaso.net/notes/2026/console-wars-lost/
6•ExMachina73•3d ago•0 comments

Vint Cerf, “father of the Internet”, is retiring

https://techcrunch.com/2026/06/30/the-father-of-the-internet-is-finally-retiring/
316•compiler-guy•3d ago•180 comments

Kode Dot Programmable pocket device for makers, pentesters and geeks

https://kode.diy
84•iNic•12h ago•21 comments

Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k

https://systima.ai/blog/claude-code-vs-opencode-token-overhead
594•systima•15h ago•323 comments

First look at Quest, the final ship of Antarctic explorer Shackleton

https://www.cbc.ca/news/canada/quest-shipwreck-expedition-images-9.7262229
34•curmudgeon22•4d ago•3 comments

Quadrupling code performance with a "useless" if

https://purplesyringa.moe/blog/quadrupling-code-performance-with-a-useless-if/
59•birdculture•2h ago•8 comments

I Learned to Read Again

https://substack.magazinenongrata.com/p/how-i-learned-to-read-again
150•georgex7•15h ago•58 comments

Why write code in 2026

https://softwaredoug.com/blog/2026/07/09/write-code
163•softwaredoug•2d ago•216 comments

How we can reduce traffic congestion

https://research.google/blog/the-power-of-collaboration-how-we-can-reduce-traffic-congestion/
134•raahelb•18h ago•199 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•1y ago

Comments

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

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

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