frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Kimi K2.7 Code is generally available in GitHub Copilot

https://github.blog/changelog/2026-07-01-kimi-k2-7-is-now-available-in-github-copilot/
125•unliftedq•4h ago•39 comments

A new Android malware from Google

https://f-droid.org/2026/07/01/adv-malware.html
324•drewfax•5h ago•151 comments

We Don't Have to Be This Bad at Improving Society

https://kasperjunge.com/blog/we-dont-have-to-be-this-bad-at-improving-society/
12•juunge•29m ago•2 comments

ZCode – Harness for GLM-5.2

https://zcode.z.ai/en
386•chvid•10h ago•287 comments

Oomwoo, an open-source robot vacuum you build yourself

https://makerspet.com/blog/building-an-open-source-robot-vacuum-meet-oomwoo/
271•devicelimit•8h ago•50 comments

Asymmetric Quantization: Near-Lossless Retrieval with 97% Storage Reduction

https://www.mixedbread.com/blog/asymmetric-quant
16•breadislove•2d ago•2 comments

CursorBench 3.1

https://cursor.com/evals
50•handfuloflight•3h ago•35 comments

Bring back crappy forums

https://tedium.co/2026/07/01/online-web-forums-retrospective/
240•pentagrama•6h ago•142 comments

The Fall of the Theorem Economy

https://davidbessis.substack.com/p/the-fall-of-the-theorem-economy
6•varjag•54m ago•0 comments

What to learn to be a graphics programmer

https://blog.demofox.org/2026/07/01/what-to-learn-to-be-a-graphics-programmer/
332•atan2•15h ago•175 comments

FFmpeg 9.1's new AAC encoder

https://hydrogenaudio.org/index.php/topic,129691.0.html
370•ledoge•18h ago•112 comments

Opening up 'Zero-Knowledge Proof' technology to promote privacy in age assurance

https://blog.google/innovation-and-ai/technology/safety-security/opening-up-zero-knowledge-proof-...
149•consumer451•10h ago•140 comments

My Favorite Keyboards

https://fabiensanglard.net/keyboards/index.html
9•tmach32•3d ago•0 comments

Ask HN: Who is hiring? (July 2026)

197•whoishiring•17h ago•207 comments

How do wombats poop cubes?

https://www.science.org/content/article/how-do-wombats-poop-cubes-scientists-get-bottom-mystery
112•bushwart•1d ago•51 comments

Learn Vim motions with an ice-cream van

https://thisismodest.com/vimscoops/
65•marcusmichaels•14h ago•12 comments

Weave Robotics launches Isaac 1, a $7,999 home robot with Fall 2026 deliveries

https://www.weaverobotics.com/isaac-1
171•ryanmerket•14h ago•239 comments

The Underhanded C Contest

https://underhanded-c.org/
90•ccabraldev•10h ago•11 comments

Qualcomm Linux 2.0

https://www.qualcomm.com/developer/blog/2026/06/qualcomm-linux-2-now-available
100•gilgamesh3•11h ago•41 comments

For first time, a cell built from scratch grows and divides

https://www.quantamagazine.org/for-the-first-time-a-cell-built-from-scratch-grows-and-divides-202...
849•defrost•18h ago•276 comments

Show HN: Searchable directory of 22k+ products from worker-owned co-ops

https://www.workerowned.info/
343•IESAI_ski•12h ago•65 comments

Why jet engines aren't made in China

https://aakash.substack.com/p/why-jet-engines-arent-made-in-china
146•paulpauper•1d ago•117 comments

The Wisdom of Quinn the Eskimo (Apple Developer Technical Support Engineer)

https://github.com/macshome/The-Wisdom-of-Quinn
17•gregsadetsky•2d ago•8 comments

Monetization Gateway: Charge for any resource behind Cloudflare via x402

https://blog.cloudflare.com/monetization-gateway/
293•soheilpro•18h ago•207 comments

Senior SWE-Bench: open-source benchmark that assesses agents as senior engineers

https://senior-swe-bench.snorkel.ai/
72•matt_d•6h ago•62 comments

Ask HN: Who wants to be hired? (July 2026)

130•whoishiring•17h ago•313 comments

The Apple Disk II Controller Card (2021)

https://www.bigmessowires.com/2021/11/12/the-amazing-disk-ii-controller-card/
82•stmw•2d ago•20 comments

Proliferate (YC S25) Is Hiring

https://www.ycombinator.com/companies/proliferate/jobs/mMHvKR9-founding-product-engineer
1•pablo24602•11h ago

Chip Off The Old Block

https://www.astralcodexten.com/p/chip-off-the-old-block
77•paulpauper•11h ago•8 comments

Launch HN: Parsewise (YC P25) – Reason Across Documents with an API

51•gergelycsegzi•19h ago•50 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?