frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Separating signal from noise in coding evaluations

https://openai.com/index/separating-signal-from-noise-coding-evaluations/
106•sk4rekr0w•1h ago•44 comments

FAANG Simulator

https://www.abeyk.com/escape-the-rat-race/
140•nerdbiscuits•2h ago•52 comments

Chatto is now open source

https://www.hmans.dev/blog/chatto-is-open-source
628•speckx•7h ago•177 comments

Decoding the obfuscated bash script on a Uniqlo t-shirt

https://tris.sherliker.net/blog/obfuscated-self-evaluating-bash-script-by-cdn-akamai-being-suppli...
1249•speerer•14h ago•200 comments

Grok 4.5

https://x.ai/news/grok-4-5
396•BoumTAC•4h ago•348 comments

Mistral's Robostral Navigate: a state of the art robotics navigation model

https://mistral.ai/news/robostral-navigate/
381•ottomengis•8h ago•89 comments

Cloudflare Drop

https://www.cloudflare.com/drop/
147•coloneltcb•3h ago•83 comments

Show HN: Microsoft releases Flint, a visualization language for AI agents

https://microsoft.github.io/flint-chart/#/
146•chenglong-hn•5h ago•64 comments

Turning a pile of documents into a searchable useable knowledge base

https://github.com/linuxrebel/DocuBrowser
34•linuxrebe1•2h ago•6 comments

DKIM2 and DMARCbis Have Landed

https://stalw.art/blog/dkim2-dmarcbis/
44•StalwartLabs•2d ago•24 comments

GPT‑Live

https://openai.com/index/introducing-gpt-live/
547•logickkk1•5h ago•370 comments

A bug which affected only left handed users

https://shkspr.mobi/blog/2026/07/a-bug-which-only-affected-left-handed-users/
62•sixhobbits•9h ago•34 comments

Show HN: Yamanote.fun – A complete soundscape for Tokyo's Yamanote line

https://www.yamanote.fun/
9•madebymagnolia•1d ago•1 comments

OpenMandriva: Statement regarding attempted distribution sabotage

https://forum.openmandriva.org/t/statement-regarding-attempted-distribution-sabotage/8997
62•workethics•4h ago•9 comments

Show HN: Onboard-CLI, a LLM powered and AST-based tool to visualize codebase

https://github.com/animesh-94/Onboard-CLI
15•yr_animesh•2h ago•2 comments

The classifiers Anthropic puts in front of Fable are too zealous

https://combine-lab.github.io/blog/2026/07/07/fable-is-not-a-useful-model.html
168•karrot-kake•2h ago•151 comments

OpenBSD has a use-after-free allowing local privilege escalation to root

https://nvd.nist.gov/vuln/detail/cve-2026-57589
237•linggen•9h ago•115 comments

EU now one step away from reviving private message scanning rules

https://cyberinsider.com/eu-now-one-step-away-from-reviving-private-message-scanning-rules/
320•ggirelli•6h ago•126 comments

Cloudflare Meerkat - Globally distributed consensus

https://blog.cloudflare.com/meerkat-introduction/
195•bobnamob•9h ago•42 comments

I Built a Telegram Client for Pi

https://www.npmjs.com/package/@atharva-again/pi-tg
39•atharva-again•2d ago•20 comments

SWE-1.7 Reach Near GPT 5.5 and Opus Intelligence

https://cognition.com/blog/swe-1-7
238•mekpro•6h ago•122 comments

Poison, redzones and shadows: inside KASAN

https://bootlin.com/blog/poison-redzones-and-shadows-inside-kasan/
6•rrampage•2d ago•0 comments

Rewriting Bun in Rust

https://bun.com/blog/bun-in-rust
61•afturner•1h ago•12 comments

Open Source Barware: free, local-first bar inventory software (GPLv3)

https://opensourcebarware.com
4•RichBJamison•1h ago•0 comments

Understanding B-Tree Indexes in PostgreSQL: A Comprehensive Guide– Part 1

https://medium.com/@devli0/b-tree-indexes-in-postgresql-part-1-theory-eb2668c52520
35•corvus-cornix•3d ago•1 comments

TypeScript 7

https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/
410•DanRosenwasser•6h ago•150 comments

EVE Online's Carbon engine is now open source: Fenris Creations explains why

https://www.gamesindustry.biz/eve-onlines-carbon-engine-is-now-open-source-fenris-creations-expla...
369•Stevvo•5d ago•123 comments

Almost Always Unsigned

https://graphitemaster.github.io/aau/
15•gavide•3h ago•8 comments

Show HN: Agent Draw: An agent draws while you talk, built on TLDraw

https://techstackups.com/articles/tldraw-agent-draw/
26•jameswhitford•2d ago•2 comments

TabFont – guitar tabs rendered as you type

https://philatype.com/tabfont/
78•ChrisArchitect•3d ago•23 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?