frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Kimi K3-256k

https://www.kimi.com/code/docs/en/kimi-code/models
214•monneyboi•1h ago•53 comments

The coolest use for the Vision Pro

https://christianselig.com/2026/07/vision-pro-house/
52•robbiet480•33m ago•17 comments

Show HN: Open-source engine running Gemma 4 26B in 2 GB RAM on any M-series Mac

https://github.com/drumih/turbo-fieldfare
531•gitpusher42•6h ago•181 comments

Anatomy of a Frontier Lab Agent Intrusion: A Technical Timeline of the Incident

https://huggingface.co/blog/agent-intrusion-technical-timeline
202•artninja1988•1d ago•110 comments

Superlogical

https://www.superlogical.com/
392•yan•5h ago•265 comments

SalesPatriot (YC W25) Is Hiring FDEs

https://www.ycombinator.com/companies/salespatriot/jobs/M46X6YX-forward-deployed-engineer
1•maciejSz•12m ago

Keychron announces first open-source firmware for gaming mice

https://www.digitalfoundry.net/news/2026/07/keychron-announces-first-open-source-firmware-for-gam...
196•JLO64•4h ago•83 comments

KOReader

https://koreader.rocks/
608•Cider9986•10h ago•194 comments

A.I. companies are recruiting electricians and carpenters by the thousands

https://www.nytimes.com/2026/07/29/business/economy/data-center-electricians-training.html
163•thm•6h ago•210 comments

A Trampoline

https://dogdogfish.com/blog/2026/07/29/a-trampoline/
19•matthewsharpe3•58m ago•5 comments

Handbook.md shows that long policy documents do not reliably govern agents

https://arxiv.org/abs/2607.25398
264•spIrr•8h ago•168 comments

Commodification of Intelligence: Good, Bad, and Ugly Circular AI Deals

https://www.emergingtrajectories.com/lh/commodification-and-circularity/
29•cl42•2h ago•21 comments

Document-borne AI worms can self-propagate through Copilot for Word

https://enklypesalt.com/posts/context-collapse-part3-ai-worming-through-word/
303•Canopy9560•9h ago•226 comments

Show HN: CheapFoodMap – A map of good meals under $10

https://cheapfoodmap.com/
75•jaep1•4h ago•68 comments

Some thoughts about Anthropic's new cryptanalysis results

https://blog.cryptographyengineering.com/2026/07/29/some-notes-about-anthropics-new-results/
73•supermatou•4h ago•41 comments

Launch HN: Tokenless (YC S26) – Automatic model switching to save money

https://usetokenless.com/
43•rohaga•5h ago•38 comments

How to Not Die by a Thousand Cuts. Or, How to Think About Software Quality

https://www.evalapply.org/posts/how-to-not-die-by-a-thousand-cuts/index.html
27•adityaathalye•2h ago•9 comments

Darktable

https://www.darktable.org/
242•siatko•8h ago•123 comments

I'm Running a Programming Contest

https://eieio.games/blog/im-running-the-icfp-programming-contest/
10•signa11•4d ago•2 comments

Theo Conjecture solves 35-year-old math problem, finds a term no one predicted

https://firstprinciples.com/blog-article/ai-system-theo-conjecture-solves-35-year-old-math-conjec...
7•otalp•51m ago•0 comments

How much can you delegate to agents?

https://newsletter.posthog.com/p/agent-autonomy
22•duck•2h ago•0 comments

The Rust on ESP Book

https://docs.espressif.com/projects/rust/book/
90•AlexeyBrin•4d ago•9 comments

Turning a Dumb AC Unit Smart (Without Losing My Security Deposit)

https://prilik.com/blog/post/automating-ac-nyc/
49•austinallegro•2h ago•42 comments

Self-hosting Kimi K3: 20% more hardware cost, 20% better task resolution

https://aistack.imec-int.com/blog/gpu-self-hosting
95•flifenstein•6h ago•32 comments

Hamburg's Stadtpark: A Park Built to Be Used

https://alsterrunde.com/hamburgs-stadtpark-a-park-built-to-be-used/
83•mertbio•2d ago•22 comments

Claude Is Down

https://status.claude.com/incidents/q2kg8n613kr3
185•gregsadetsky•1h ago•158 comments

A field day for Gleam's language server – Gleam v1.18.0 release

https://gleam.run/news/a-field-day-for-gleams-language-server/
13•linggen•2h ago•0 comments

Shipping Godot VR and Porting to PSVR2: A Partial Post Mortem

https://www.claire-blackshaw.com/blog/2026/07/shipping-godot-vr-and-porting-to-psvr2-a-partial-po...
98•ibobev•8h ago•11 comments

GPT-5.6 vs. Claude Fable 5 for Physical AI, which performs best?

https://juliahub.com/blog/frontier-models-physical-ai-evaluation
70•mbauman•6h ago•15 comments

Show HN: Qwen Scribe – local transcription and dictation for Apple Silicon

https://github.com/VladUZH/qwen-scribe
61•sidclaw•6h ago•16 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?