frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

AWS: Inaccurate Estimated Billing Data – $1.7 billion

589•nprateem•7h ago•350 comments

Mozilla: The state of open source AI

https://stateofopensource.ai/
182•rellem•2h ago•119 comments

First atmosphere found on Earth-like planet in habitable zone of distant star

https://www.bbc.com/news/articles/cy4kdd1e0ejo
120•neversaydie•3h ago•96 comments

A Road to Lisp: Which Lisp

https://scotto.me/blog/2026-07-17-which-lisp/
86•silcoon•3h ago•43 comments

Kimi K3, and what we can still learn from the pelican benchmark

https://simonwillison.net/2026/Jul/16/kimi-k3/
66•droidjj•2h ago•29 comments

Three ways people respond to a problem (other than solving it)

https://improvesomething.today/responses-to-problems/
77•surprisetalk•3h ago•27 comments

AI Meets Cryptography 2: What AI Found in OpenVM's ZkVM

https://blog.zksecurity.xyz/posts/openvm-bugs/
51•duha•2h ago•0 comments

Show HN: Watch bots interact with an SSH honeypot in real time

https://honeypotlive.cc/
73•tusksm•3h ago•27 comments

More Bounce to the Ounce

https://mceglowski.substack.com/p/more-bounce-to-the-ounce
46•pavel_lishin•3h ago•7 comments

Frame – the first Linux Assembly X server

https://isene.org/2026/07/Frame.html
13•guybedo•1h ago•3 comments

Show HN: Explore the Workspaces of Modern Creators

https://workspaces.xyz/
24•ryangilbert•1h ago•14 comments

EEG shows brain can simultaneous encode two speech streams

https://journals.plos.org/plosbiology/article?id=10.1371/journal.pbio.3003876
212•giuliomagnifico•11h ago•135 comments

Claude Code: Anatomy of a Misfeature

https://www.olafalders.com/2026/07/17/claude-code-anatomy-of-a-misfeature/
103•oalders•2h ago•68 comments

Manufact (YC S25) Is Hiring a Senior infra engineer to build the MCP cloud

https://www.ycombinator.com/companies/manufact/jobs/Dh6PYP5-senior-infrastructure-engineer
1•luigipederzani•3h ago

Pebble Mega Update – July 2026

https://repebble.com/blog/pebble-mega-update-july-2026
222•crazysaem•13h ago•133 comments

CO2 overload, detected in human blood, suggests toxic atmosphere within 50 years

https://link.springer.com/article/10.1007/s11869-026-01918-5
37•OutOfHere•45m ago•27 comments

PennyLane is an open-source quantum software platform for quantum

https://github.com/PennyLaneAI/pennylane
28•donutloop•3h ago•3 comments

VulnHunter: Capital One's agentic AI code security tool

https://www.capitalone.com/tech/open-source/announcing-vulnhunter/
30•medina•4h ago•19 comments

Faster binary search: from compiled code to mechanical sympathy

https://pythonspeed.com/articles/branchless-binary-search/
30•enz•5d ago•9 comments

Microsoft Comic Chat is now open source

https://opensource.microsoft.com/blog/2026/07/16/microsoft-comic-chat-is-now-open-source/
764•jervant•1d ago•162 comments

Show HN: On-chain bond market where the issuers are AI agents

https://selbonds.now
11•griffinfoster7•2h ago•13 comments

Apple targets dozens of OpenAI employees with legal letters

https://www.ft.com/content/1b8c9d52-88a9-426b-ba47-f1811f859166
246•merksittich•5h ago•196 comments

Camera Chase Vehicle

https://transistor-man.com/gimbal_camera_rover.html
130•geerlingguy•1w ago•14 comments

Frank Lloyd Wright's First Home

https://www.architecturaldigest.com/story/frank-lloyd-wright-home-and-studio-everything-you-need-...
5•NaOH•4d ago•0 comments

How Has Roman Concrete Lasted for Millennia? 1,900-Year-Old Latrine Offers Clues

https://www.smithsonianmag.com/smart-news/how-has-roman-concrete-lasted-for-millennia-a-1900-year...
227•divbzero•13h ago•178 comments

Decoy Font

https://www.mixfont.com/experiments/decoy-font
648•ray__•1d ago•146 comments

Kimi K3: Open Frontier Intelligence

https://www.kimi.com/blog/kimi-k3
1910•vincent_s•1d ago•1121 comments

Show HN: Simulator for a custom 8-bit discreet logic computer

https://msap2.mehran.dk
6•mehrant•3d ago•0 comments

Tannakian Reconstruction

https://bartoszmilewski.com/2026/07/14/tannakian-reconstruction/
17•ibobev•3d ago•1 comments

An Engineer's Guide to USB Typе-С (2024)

https://www.ti.com/lit/eb/slyy228/slyy228.pdf?ts=1759892558029
257•gregsadetsky•1w ago•53 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?