frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Aluminum foil (2021)

https://dernocua.github.io/notes/aluminum-foil.html
146•firephox•3h ago•50 comments

AMD Ryzen AI Halo – $4k AI Dev Kit

https://www.lttlabs.com/articles/2026/07/06/amd-ryzen-ai-halo
100•LabsLucas•2h ago•77 comments

Road to Elm 1.0

https://elm-lang.org/news/faster-builds
224•wolfadex•5h ago•90 comments

Fable 5 On Vending-Bench: Misbehaving, With Plausible Deniability

https://andonlabs.com/blog/fable5-vending-bench
109•optimalsolver•4h ago•58 comments

Egypt Is Building a New Nile

https://www.theb1m.com/video/egypt-is-building-a-new-nile
23•geox•2d ago•1 comments

Real-time map of Great Britain's rail network

https://www.map.signalbox.io
319•scrlk•7h ago•123 comments

Stealth robotics startup (YC S26) is hiring principal engineers (Palo Alto)

1•david-venegas•52m ago

Clojure 1.13 adds support for checked keys

https://clojure.org/news/2026/07/02/clojure-1-13-alpha1
116•FelipeCortez•3d ago•22 comments

1k Words: A Writing Contest

https://writingclub.world/1picture1000words
44•surprisetalk•1h ago•16 comments

Show HN: Pulpie – Models for Cleaning the Web

https://usefeyn.com/blog/pulpie-pareto-optimal-models-for-cleaning-the-web/
17•snyy•1h ago•2 comments

Resetting Xbox

https://news.xbox.com/en-us/2026/07/06/resetting-xbox/
118•dijksterhuis•3h ago•84 comments

Should DayQuil Be Legal?

https://www.theargumentmag.com/p/should-dayquil-be-legal
61•paulpauper•1h ago•69 comments

Multilingual experience linked to delayed aging

https://fens2026.abstractserver.com/program/#/details/presentations/5474
43•bookofjoe•2h ago•36 comments

OfficeCLI: Office suite for AI agents to read and edit Microsoft Office files

https://github.com/iOfficeAI/OfficeCLI
4•maxloh•37m ago•0 comments

Introduction to Genomics for Engineers

https://learngenomics.dev/docs/biological-foundations/cells-genomes-dna-chromosomes/
164•yreg•4d ago•25 comments

When 2+2=5

https://arstechnica.com/security/2026/06/ai-browsers-can-be-lulled-into-a-dream-world-where-guard...
51•noashavit•3d ago•20 comments

What Emily Bender meant by "stochastic parrots"

https://spectrum.ieee.org/stochastic-parrot
110•digital55•2h ago•133 comments

Nintendo announces new product revisions in Europe with replaceable batteries

https://www.nintendo.com/en-gb/Support/Nintendo-Switch-2/Information-about-upcoming-battery-relat...
196•akyuu•4h ago•133 comments

Show HN: I Built LangGraph for Swift

https://github.com/christopherkarani/Swarm
10•christkarani•2h ago•2 comments

Kani: A Model Checker for Rust

https://arxiv.org/abs/2607.01504
5•Jimmc414•1h ago•0 comments

Apricot Computers: An underrated British brand

https://dfarq.homeip.net/apricot-computers-an-underrated-british-brand/
55•giuliomagnifico•5d ago•18 comments

Building relationships with customers through support didn't turn out as hoped

https://www.uncommonapps.nyc/p/castro-podcasts-things-i-got-wrong-support
275•dabluck•15h ago•167 comments

Do you need separate systems when you already have Postgres?

https://postgresisenough.dev/
96•b-man•2h ago•59 comments

Lost and Found

https://walzr.com/lost-and-found
27•walz•16h ago•6 comments

Amazon will stop accepting new customers for Mechanical Turk

https://techcrunch.com/2026/07/05/amazon-will-stop-accepting-new-customers-for-mechanical-turk/
105•bookofjoe•4h ago•30 comments

Why low-latency Java still requires discipline?

https://chronicle.software/insights/blogs/why-low-latency-java-still-requires-discipline
58•theanonymousone•4h ago•31 comments

Tom Colicchio's Final Service

https://www.esquire.com/preview/food-drink/restaurants/a71774153/tom-colicchio-craft-closing/
6•NaOH•2h ago•0 comments

DOJ Closing Abbott Labs Case Spurs Wider Corporate Crime Retreat

https://news.bloomberglaw.com/us-law-week/doj-closing-abbott-labs-case-spurs-wider-corporate-crim...
72•petethomas•2h ago•17 comments

Electric anti-aircraft interceptor drone breaks world air speed record at 434mph

https://www.tomshardware.com/tech-industry/drones/electric-drone-breaks-world-air-speed-record-at...
42•LorenDB•2h ago•26 comments

The Complete Homemade Juggling Beanbag Guide

https://www.joshuaclifton.com/juggle/
58•mrauha•4d ago•6 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?