frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Fingerprints are the new cookies

https://royfish.dev/fingerprints-are-the-new-cookies
165•royfish•5h ago•73 comments

Whatever became of holography? (2011)

https://www.americanscientist.org/article/whatever-became-of-holography
96•cainxinth•4h ago•44 comments

Total Annihilation, rebuilt for modern computers

https://nanolathe.gg
416•jttnr•10h ago•178 comments

Calculus with Julia

https://jverzani.github.io/CalculusWithJuliaNotes.jl/
28•subset•1d ago•1 comments

Cartographers of North Korea (2019)

https://cartographers-nk.wonyoung.so/
208•edent•8h ago•38 comments

Tattoos you can turn on and off

https://www.livescience.com/technology/cool-chemistry-trick-allows-new-tattoos-to-turn-on-and-off
30•MortyDev•7h ago•9 comments

The gap in shared understanding of LLM capability is widening

https://twitter.com/karpathy/status/2109361546505966046
317•albertzeyer•7h ago•493 comments

Doory – Open-Source Canva

https://github.com/shaongitbd/doory
27•acley•3h ago•2 comments

Illustration Beyond Proof

https://terrytao.wordpress.com/2026/10/11/illustration-beyond-proof/
46•smilelamp•4h ago•0 comments

Terence Tao: Math 2.0 [pdf]

https://teorth.github.io/tao-web/slides/math-2-0-caltech-2026.pdf
347•Anon84•15h ago•394 comments

Vectorized CLZ and CTZ

https://purplesyringa.moe/blog/vectorized-clz-and-ctz/
25•zX41ZdbW•1d ago•2 comments

Google is illegaly cutting forest to build data centers

https://www.theguardian.com/technology/2026/oct/06/google-datacentres-finland-temporary-halt-envi...
248•heyimada•5h ago•65 comments

No portable way to detect string-to-float conversion errors in standard C

https://sebsite.pw/w/20261009-strtod.html
6•signa11•1d ago•0 comments

Passkeys are a trap

https://nonfunctional.substack.com/p/passkeys-are-a-trap-do-not-use-them
389•laurex•6h ago•216 comments

Chapter 1 of "Ways of Seeing" by John Berger (1972)

https://www.ways-of-seeing.com/ch1
92•rafael859•9h ago•14 comments

Programmable pigments: Photochromic nanoparticle inks for rewritable tattoos

https://www.cell.com/matter-light/fulltext/S3117-5848(26)00119-5
35•Bluestein•18h ago•4 comments

Local Indexing to reduce tool calling and token usage

https://tedhaley.ca/pensieve/
40•TedHaley•4h ago•8 comments

So, You’d Like To Sell Your Print Issues Of The Onion?

https://theonion.com/archivehunt/
279•mooreds•8h ago•38 comments

Recursive self-improvement through collective intelligence

https://pub.sakana.ai/mass/
81•hardmaru•5h ago•43 comments

I guess I'm using WebP now?

https://anderegg.ca/2026/10/08/i-guess-im-using-webp-now
92•Brajeshwar•2d ago•92 comments

NYC's "Click to Cancel" rule is now in effect

https://www.nyc.gov/main/click-to-cancel
395•gregsadetsky•10h ago•196 comments

500B tokens later: Letting AI agents decompile a first-person shooter

https://momo5502.com/posts/2026-10-09-game-decompilation/
184•davikr•1d ago•127 comments

Safe SIMD in Rust, even on the inside

https://shnatsel.github.io/safe-simd-in-rust-even-on-the-inside/
49•ravenical•1d ago•2 comments

HashiCorp archives the Boundary open source repo

https://github.com/hashicorp/boundary
55•vmatsiiako•4h ago•12 comments

apsw: Another Python SQLite Wrapper

https://github.com/rogerbinns/apsw
75•tosh•11h ago•15 comments

Show HN: BetterWispr – Free, open-source dictation for Mac

https://betterwispr.com/
173•kartik017•16h ago•101 comments

ClickHouse C – Talk to ClickHouse using its native binary protocol

https://github.com/ClickHouse/clickhouse-c
17•saisrirampur•5h ago•0 comments

FlowCE: Calculus on your TI-84 Plus CE

https://tommyb3ll.github.io/FlowCE/
38•jgx0•1d ago•18 comments

How I reverse engineered a commercial spatial audio effect

http://epestr.com/blog/reverse-engineering-a-commercial-spatial-audio-effect/
111•epestr•12h ago•35 comments

Valen's Memory Safety: A New Kind of Borrow Checking

https://verdagon.dev/blog/valen-group-borrowing
147•verdagon•16h ago•80 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?