frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

7.1 Earthquake in Japan

https://www.data.jma.go.jp/multi/quake/quake_detail.html?eventID=20260728163528&lang=en
221•krembo•2h ago•52 comments

Our position on open-weights models

https://www.anthropic.com/news/position-open-weights-models
925•surprisetalk•12h ago•1343 comments

About the security content of macOS Tahoe 26.6

https://support.apple.com/en-us/128067
20•andor•41m ago•8 comments

What Even Are Microservices?

https://var0.xyz/posts/what-even-are-microservices.html
13•tuxie_•34m ago•18 comments

A $500 RL fine-tune of a 9B open model beat frontier models on catalog review

https://fermisense.com/when-machines-take-the-wheel/
196•ilreb•8h ago•52 comments

Ars Astronomica – English translations of rare Hebrew and Latin astronomy texts

https://arsastronomica.com/
64•sweisman•5h ago•10 comments

Benchmarking Opus 5 on SlopCodeBench

https://github.com/humanlayer/advanced-context-engineering-for-coding-agents/blob/main/benchmarki...
298•dhorthy•11h ago•66 comments

How to Survive Boiling Water

https://taxa.substack.com/p/how-to-survive-boiling-water
17•cainxinth•3d ago•1 comments

Vehicle Motion Cues

https://support.apple.com/guide/iphone/iphone-comfortably-riding-a-vehicle-iph55564cb22/ios
123•Austin_Conlon•9h ago•55 comments

Watching Go's new garbage collector move through the heap

https://theconsensus.dev/p/2026/07/19/observing-gos-garbage-collector-old-and-new.html
229•matheusmoreira•3d ago•27 comments

Using an open model feels surprisingly good

https://matthewsaltz.com/blog/using-an-open-model-feels-surprisingly-good/
283•msaltz•7h ago•107 comments

Neutrino-1 8B

https://www.fermionresearch.com/models/neutrino-8b/
84•handfuloflight•5h ago•26 comments

PyTorch: A Reference Language

https://docs.pytorch.org/devlogs/compiler/2026-07-25-pytorch-a-reference-language/
32•matt_d•5h ago•3 comments

RTX 2080 Ti Memory Upgrade to 22 GB

https://gpusolutions.net/rbservices/graphics-card-upgrade/
113•wslh•3d ago•72 comments

TWC Classics

https://twcclassics.com/
11•stefanpie•5d ago•1 comments

Programming Languages Are Authoring Tools for Platforms

https://www.makonea.com/en-US/blog/programming-languages-are-authoring-tools-for-platforms
21•jdw64•3d ago•4 comments

Kimi K3 Now Available via Telnyx Inference API

https://telnyx.com/release-notes/kimi-k3-telnyx-inference
89•fionaattelnyx•11h ago•42 comments

DConf 2026 in London

https://dconf.org/2026/index.html
91•teleforce•11h ago•41 comments

EYG: A Programming Language for Humans

https://crowdhailer.me/2026-06-08/a-programming-language-for-humans/
69•crowdhailer•8h ago•39 comments

Show HN: Yap – OSS on-device voice dictation for macOS with no model to download

https://github.com/FrigadeHQ/yap
72•pancomplex•15h ago•26 comments

Launch HN: Rise Reforming (YC S26) – Turning Waste Gases into Valuable Chemicals

https://www.rise-reforming.com
73•george_rose25•14h ago•31 comments

C/C++ projects packaged for Zig

https://github.com/allyourcodebase
63•jcbhmr•11h ago•35 comments

Ray tracing massive amounts of animated geometry using tetrahedral cages

https://gpuopen.com/learn/ray-tracing-massive-amounts-animated-geometry/
107•LorenDB•4d ago•13 comments

Self-contained highly-portable Python distributions

https://gregoryszorc.com/docs/python-build-standalone/main/
146•jcbhmr•15h ago•31 comments

Some combinatorial applications of spacefilling curves

https://www2.isye.gatech.edu/~jjb/research/mow/mow.html
55•shraiwi•2d ago•6 comments

Paged Out #9 [pdf]

https://pagedout.institute/download/PagedOut_009.pdf
242•laurensr•20h ago•26 comments

Securing Services with Rootless Containers

https://blog.coderspirit.xyz/blog/2026/07/06/securing-services-with-rootless-containers/
99•speckx•4d ago•28 comments

How real are real numbers? (2004)

https://arxiv.org/abs/math/0411418
81•surprisetalk•18h ago•59 comments

A Dying Art: The last of the morticians

https://harpers.org/archive/2026/08/a-dying-art-john-semley-mortuary-sciences-competition/
34•Petiver•4d ago•3 comments

Netflix employee fired for sharing personal details in retreat trust exercise

https://nypost.com/2026/07/26/us-news/netflix-exec-goes-ballistic-after-being-fired-for-stunning-...
341•softwaredoug•11h ago•323 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?