frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Organic Maps

https://organicmaps.app/
639•tosh•6h ago•187 comments

New AI tutor achieves 0.71-1.30 SD effect size in Dartmouth course [pdf]

https://intextbooks.science.uu.nl/workshop2026/files/itb26_s1s2.pdf
75•jonahbard•2h ago•44 comments

The future of Flipper Zero development

https://blog.flipper.net/future-of-flipper-zero-development/
122•croes•2h ago•14 comments

Starring the Computer

https://www.starringthecomputer.com/computers.html
118•gitowiec•3h ago•31 comments

Mr. Baby Paint and accidentally discovering a new cellular automata

https://tekstien-marginaalien-keskus.aalto.fi/residenssi/heikki/blog/004-december-2/
39•jfil•2d ago•5 comments

It's not about physical vs. digital games, it's about ownership

https://popcar.bearblog.dev/its-about-ownership/
186•popcar2•6h ago•144 comments

Introduction to Compilers and Language Design (2021)

https://dthain.github.io/books/compiler/
241•AlexeyBrin•9h ago•42 comments

Run Windows 2000 on a DEC Alpha with a new es40 fork

https://raymii.org/s/blog/Run_Windows_2000_for_Dec_Alpha_on_a_new_es40_fork.html
79•jandeboevrie•7h ago•43 comments

Installing A/UX 1.1 like it's the 90s

https://thomasw.dev/post/aux11/
31•zdw•5h ago•9 comments

You need a webring

https://shub.club/writings/2026/july/you-need-a-webring/
28•forthwall•2h ago•17 comments

Small Penis Rule

https://en.wikipedia.org/wiki/Small_penis_rule
72•chistev•1h ago•21 comments

Papa Johns Can Predict When Your Fridge Is Empty

https://www.adexchanger.com/tv/papa-johns-can-predict-when-your-fridge-is-empty/
14•WaitWaitWha•3d ago•16 comments

The great blogging collapse: What happened to 100 successful blogs?

https://danielstanica.com/posts/Great-Blogging-Collapse
111•thm•3d ago•86 comments

We Always Leave Things Unfinished

https://bigreaderbadgrades.substack.com/p/we-always-leave-things-unfinished
7•bryanrasmussen•3d ago•0 comments

Airplane Boneyards List and Map

https://airplaneboneyards.com/airplane-boneyards-list-and-map.htm
67•hyperific•1d ago•12 comments

Why DMARC's new "NP" tag can fail with DNSSEC

https://dmarcwise.io/blog/dmarc-np-incompatibility-with-dnssec
35•matteocontrini•6h ago•12 comments

Shadcn/UI now defaults to Base UI instead of Radix

https://ui.shadcn.com/docs/changelog
270•dabinat•16h ago•146 comments

Jim Keller's startup is building a factory to mass-produce small chip fabs

https://www.tomshardware.com/tech-industry/atomic-semi-rebrands-as-fab2-and-shifts-operations-to-...
47•logickkk1•2h ago•10 comments

OpenWiki: CLI that writes and maintains agent documentation for your codebase

https://github.com/langchain-ai/openwiki
69•handfuloflight•4d ago•17 comments

Taphonomic analysis reveals behavioral & tech capabilities of Homo floresiensis

https://www.science.org/doi/10.1126/sciadv.aeb7219
6•bushwart•3h ago•0 comments

Medieval-style fortifications are back in the Sahel

https://www.economist.com/middle-east-and-africa/2026/06/25/medieval-style-fortifications-are-bac...
78•andsoitis•4d ago•61 comments

The GNU Emacs Architecture: Unlocking the Core [pdf]

https://www.diva-portal.org/smash/get/diva2:2052282/FULLTEXT01.pdf
168•cenazoic•4d ago•13 comments

Web-based cryptography is always snake oil

https://www.devever.net/~hl/webcrypto
89•enz•13h ago•93 comments

Fast Software, the Best Software (2019)

https://craigmod.com/essays/fast_software/
115•ustad•13h ago•65 comments

Show HN: KiCad in the Browser

https://demo.pcbjam.com/
84•ViktorEE•9h ago•30 comments

Optimizing an algorithm that's quadratic by design

https://whatchord.earthmanmuons.com/articles/chord-ranking-performance.html
12•elasticdog•3d ago•2 comments

Pandoc Lua Filters

https://pandoc.org/lua-filters.html
130•ankitg12•2d ago•11 comments

A sociotechnical threat model for AI-driven smart home devices

https://arxiv.org/abs/2602.09239
77•dijksterhuis•4h ago•55 comments

EU Council forces Chat Control via fast-track

https://www.heise.de/en/news/Chat-Control-1-0-EU-Council-forces-messenger-scans-via-fast-track-11...
342•stavros•9h ago•193 comments

Tripadvisor AI summaries give glowing reviews to dangerous hotels

https://www.euronews.com/travel/2026/07/03/tripadvisor-ai-summaries-give-glowing-reviews-to-dange...
10•jethronethro•57m ago•3 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?