frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Introducing System One Models and Jev

https://typesafe.ai/blog/introducing-system-one-models-and-jev
1136•albelfio•11h ago•336 comments

Apple Reference Image: A New Approach for Verified Photography

https://security.apple.com/blog/apple-reference-image/
154•imwally•4h ago•84 comments

Show HN: An e-ink frame that hears birds and draws them as 1800s illustrations

https://github.com/arnegiacomo/fugleramme
1505•arnemunthekaas•17h ago•193 comments

Show HN: I made a flight simulator, except you're just a passenger

https://inflightsimulator.com
104•rkotcher•1d ago•50 comments

Negativland, Culture Jamming, and the Art of Making Something New

https://blog.archive.org/2026/09/11/negativland-culture-jamming-and-the-art-of-making-something-new/
65•bananaboy•3h ago•17 comments

Datamimic – don't let your coding agent invent its own test world

https://github.com/rapiddweller/datamimic
16•ake2l•1h ago•2 comments

An update on Wayback Machine access

https://blog.archive.org/2026/09/15/an-update-on-wayback-machine-access/
487•ChrisArchitect•12h ago•250 comments

Gemini 3.8 Live and 3.8 Live Extended Thinking

https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-3-8-live-gemini-3-...
374•leumon•12h ago•242 comments

Recreating Voodoo Graphics and a Late-1990s Gaming PC on an FPGA

https://nand2mario.github.io/posts/2026/zsst-voodoo/
96•zdw•7h ago•20 comments

German Rheinmetall open-sources its Battlesuite connected weapon system protcol

https://rheinmetall.github.io/onboardapi-documentation/9.10.0/index.html
182•summarity•9h ago•60 comments

Doing Everyone Else's Job

https://yosefk.com/blog/doing-everyone-elses-job.html
21•luu•1d ago•14 comments

Building a Linux GPU Driver for the M4 Mac Mini in One Month

https://codyho.dev/blog/gpu-driver/
247•ADevWithAnIdea•11h ago•152 comments

An interactive world map of the stories cultures have told

https://originmap.sunnyguha.com/
29•momentmaker•2d ago•0 comments

We got admin access to Baseten's production GitHub

https://www.strix.ai/blog/baseten-harbor-github-pat-takeover
264•bearsyankees•12h ago•142 comments

Saving Jet Fuel

https://tech.marksblogg.com/scikit-decide-openap-optimal-flight-planning.html
78•marklit•7h ago•33 comments

Learning to solve hard problems in RL for LLMs by never giving up

https://mnoukhov.github.io/posts/ngu/
79•natolambert•11h ago•0 comments

Jean-Pierre Serre turns 100

https://mathshistory.st-andrews.ac.uk/Biographies/Serre/
128•jzox•9h ago•21 comments

Stay discoverable in search while disallowing AI training

https://blog.cloudflare.com/accountable-mixed-use-ai-crawlers/
51•djfergus•4h ago•32 comments

Chopping up books when they're physically too big

https://attainablefelicity.mattkirkland.com/20260915/cut-up-your-books.html
156•matt_kirkland•11h ago•146 comments

Show HN: Capsule – Single-file web apps that save their data into SQLite

https://withcapsule.app/
315•bashtian•16h ago•127 comments

A single firm is behind OpenAI, Anthropic, and Meta hacking scandals

https://www.effort.news/irregular
581•yusufozkan•1d ago•197 comments

Let's make quality the norm again

https://www.forbrukerradet.no/short-life/
360•ingve•20h ago•374 comments

WangNet – 1.8 MB, zero-dependency Numberwang adjudication in 11 languages

https://github.com/GraafHenk/numberwang
134•Liogra123•11h ago•48 comments

Suspected sabotage causes major Netherlands rail disruption

https://www.bbc.com/news/articles/c8ly49w9g1edo
466•choult•20h ago•413 comments

Piezoelectric effect in polycrystalline diamond membranes

https://www.science.org/doi/10.1126/sciadv.aea8318
3•westurner•2d ago•1 comments

Most people prefer traditional architecture

https://www.worksinprogress.news/p/do-people-prefer-traditional-architecture
309•alihm•1d ago•262 comments

Sierra digital cameras on the Apple II

https://www.colino.net/wordpress/archives/2026/09/11/sierra-digital-cameras-on-the-apple-ii/
33•ibobev•2d ago•5 comments

Show HN: Pizza Bot – An inbox for AI agents that work in the background

https://github.com/pizza-bot-app/pizza-bot
46•jd_•15h ago•26 comments

The Inference Hardware Revolution of 2026

https://spectrum.ieee.org/inference-hardware-revolution
137•vinhnx•16h ago•13 comments

Jiga (YC W21) Is Hiring Product Engineer (Remote/US)

https://jiga.io/about-us/?ashby_jid=0b75d72d-c92b-4dca-8062-09d298ada0bd
1•grmmph•13h ago
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?