frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

OpenAI unveils its first custom chip, built by Broadcom

https://techcrunch.com/2026/06/24/openai-unveils-its-first-custom-chip-built-by-broadcom/
299•jamdesk•3h ago•222 comments

Wikipedia Workers to Seek Union Recognition

https://www.cwu.org/press_release/wikipedia-workers-to-seek-union-recognition/
83•addshore•2h ago•30 comments

RubyLLM: A Ruby framework for all major AI providers

https://rubyllm.com/
284•doener•6h ago•42 comments

We’re making Bunny DNS free

https://bunny.net/blog/were-making-bunny-dns-free/
763•dabinat•12h ago•244 comments

PR spam today looks like email spam in the early 2000s

https://www.greptile.com/blog/prs-on-openclaw
112•dakshgupta•6h ago•81 comments

Zero-Downtime Deployments with Docker Compose – No Kubernetes Required

https://statusdude.com/blog/zero-downtime-docker-compose
13•canto•34m ago•14 comments

Qualcomm to Acquire Modular

https://www.reuters.com/business/qualcomm-buy-ai-startup-modular-2026-06-24/
12•timmyd•7h ago•17 comments

There are a few things that I look back on as my mistakes in the early days

https://twitter.com/ID_AA_Carmack/status/2069799283369345247
415•shadowtree•4h ago•207 comments

Big AI labs are hiring philosophers

https://www.economist.com/science-and-technology/2026/06/24/why-big-ai-labs-are-hiring-so-many-ph...
57•Brajeshwar•4h ago•41 comments

Show HN: Nub – A Bun-like all-in-one toolkit for Node.js

https://github.com/nubjs/nub
162•colinmcd•6h ago•41 comments

Stealing Is a Skill

https://ben-mini.com/2026/stealing-is-a-skill
173•bewal416•7h ago•109 comments

Krea 2: SOTA open-weights 12B image model

https://www.krea.ai/blog/krea-2-technical-report
269•mattnewton•1d ago•34 comments

Thomann takes legal action against Fender

https://www.thomann.de/blog/en/inside/thomann-takes-legal-action-against-fender/
114•Audiophilip•1h ago•59 comments

Show HN: LookAway, a Mac break reminder that knows when not to interrupt

https://lookaway.com
18•_kush•7h ago•0 comments

Running Windows Games on a Hobby OS with Wine

https://astral-os.org/posts/2026/04/03/wine-on-astral.html
81•avaliosdev•6h ago•23 comments

Pull request limits are cutting down the noise

https://github.blog/open-source/maintainers/how-pull-request-limits-are-cutting-down-the-noise/
50•ingve•5d ago•35 comments

I rewrote PostHog's SQL parser, 70x faster, while barely looking at the code

https://posthog.com/blog/sql-parser
67•robbie-c•2h ago•33 comments

A Practical Guide to SSH Tunnels: Local and Remote Port Forwarding

https://labs.iximiuz.com/tutorials/ssh-tunnels
214•signa11•4d ago•46 comments

I taught a bucket to speak Git

https://www.tigrisdata.com/blog/objgit/
63•xena•4h ago•16 comments

Show HN: Monolisa v3 – a typeface for developers and creatives

https://www.monolisa.dev/
133•bebraw•2d ago•41 comments

Computer use in Gemini 3.5 Flash

https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-computer-use-...
92•swolpers•3h ago•56 comments

Self-Harness: Harnesses That Improve Themselves

https://arxiv.org/abs/2606.09498
51•jonnonz•2d ago•2 comments

GitHub shouldn't be a dependency for publishing Rust on crates.io

https://infosec.exchange/@mttaggart/116806641273303255
29•speckx•1h ago•8 comments

Genuinely, my all-time favourite image: Mamenchisaurus hochuanensis

https://svpow.com/2026/06/04/genuinely-my-all-time-favourite-image-mamenchisaurus-hochuanensis/
71•surprisetalk•2d ago•26 comments

Crawling BitTorrent DHTs for Fun and Profit [pdf]

https://www.usenix.org/legacy/event/woot10/tech/full_papers/Wolchok.pdf
5•dgellow•3d ago•1 comments

Why eval startups fail (2025)

https://thomasliao.com/eval-startups
83•jxmorris12•1d ago•51 comments

Show HN: peerd – AI agent harness that runs entirely in your browser

https://github.com/NotASithLord/peerd
48•NotASithLord•1d ago•16 comments

Too many R packages: CRAN is inundated with submissions

https://rworks.dev/posts/too-many-R-packages/
84•ionychal•9h ago•71 comments

For Most of the World, Open-Source AI Is the Only Way Forward

https://techstrong.ai/articles/for-most-of-the-world-open-source-ai-is-the-only-way-forward/
175•CrankyBear•6h ago•117 comments

Exploiting vulnerabilities in Johnson and Johnson web apps

https://eaton-works.com/2026/06/24/jnj-webapp-hacks/
24•EatonZ•4h ago•0 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?