frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

OpenTTD 16.0-Beta1

https://www.openttd.org/news/2026/06/25/openttd-16-0-beta1
98•untilted•3h ago•12 comments

Previewing GPT‑5.6 Sol: a next-generation model

https://openai.com/index/previewing-gpt-5-6-sol/
969•minimaxir•14h ago•601 comments

WordStar: A Writer's Word Processor (1996)

https://www.sfwriter.com/wordstar.htm
69•droidjj•4h ago•26 comments

Why does kinetic energy increase quadratically, not linearly, with speed? (2011)

https://physics.stackexchange.com/questions/535/why-does-kinetic-energy-increase-quadratically-no...
215•ProxyTracer•9h ago•101 comments

IBM MCGA Gate Array Reverse Engineering

https://github.com/schlae/IBM_MCGA
18•userbinator•2h ago•4 comments

U.S. allows Anthropic to release Mythos AI to ‘trusted’ US organizations

https://www.semafor.com/article/06/27/2026/us-releases-powerful-anthropic-model-mythos-to-some-us...
395•bobrenjc93•9h ago•396 comments

Fusion Programming Language

https://fusion-lang.org/
53•efrecon•2d ago•21 comments

MicroVMs: Run isolated sandboxes with full lifecycle control

https://aws.amazon.com/blogs/aws/run-isolated-sandboxes-with-full-lifecycle-control-aws-lambda-in...
317•justincormack•3d ago•182 comments

Show HN: Hacker News on a train station-style flip board

https://popflame.quickish.space/hn-flipboard/
60•PaybackTony•7h ago•10 comments

Hellishly Slow Level 13 Deflate Compression

https://kirill.korins.ky/articles/hellishly-slow-level-13-deflate-compression/
47•zX41ZdbW•4d ago•11 comments

SCC Technical Assistance Program

https://nerocam.com/scc_tap.asp
12•luu•2d ago•1 comments

Anatomy of a Failed (Nation-State?) Attack

https://grack.com/blog/2026/06/25/dissecting-a-failed-nation-state-attack/
34•signa11•5h ago•7 comments

U.S. government will decide who gets to use GPT-5.6

https://www.washingtonpost.com/technology/2026/06/26/openai-says-us-government-will-vet-users-its...
987•alain94040•13h ago•1043 comments

Show HN: DBOSify – Drop-in Temporal replacement built on Postgres

https://github.com/dbos-inc/dbosify-py
55•KraftyOne•2d ago•8 comments

Om

https://daringfireball.net/2026/06/om
328•throw0101a•8h ago•15 comments

AI in mathematics is forcing big questions

https://spectrum.ieee.org/ai-in-mathematics
108•rbanffy•9h ago•76 comments

We can still stop California's 3D printer surveillance scheme

https://www.eff.org/deeplinks/2026/06/we-can-still-stop-californias-3d-printer-surveillance-scheme
369•hn_acker•10h ago•124 comments

Building apps using TanStack Start

https://lovable.dev/blog/building-apps-using-tanstack-start
11•nadis•3d ago•0 comments

Linux on Older Hardware: The Complete Revival Guide

https://www.fosslinux.com/158206/linux-on-older-hardware-revival-guide.htm
4•tapanjk•2d ago•0 comments

The gap between open weights LLMs and closed source LLMs

https://blog.doubleword.ai/frontier-os-llm
185•kkm•10h ago•156 comments

A C++ implementation of a fast hash map and hash set using hopscotch hashing

https://github.com/Tessil/hopscotch-map
89•gjvc•10h ago•15 comments

Ultrasound imaging of the brain

https://alephneuro.com/blog/ultrasound-brain
271•rossant•20h ago•111 comments

Show HN: Smart model routing directly in Claude, Codex and Cursor

https://github.com/workweave/router
165•adchurch•15h ago•96 comments

What Is a Nomogram and Why Would It Interest Me?

https://lefakkomies.github.io/pynomo-doc/introduction/introduction.html#what-is-a-nomogram-and-wh...
110•Eridanus2•14h ago•19 comments

Hightouch (YC S19) Is Hiring

https://hightouch.com/careers#open-positions
1•joshwget•10h ago

Foreign funds help make housing unaffordable: research

https://news.mccombs.utexas.edu/research/foreign-funds-help-make-housing-unaffordable/
62•hhs•8h ago•17 comments

Pre-Modern Armies for Worldbuilders, Part III: Paying for It

https://acoup.blog/2026/06/26/collections-pre-modern-armies-for-worldbuilders-part-iii-paying-for...
91•jfoucher•13h ago•16 comments

A Tiny Compiler for Data-Parallel Kernels

https://healeycodes.com/a-tiny-compiler-for-data-parallel-kernels
39•healeycodes•1d ago•4 comments

Making Sense of Proof by Contradiction [pdf]

https://www.foster77.co.uk/Foster,%20Scottish%20Mathematical%20Council%20Journal,%20Making%20sens...
35•surprisetalk•3d ago•12 comments

Long Wave radio era set to end with switch-off

https://www.bbc.com/news/articles/c74yn7v7k4qo
79•speckx•12h ago•33 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?