frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Fable 5.1 Solves the Cyphral Distich, a 370-year-old cipher

https://www.vals.ai/blogs/fable-solves-cyphral-distich
891•u1hcw9nx•11h ago•372 comments

Spaceships (Reverse Asteroid)

https://spaceships.treybastian.com/
221•zdw•4d ago•39 comments

Registration without a phone number on Signal will use zero-knowledge proofs

https://community.signalusers.org/t/registration-without-a-phone-number/2222?page=10
244•Cider9986•11h ago•118 comments

The case against JPEG XL

https://giannirosato.com/blog/post/case-against-jxl/
149•contact9879•7h ago•198 comments

Apple's Dimensional Drawings

https://developer.apple.com/accessories/dimensional-drawings/
170•herbertl•8h ago•64 comments

Show HN: 1080p is 920px tall – 1k real browser viewports

https://screensize.net/reports/viewport-stats
6•zenpe•1h ago•4 comments

Of Gods and Languages: On "When God Spoke Greek" (2013)

https://lareviewofbooks.org/article/of-gods-and-languages-on-when-god-spoke-greek/
25•bryanrasmussen•2h ago•12 comments

Rope, twine and thread: Invisible technologies of the Stone Age

https://knowablemagazine.org/content/article/society/2026/prehistory-lost-threads
58•knowablemag•2d ago•15 comments

Julia 1.13 highlights

https://julialang.org/blog/2026/09/julia-1.13-highlights/
227•eigenspace•3d ago•20 comments

Mullenweg has returned as CEO after attempted board ouster

https://techcrunch.com/2026/09/12/automattic-confirms-mullenweg-has-returned-as-ceo-after-attempt...
143•ilamont•12h ago•199 comments

Ask HN: What are you working on? (September 2026)

161•david927•15h ago•500 comments

Why is Google still serving dodgy ads?

https://www.atomic14.com/2026/09/13/why-is-google-still-serving-dodgy-ads
795•iamflimflam1•15h ago•355 comments

OEMpocalypse: Unprivileged Android app to root on Samsung, Xiaomi, others

https://calif.io/research/oempocalypse
49•negura•6h ago•19 comments

Show HN: EterDB, a Postgres fork that makes it easy to recover from incidents

https://eterdb.com/
31•fdeth•3d ago•7 comments

The GDR and Vietnam: From Fake Coffee to Coffee Empire

https://www.katjahoyer.uk/p/the-gdr-and-vietnam-from-fake-coffee
77•NaOH•3d ago•29 comments

Flawed routers flood University of Wisconsin internet time server (2003)

https://pages.cs.wisc.edu/~plonka/netgear-sntp/
80•walrus01•12h ago•10 comments

Bad benchmarks and evals: Senior SWE-Bench, napkin math, and winter tires

https://danluu.com/exercise-7/
23•luu•2d ago•3 comments

Open-source AI and open models reading list

https://www.interconnects.ai/p/open-source-ai-reading-list
106•simonpure•8h ago•18 comments

The Malicious Use of Artificial Intelligence

https://arxiv.org/abs/1802.07228
63•rasengan0•7h ago•13 comments

Nike exits the S&P 100 after 18 years and a $200B market-cap wipeout

https://fortune.com/2026/09/08/nike-stock-plummets-sp500-market-cap-index/
115•andsoitis•6h ago•138 comments

CUDA for AMD on Windows

https://github.com/Speedstu/CUDA-for-AMD-Windows
165•chiassedu80•18h ago•86 comments

Five Words from Vanishing Fleece

https://blog.wordnik.com/five-words-from-vanishing-fleece
5•dan353hehe•2d ago•0 comments

'Coltrane' Review: Sound and Spirit

https://www.wsj.com/arts-culture/books/coltrane-review-sound-and-spirit-b2417282
8•Thevet•1d ago•1 comments

Astra and Fable still hack on simple variants of alignment evals from 2025

https://www.lesswrong.com/posts/munJKF7iWMsWJLAH2/astra-and-fable-still-hack-on-simple-variants-o...
433•Levitating•18h ago•202 comments

Necker, 1832: "An optical phænomenon on viewing a figure of a geometrical solid"

https://zenodo.org/records/1430991
29•akkartik•2d ago•7 comments

AI Robots – When will they be in our homes

https://spectrum.ieee.org/ai-robots
29•andsoitis•8h ago•19 comments

Reverse-Engineering Claude Web's MicroVM: Uncovering Anthropic's Hidden Antspace

https://aprilnea.me/en/blog/reverse-engineering-claude-code-antspace
90•rzk•3d ago•20 comments

Data collected by cars and sold to third parties

https://www.theverge.com/column/994172/your-car-is-selling-your-data
423•bookofjoe•19h ago•211 comments

Who gets to define the rules for AI?

https://cohere.com/blog/who-gets-to-define-the-rules-for-ai
37•throwworhtthrow•4h ago•29 comments

Why is privacy so hard? (2019)

https://cacm.acm.org/blogcacm/why-is-privacy-so-hard/
46•andsoitis•11h ago•55 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?