frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Why Book Corners won't sync contributions back to OpenStreetMap

https://www.andreagrandi.it/posts/why-book-corners-wont-sync-contributions-back-to-openstreetmap/
25•pizzaiolo•1h ago•11 comments

CP/M-386 – CP/M for 386 protected mode, derived from CP/M‑68K

https://github.com/johnsonjh/cpm386
11•TMWNN•57m ago•1 comments

Karpathy’s Pelican

https://twitter.com/karpathy/status/2083749667410727319
434•delichon•21h ago•337 comments

Autoregressive Language Model on the 6502 Processor

https://mattbeton.com/blog/bitnet-6502.html
55•nmstoker•2d ago•5 comments

Show HN: Kakehashi – Experimental userspace to run macOS binaries on Linux ARM

https://github.com/wie-project/kakehashi
178•vlad_kalinkin•9h ago•38 comments

RFC 9851: TLS 1.2 is in Feature Freeze

https://www.rfc-editor.org/rfc/rfc9851.html
5•Jimmc414•12m ago•0 comments

Note-Taking and Personal Knowledge Management

https://unattributed.cc/note-taking-and-personal-knowledge-management
126•surprisetalk•5d ago•36 comments

Developers are attached to tools because tools encode trust

https://stackoverflow.blog/2026/07/29/developers-are-attached-to-tools-because-tools-encode-trust/
149•HieronymusBosch•4d ago•71 comments

Read the Novels and Forget Everything Else

https://hedgehogreview.com/web-features/thr/posts/read-the-novels-and-forget-everything-else
50•samclemens•2d ago•24 comments

Show HN: Mu – Tools for Agents

https://github.com/micro/mu
28•asim•3h ago•8 comments

The Computational Theory of Mind (2015)

https://plato.stanford.edu/entries/computational-mind/
25•cyanregiment•3h ago•8 comments

Show HN: Make your Framework 12 sound like a creaky door

https://github.com/ArcaEge/creakwork12
49•arcaege•5h ago•5 comments

Show HN: Isopolis – isometric pixel map of SF

https://sf.isopolis.city/
7•nuwandavek•49m ago•2 comments

Show HN: NixOS-DGX-Spark – Nix and NixOS on the DGX Spark

https://github.com/graham33/nixos-dgx-spark
95•graham33•8h ago•28 comments

Playing with Georgia

https://mighil.com/playing-with-georgia
7•surprisetalk•4d ago•4 comments

TinyNES Review – A Super Niche NES Console

https://blog.lon.tv/2023/02/05/tinynes-review-a-super-niche-nes-console/
33•throwoutway•5h ago•4 comments

Californians' data deletion requests, DROP, become enforceable Aug. 1

https://www.nbcsandiego.com/nbc-7-responds-2/californians-data-deletion-requests-drop-become-enfo...
81•MilnerRoute•3h ago•29 comments

F*: A general-purpose proof-oriented programming language

https://fstar-lang.org/
155•ducktective•13h ago•67 comments

My personal AI benchmark: "Generate an SVG of a frog with a Habsburg jaw."

https://frogs.vaguespac.es/
101•thebigship•5h ago•45 comments

Twenty Years of RISC OS Open

https://www.riscosopen.org/news/articles/2026/06/20/twenty-years-of-risc-os-open
151•AlexeyBrin•12h ago•29 comments

Show HN: ssh ssh.place

https://ssh.place
3•jeninh•1h ago•0 comments

Sharing an X11 Server Across Hosts with FamilyWild

https://dobrowolski.dev/article/sharing-an-x-server-across-hosts-with-familywild/
34•shirozuki•5h ago•10 comments

Show HN: Shitty – fast terminal. Memory-unsafe and faster than yours

https://github.com/pg83/shitty
83•pshirshov•2h ago•65 comments

A tool for finding the causes of unstable Python tests

https://github.com/mgaitan/pytest-leak-finder
10•pomponchik•3d ago•0 comments

The Myth of Snow Leopard

https://www.rubenerd.au/the-myth-of-snow-leopard/
43•speckx•7h ago•39 comments

When transit passes were designed by hand (2022)

https://letterformarchive.org/news/milwaukee-transit-passes/
99•nate•2d ago•28 comments

Flock – Chilling Effects: Long Island's Emerging Open-Air Prison

https://www.11971.com/
34•mediaeater•4h ago•9 comments

Great Question (YC W21) Is Hiring Senior Demand Gen Manager

https://www.ycombinator.com/companies/great-question/jobs/YutDxyf-senior-demand-generation-manager
1•nedwin•13h ago

'Crush this lady': how eBay harassment campaign led to $56M payout

https://www.ft.com/content/06ec1b03-d4af-40cf-b12a-4ba5a410f6d2
178•JumpCrisscross•6h ago•83 comments

Fasttracker II clone in C using SDL 2

https://16-bits.org/ft2.php
116•andsoitis•4d ago•45 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?