frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

5k menus from the New York Public Library’s Buttolph Collection (1880-1920)

https://pudding.cool/2026/06/menu-story/
267•xbryanx•5h ago•69 comments

GitHub – librepods-org/librepods: AirPods liberated from Apple's ecosystem

https://github.com/librepods-org/librepods
33•rbanffy•1h ago•2 comments

I used Claude Code to get a second opinion on my MRI

https://antoine.fi/mri-analysis-using-claude-code-opus
169•engmarketer•3h ago•263 comments

Tokenmaxxing is dead, long live tokenmaxxing

https://12gramsofcarbon.com/p/agentics-tech-things-tokenmaxxing
61•theahura•3h ago•72 comments

The Boeing 747 begins its final descent

https://www.theatlantic.com/magazine/2026/07/boeing-747-retirement/687304/
70•dbl000•3d ago•62 comments

Working around dragons with the Lemote Yeeloong laptop and OpenBSD

http://oldvcr.blogspot.com/2026/06/working-around-dragons-with-lemote.html
57•zdw•3h ago•9 comments

Semgrep: GLM 5.2 beats Claude in our Cyber Benchmarks

https://semgrep.dev/blog/2026/we-have-mythos-at-home-glm-52-beats-claude-in-our-cyber-benchmarks/
19•jms703•2h ago•4 comments

Computer-Aided Language Development in Nonspeaking Children (1968) [pdf]

https://archive.org/details/colby1968-computer-aided-language-development-in-non-speaking-children
8•dang•1h ago•0 comments

The cost YAGNI was never about

https://newsletter.kentbeck.com/p/the-cost-yagni-was-never-about
56•kiyanwang•1h ago•33 comments

Examining circuit boards from the Space Shuttle's I/O Processor

https://www.righto.com/2026/06/space-shuttle-io-processor-boards.html
60•pwg•3h ago•12 comments

TOP500 at ISC'26: We Have a New Number 1 – By George Cozma

https://chipsandcheese.com/p/top500-at-isc26-we-have-a-new-number
5•rbanffy•26m ago•1 comments

Show HN: Zanagrams

https://zanagrams.com/
94•pompomsheep•4h ago•30 comments

Daisugi, the Japanese technique of growing trees out of other trees (2020)

https://www.openculture.com/2020/10/daisugi.html
67•MaysonL•3h ago•20 comments

Ford rehires 'gray beard' engineers after AI falls short

https://techcrunch.com/2026/06/28/ford-rehires-gray-beard-engineers-after-ai-falls-short/
25•rbanffy•28m ago•8 comments

A way to exclude sensitive files issue still open for OpenAI Codex

https://github.com/openai/codex/issues/2847
155•pikseladam•7h ago•99 comments

The curious case of the disappearing Polish S (2015)

https://aresluna.org/the-curious-case-of-the-disappearing-polish-s/
183•colinprince•7h ago•53 comments

The MUMPS 76 Primer – anniversary edition

https://github.com/rochus-keller/MUMPS/blob/main/docs/MUMPS_Primer.adoc
59•Rochus•7h ago•26 comments

Show HN: Appaca – AI Workspace for Operators

https://www.appaca.ai/
5•susros•2d ago•6 comments

Historical memory prices 1960-2026

https://dam.stanford.edu/memory-prices.html
19•vga1•1h ago•5 comments

Show HN: DRM-Free Books

https://frequal.com/Perspectives/DrmFreeAuthors.html
28•TeaVMFan•3h ago•9 comments

EU to legislate about Chat Control behind closed doors

https://www.patrick-breyer.de/en/double-threat-to-private-communications-undemocratic-chat-contro...
455•NeutralForest•5h ago•262 comments

More evidence is consistent with possible ancient life on Mars (2025)

https://www.cbc.ca/radio/quirks/more-evidence-of-life-on-mars-but-still-no-life-1.7649645
38•pseudolus•8h ago•52 comments

Programmable Probabilistic Computer with 1M p-bits

https://arxiv.org/abs/2606.25313
26•rbanffy•4h ago•0 comments

The KIDS Act would require age checks to get online

https://www.eff.org/deeplinks/2026/06/kids-act-would-require-age-checks-get-online
162•bilsbie•8h ago•180 comments

Michigan bill would bar employers from requiring after-hours coms with workers

https://www.cbsnews.com/detroit/news/workplace-boundaries-act-employees-after-hours/
189•cebert•5h ago•134 comments

Marfa Public Radio Puts You to Sleep

https://www.marfapublicradio.org/podcast/marfa-public-radio-puts-you-to-sleep
371•reaperducer•17h ago•113 comments

Linux Kills Strncpy

https://smist08.wordpress.com/2026/06/25/linux-kills-strncpy/
16•ingve•2d ago•5 comments

Trade, merchants, and the lost cities of the Bronze Age (2019) [pdf]

https://keremcosar.uvacreate.virginia.edu/publications/BCCH-BronzeAgeTrade-qje.pdf
68•NaOH•5d ago•62 comments

DLL that was not present in memory despite not being formally unloaded

https://devblogs.microsoft.com/oldnewthing/20260625-00/?p=112467
111•ibobev•10h ago•39 comments

The US Used to Demand the Best Tech. Now We Ban It

https://www.pcmag.com/opinions/the-us-used-to-demand-the-best-tech-now-we-ban-it
14•mwexler•56m 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?