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/
599•jamdesk•10h ago•347 comments

Anthropic says Alibaba illicitly extracted Claude AI model capabilities

https://www.reuters.com/world/china/anthropic-says-alibaba-illicitly-extracted-claude-ai-model-ca...
154•htrp•8h ago•279 comments

LuaJIT 3.0 proposed syntax extensions

https://github.com/LuaJIT/LuaJIT/issues/1475
90•phreddypharkus•3h ago•50 comments

Ending All Respiratory Infections

https://blog.interceptfund.com/p/ending-respiratory-infections
80•EthanFantl•2h ago•30 comments

Blogging can just be stating the obvious

https://blog.jim-nielsen.com/2026/blogging-stating-the-obvious/
116•Curiositry•4h ago•45 comments

Cloudflare launched self-managed OAuth for all

https://blog.cloudflare.com/oauth-for-all/
34•terryds•1h ago•6 comments

Show HN: Write SaaS apps where users control where their data is stored

https://github.com/wolfoo2931/linkedrecords/
10•WolfOliver•5d ago•0 comments

Dostoyevsky isn't difficult

https://www.autodidacts.io/dostoyevsky-isnt-difficult/
71•surprisetalk•2d ago•61 comments

Qualcomm to Acquire Modular

https://www.reuters.com/business/qualcomm-buy-ai-startup-modular-2026-06-24/
166•timmyd•14h ago•39 comments

Mixing Visual and Textual Code

https://arxiv.org/abs/2603.15855
22•doppioandante•2h ago•2 comments

RubyLLM: A Ruby framework for all major AI providers

https://rubyllm.com/
360•doener•13h ago•60 comments

45°C cooling design cuts data center water use to near zero

https://blogs.nvidia.com/blog/liquid-cooling-ai-factories/
238•nitin_flanker•13h ago•166 comments

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

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

Computer use in Gemini 3.5 Flash

https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-computer-use-...
190•swolpers•10h ago•119 comments

GLM-5.2 is a step change for open agents

https://www.interconnects.ai/p/glm-52-is-the-step-change-for-open
151•vantareed•2d ago•90 comments

Zombie unicorns are haunting Silicon Valley

https://www.economist.com/business/2026/06/21/zombie-unicorns-are-haunting-silicon-valley
10•andsoitis•1h ago•4 comments

Optimizing [sqlx:test] rebuild time

https://kobzol.github.io/rust/2026/06/21/optimizing-sqlx-test-rebuild-time.html
4•ibobev•2d ago•0 comments

What I'm Finding About LLM Code Style and Token Costs

https://www.jimmont.com/llm-style-token-costs
17•jimmont•3h ago•7 comments

Writers and Drugs

https://lithub.com/are-writers-intrinsically-vulnerable-to-alcohol-and-drugs/
13•dang•2h ago•5 comments

15 sorting algorithms in 6 minutes (2013) [video]

https://www.youtube.com/watch?v=kPRA0W1kECg
10•akkartik•1d ago•0 comments

Bible as RAG Database

https://www.crosscanon.com/
62•jacksonastone•2h ago•35 comments

Exploring the internal representations of Pangram 3.3.2

https://www.pangram.com/pangram-space
15•krackers•2h ago•5 comments

The Xteink X4 E-Ink Reader

https://blog.omgmog.net/post/xteink-x4-e-ink-reader/
193•felixdoerp•11h ago•118 comments

Medical students are using popular research tool to pump out misleading studies

https://www.science.org/content/article/medical-students-are-using-popular-research-tool-pump-out...
5•rndsignals•1h ago•0 comments

Ask HN: Where is our profession (programmer) going?

17•syntaxbush•1h ago•10 comments

Crawling BitTorrent DHTs for Fun and Profit [pdf]

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

Elastic lays off 7% of employees

https://www.elastic.co/blog/ceo-ash-kulkarni-announcement-to-elastic-employees
160•dakrone•6h ago•144 comments

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

https://github.com/nubjs/nub
217•colinmcd•13h ago•63 comments

Matt's Script Archive: The Scripts That Reshaped the Web

https://tedium.co/2026/06/22/matts-script-archive-retrospective/
18•1317•2d ago•8 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
505•shadowtree•12h ago•252 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?