frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Parley: Federated, decentralised chat that speaks plain IRC

https://git.mills.io/prologic/parley
33•davidcollantes•50m ago•10 comments

Owed a billion dollars in Nvidia stock

https://colo.to/nvidia-stock-narrative.html
763•Eric_Gullichsen•9h ago•314 comments

Footguns with Postgres "at time zone 'UTC'"

https://bookofrevenue.com/blog/6ab81e9a97a13f0001f7e4e1/postgres-at-time-zone-u-does-not-do-what-...
45•birdculture•1d ago•26 comments

Thinking fast and slow in AI: The role of metacognition (2021)

https://arxiv.org/abs/2110.01834
114•teleforce•7h ago•38 comments

Ember-1

https://fireworks.ai/blog/ember-1
486•gmays•17h ago•221 comments

When did Google get so weird?

https://sancho.bearblog.dev/google-weird/
1370•sancho-panza•15h ago•743 comments

Nissan's third generation e-POWER powertrain

https://www.nissan-global.com/EN/INNOVATION/TECHNOLOGY/ARCHIVE/E_POWER_GEN3/
77•mroche•8h ago•95 comments

AI companies in race to demonstrate their model most threatening to humanity

https://thecivilian.co.nz/2026/09/27/ai-companies-in-fierce-arms-race-to-demonstrate-their-model-...
23•ljewalsh•2h ago•1 comments

SpaceX's Starship launching to orbit for first time ever today

https://www.space.com/space-exploration/launches-spacecraft/spacexs-starship-megarocket-launching...
57•geox•2h ago•9 comments

Prompting Claude Opus 5.5

https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/prompting-claude-opus-5-5
117•Michelangelo11•3h ago•113 comments

Malleable software: Restoring user agency in a world of locked-down apps (2025)

https://www.inkandswitch.com/essay/malleable-software/
103•evakhoury•16h ago•48 comments

Functional Mechanical Sympathy [video]

https://www.youtube.com/watch?v=jSHmDnUZCm8
40•surprisetalk•2d ago•2 comments

Made by Mechanical Means

https://felixrieseberg.com/made-by-mechanical-means/
34•cocoflunchy•4h ago•7 comments

Alan Kay's answer to “Did the ENIAC have a BIOS”?

https://www.quora.com/Did-the-ENIAC-have-a-BIOS/answer/Alan-Kay-11
143•midnightfish•15h ago•42 comments

Self-Hosting on the Dark Web

https://david.alvarezrosa.com/posts/self-hosting-on-the-dark-web/
217•mooreds•15h ago•83 comments

Lunar Terminator Paradox

https://notes.secretsauce.net/notes/2026/09/27_lunar-terminator-paradox.html
88•dima55•14h ago•56 comments

Guitar amp and effects pedal built on the Waveshare ESP32-S3-Touch-AMOLED-2.06

https://github.com/dashersw/coyopedal
93•arbayi•2d ago•44 comments

Three Days in August: What a DDoS Attack Exposed in Our Network

https://nine.ch/en/blog/ddos-attack-august-2026-postmortem/
6•nine_ch•2h ago•1 comments

Don't couple your Go code to GitHub

https://iain.rocks/blog/dont-couple-your-go-code-to-github
255•birdculture•18h ago•116 comments

The state of SIMD in Rust in 2026

https://shnatsel.github.io/state-of-simd-rust-2026/
163•verdagon•2d ago•39 comments

Deterministic Concurrency [video]

https://www.youtube.com/watch?v=25x0UuSCKuU
47•surprisetalk•2d ago•4 comments

In an $80 motel room, a discovery to shed light on the origins of life

https://www.nytimes.com/2026/09/26/science/motel-science-discovery.html
254•danso•20h ago•94 comments

Show HN: Lofi Cities – Pixel-art city nights with browser-generated lofi

https://loficities.com/
258•safaelmali•16h ago•112 comments

37,500 border drawings: a map of the world as people remember it

https://www.habibicode.org/thedrawnworld
13•nicocarsui•2h ago•8 comments

Replacing the old battery on rechargeable bike lights

https://jvns.ca/blog/2026/09/27/replacing-the-old-battery-on-rechargeable-bike-lights/
177•surprisetalk•21h ago•98 comments

What I did at Recurse Center

https://thill.me/2026/09/11/what-i-did-at-rc.html
108•bingden•16h ago•34 comments

Imp is a full port of DSPy to the BEAM

https://github.com/deepfates/imp
78•mpweiher•15h ago•7 comments

Reading’s Bayeux Tapestry

https://diamondgeezer.blogspot.com/2026/09/readings-bayeux-tapestry.html
52•zeristor•2d ago•20 comments

Previously unheard recordings of John Coltrane, captured by Frank Tiberi

https://www.jazzwise.com/content/news/john-coltrane-centenary-celebrations-see-impulse-records-re...
94•gregsadetsky•2d ago•33 comments

There is more to code review than (automatable) detection

https://www.adaptivecapacitylabs.com/2026/08/24/there-is-more-to-code-review-than-automatable-det...
142•utiiiD•1d ago•89 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?