frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Qwen 3.0 Image Pro

https://www.qwencloud.com/models/qwen-image-3.0-pro
102•theanonymousone•2h ago•31 comments

Discovery Loop

https://www.discoveryloop.com/
44•xtreak29•41m ago•7 comments

Google DeepMind CEO Demis Hassabis is stepping down

https://www.axios.com/2026/08/05/google-deepmind-demis-hassabis-ai
203•ot•55m ago•119 comments

Oracle Just Halved Its Always Free ARM Limits

https://www.cnelecar.com/blog/oracle-always-free-arm-limits-cut-2026/
64•iplaypc•2h ago•42 comments

Aristotle quotes on virtue, knowledge, and happiness

https://www.campion.edu.au/blog/top-25-aristotle-quotes-on-virtue-knowledge-and-happiness/
88•teleforce•2h ago•26 comments

Cloudflare OS: an open platform for agents, apps, and work

https://blog.cloudflare.com/cloudflare-os/
282•speckx•3h ago•158 comments

Cops Used Flock to Track a Man Across State Lines for a Pretextual Weed Search

https://www.404media.co/cops-used-flock-to-track-a-man-across-state-lines-to-create-pretext-to-se...
188•cdrnsf•1h ago•74 comments

Launch HN: HyperProbe (YC S26) – Agents that do read-only debugging in prod

https://www.hyperprobe.co
5•shailendraht•13m ago•0 comments

The next chapter of our AI momentum

https://blog.google/company-news/inside-google/message-ceo/next-chapter-ai-momentum/
19•colesantiago•55m ago•12 comments

The "Disability Dongle": Why Silicon Valley Hates Me and You

https://sightlessscribbles.com/disability-dongle/
45•calcifer•2h ago•14 comments

Jeff Dean leaving Alphabet

https://www.nytimes.com/2026/08/05/technology/google-researchers-ai-startup.html
134•louiereederson•56m ago•22 comments

Western Sahara

https://en.wikipedia.org/wiki/Western_Sahara
26•brudgers•18h ago•7 comments

The Entropy of a Markov Chain

https://chillphysicsenjoyer.substack.com/p/the-entropy-of-a-markov-chain
50•surprisetalk•3h ago•2 comments

The Valley of Webhooks

https://weli.dev/blog/the-valley-of-webhooks/
19•weli•1h ago•7 comments

Discovery of a multicomponent alloy forged by the Hiroshima atomic blast

https://www.science.org/doi/10.1126/sciadv.aeg8299
37•_____k•5d ago•12 comments

Building an Advanced Agentic Harness

https://data4sci.com/blog/building-an-advanced-agentic-harness
52•Anon84•3h ago•25 comments

Painting with Gaussians

https://yogthos.net/posts/2026-08-03-splat-painter.html
40•yogthos•3h ago•4 comments

Rubin Observatory's first LSST Camera release: 500k galaxies in the COSMOS field

https://rubinobservatory.org/news/rubin-new-window-cosmos-field
34•MarcoDewey•2h ago•1 comments

Civilian plane crash in New Mexico tied to military GPS blocking

https://www.wired.com/story/a-civilian-plane-crashed-in-new-mexico-was-the-militarys-tech-to-blame/
330•dzdt•5h ago•163 comments

Jeff Dean Leaving Google

https://twitter.com/JeffDean/status/2085034604172603724
27•bifftastic•46m ago•0 comments

Faster Than Ninja

https://build2.org/blog/faster-than-ninja.xhtml
47•elasticdog•3h ago•15 comments

Position: LLMs Can't Jump

https://openreview.net/challenge?redirect=%2Fforum%3Fid%3DklU4737opt
174•theanonymousone•5h ago•122 comments

Intelligence Is Not the Main Bottleneck

https://www.writingruxandrabio.com/p/intelligence-is-not-the-main-bottleneck
81•rruxandra_l•2h ago•58 comments

Stateless MCP has recaptured my interest

https://simonwillison.net/2026/Jul/31/stateless-mcp/
342•tosh•4d ago•195 comments

TIME Is Serving AI Bots a Different Website, with Ads Built In

https://www.vincentschmalbach.com/time-serves-ai-bots-a-different-website/
170•vincent_s•4h ago•69 comments

TSON – A JSON superset with immutable, hash-pinned schemas

https://tson.io/
38•andrewjneumann•2h ago•31 comments

What is distributed Key Generation (DKG)?

https://stoffelmpc.com/stoffel-blog/what-is-distributed-key-generation-(dkg)
4•badcryptobitch•4d ago•0 comments

The Law of Jante (2015)

https://www.theparisreview.org/blog/2015/02/11/the-law-of-jante/
8•NaOH•22h ago•0 comments

Fed's Kashkari says 'now is the time to start slowly moving' rates up

https://www.cnbc.com/2026/08/05/feds-kashkari-says-now-is-the-time-to-start-slowly-moving-rates-u...
33•mapping365•1h ago•39 comments

Energizing a vacuum-tube flip-flop module from a 1948 IBM system

https://www.righto.com/2026/07/ibm-604-trigger-tube-module.html
23•Jimmc414•5d ago•3 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?