frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Job: Head of Stonehenge

https://www.english-heritage.org.uk/about/our-people/careers-with-us/job-search/default-job-page/...
80•mooreds•1h ago•33 comments

Apple reveals new AI architecture built around Google Gemini models

https://www.macrumors.com/2026/06/08/apple-reveals-new-ai-architecture/
443•unclefuzzy•9h ago•362 comments

Siri AI

https://www.apple.com/apple-intelligence/
483•0xedb•10h ago•424 comments

Old'aVista – The most powerful guide to the old Internet

https://oldavista.com/
31•abnercoimbre•12h ago•2 comments

xAI is looking more like a datacentre REIT than a frontier lab

https://martinalderson.com/posts/xais-new-rental-business/
480•martinald•13h ago•367 comments

Show HN: Performative-UI – A react component library of design tropes

https://vorpus.github.io/performativeUI/
855•lizhang•14h ago•162 comments

MiMo-v2.5-Pro-UltraSpeed: 1T model with 1000 tokens per second

https://mimo.xiaomi.com/blog/mimo-tilert-1000tps
522•gainsurier•13h ago•377 comments

GoGoGrandparent (YC S16) is hiring Back end Engineers

https://www.ycombinator.com/companies/gogograndparent/jobs/2vbzAw8-backend-engineer
1•davidchl•1h ago

EU-banned pesticides found in rice, tea and spices

https://www.foodwatch.org/en/eu-banned-pesticides-found-in-rice-tea-and-spices
282•john-titor•12h ago•105 comments

Apple Core AI Framework

https://developer.apple.com/documentation/coreai/
238•hmokiguess•9h ago•55 comments

Looking Forward to Postgres 19: Query Hints

https://www.pgedge.com/blog/looking-forward-to-postgres-19-query-hints
92•jjgreen•3d ago•16 comments

Show HN: Gitdot – a better GitHub. Open-source, written in Rust

https://gitdot.io/
191•baepaul•11h ago•150 comments

Passing DBs through continuations

https://remy.wang/blog/cps.html
17•remywang•2d ago•0 comments

Why are cells small?

https://burrito.bio/essays/what-limits-a-cells-size
124•mailyk•9h ago•54 comments

Ask HN: What are tools you have made for yourself since the advent of AI?

200•aryamaan•10h ago•350 comments

How much do amd64 microarchitecture levels help in Go?

https://lemire.me/blog/2026/06/06/how-much-do-amd64-microarchitecture-levels-help-in-go/
18•zdw•1d ago•1 comments

Surveillance is not safety: A statement on the UK's latest threat to privacy [pdf]

https://signal.org/blog/pdfs/2026-06-08-uk-surveillance-is-not-safety.pdf
464•g0xA52A2A•9h ago•176 comments

FrontierCode

https://cognition.ai/blog/frontier-code
128•streamer45•8h ago•23 comments

Ask HN: Why hasn't there been a real competitor to Ticketmaster yet?

114•mdni007•11h ago•97 comments

I'm building a parallel internet, and it's called The Thinnernet

https://inavoyage.blogspot.com/2026/06/im-building-parallel-internet-and-its.html
60•initramfs•9h ago•60 comments

Launch HN: Intuned (YC S22) – Build and run reliable browser automations as code

https://intunedhq.com
104•fkilaiwi•15h ago•44 comments

Apple bets cheaper AI will woo small developers

https://techcrunch.com/2026/06/08/apple-bets-cheaper-ai-will-woo-small-developers/
39•jbernardo95•7h ago•17 comments

Confidential submission of draft S-1 to the SEC

https://openai.com/index/openai-submits-confidential-s-1/
320•hackerBanana•7h ago•240 comments

AI is slowing down

https://www.wheresyoured.at/ai-is-slowing-down/
451•crescit_eundo•12h ago•473 comments

A Survey of Inlining Heuristics

https://bernsteinbear.com/blog/inlining-heuristics/
13•ibobev•4d ago•0 comments

1worldflag: A blue dot on a transparent background

https://1worldflag.com/
180•davidbarker•1d ago•153 comments

Anti-social: It's fads, not friends, which now dominate social media feeds

https://www.bbc.com/worklife/article/20260520-how-social-media-ceased-to-be-social
594•1vuio0pswjnm7•16h ago•426 comments

Federal judge blocks H1B visa $100K fee

https://www.alaskasnewssource.com/2026/06/08/federal-judge-blocks-h1-b-visa-100k-fee/
113•naturalmovement•4h ago•194 comments

Games Between Programs: The Ruliology of Competition

https://writings.stephenwolfram.com/2026/06/games-between-programs-the-ruliology-of-competition/
17•andromaton•3d ago•0 comments

OCaml Onboarding: Introduction to the Dune build system

https://ocamlpro.com/blog/2025_07_29_ocaml_onboarding_introduction_to_dune/
148•andrewstetsenko•4d ago•21 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?