frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Ember-1

https://fireworks.ai/blog/ember-1
135•gmays•2h ago•66 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
145•danso•5h ago•56 comments

Writing Efficient C++ Code (2013)

https://asawicki.info/articles/writing_efficient_cpp_code.php
112•ibobev•1d ago•49 comments

Replacing the old battery on rechargeable bike lights

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

Show HN: TinyAIArena watch AI agents battle it out

https://tinyaiarena.com/
64•hp6•3h ago•31 comments

Oral history of John Chowning, inventor of FM synthesis [video]

https://www.youtube.com/watch?v=e1Xn3030IvM
7•Rochus•1h ago•0 comments

The Normalization of Inexplicable Failures

https://www.ihatethefuture.com/2026/09/the-normalization-of-inexplicable.html
192•pxx•4h ago•69 comments

On caring for user data: NeoVim caused Vim undo files to be deleted

https://unsung.aresluna.org/they-had-no-concept-of-a-duty-of-care-to-their-users/
297•jandeboevrie•4h ago•257 comments

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

https://loficities.com/
40•safaelmali•53m ago•7 comments

Fragment of oldest known peace treaty found in Turkey

https://www.livescience.com/archaeology/ancient-egyptians/we-have-found-traces-of-peace-thousands...
24•gmays•5h ago•5 comments

The Cartesian Hand: In-Hand Manipulation with All-Linear Fingers

https://generalroboticslab.com/cartesian_handv1
18•AareyBaba•1d ago•4 comments

John Coltrane Centenary's – Impulse Records Release the Legendary Tiberi Tapes

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

Flip Fluid on Flip Dots

https://mitxela.com/projects/flipflip
316•blutack•1d ago•21 comments

Fakecloud: Local AWS cloud emulator for integration tests

https://fakecloud.dev/
75•theanonymousone•1d ago•41 comments

Show HN: Building a Markdown editor for Mac, iOS and web

https://www.markdown.beauty/
47•thiagoperes•5h ago•29 comments

There are no "rogue" AI agents

https://eoinhiggins.substack.com/p/there-are-no-rogue-ai-agents
242•zzzeek•3h ago•177 comments

Show HN: Trail – new kind of logic game

https://trail.franzai.com/
18•franze•12h ago•7 comments

Video CDs Break Windows Explorer

https://clydesnotes.blogspot.com/2026/08/video-cds-break-windows-explorer.html
43•ClydeN•1d ago•14 comments

Kicki: A DECsystem1060 – Interim Computer Museum

https://icm.museum/blog/?p=207
7•rbanffy•1d ago•1 comments

Faster prompt lookup drafting in llama.cpp

https://jadidbourbaki.github.io/blog/prompt-lookup-llama-cpp/
35•pptadversary•23h ago•3 comments

Improving site performance by shipping more CSS

https://github.blog/engineering/architecture-optimization/improving-site-performance-by-shipping-...
69•torutofu•1d ago•56 comments

Walgit: A Git server that is one binary in front of an object store

https://github.com/rgodha24/walgithub
58•handfuloflight•1d ago•7 comments

PostmarketOS is rebranding as Nura

https://nura.eco/blog/2026/09/27/nura-rename/
117•HotGarbage•4h ago•21 comments

Go Concurrency Distilled

https://antonz.org/go-concurrency-distilled/
348•chmaynard•1d ago•147 comments

C's Flexible Integer Sizes Were Not a Design Mistake

https://pikuma.com/blog/c-integer-sizes-not-a-mistake
50•ibobev•2d ago•76 comments

Ten lines of code that changed my world

https://pixelambacht.nl/2026/ten-lines-of-code/
100•dimonomid•6h ago•29 comments

PipePipe: NewPipe hard fork implementing SponsorBlock

https://github.com/InfinityLoop1308/PipePipe
478•Qision•2d ago•262 comments

Rusty thoughts on "Parse, don't validate"

https://eli.thegreenplace.net/2026/rusty-thoughts-on-parse-dont-validate/
60•ingve•10h ago•31 comments

Show HN: A CC0 museum of retro 3D tricks you can paste into a page

https://3d-retro.com/
59•SouthWestAtlas•3d ago•10 comments

Finally, A True Blue Rose Exists

https://www.sciencenews.org/article/true-blue-rose-pigment-copigment
86•bookofjoe•1d 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?