frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Powerless F1 drivers frustrated by Bahrain F1 software glitch

https://www.motorsport.com/f1/news/horrible-totally-unacceptable-powerless-f1-drivers-frustrated-...
138•llm_nerd•3h ago•69 comments

Run Qwen 3.8 Flash Next (125B) on consumer hardware (RTX 4090) at 100T/s

https://github.com/Niko1221/Strata
666•snehesht•16h ago•309 comments

In the wake of closure, a digital archive of animated materials appears online

https://filmstories.co.uk/news/tippett-studios-in-the-wake-of-its-closure-a-digital-archive-of-an...
73•rdmuser•7h ago•7 comments

Nearly 200 People Under Observation After Irkutsk Lab Worker Dies from Plague

https://www.themoscowtimes.com/2026/10/02/nearly-200-people-under-observation-after-irkutsk-lab-w...
118•ericmay•2h ago•68 comments

Infidel goes wild

https://blog.zarfhome.com/2026/10/infidel-goes-wild
101•tobr•1d ago•14 comments

A 40ms Go garbage collector pause caused by swap

https://frn.sh/go-gc/
22•shellpipe•3h ago•6 comments

A browser-native classic Visual Basic VB6 IDE

https://wieslawsoltes.github.io/VB6/
134•wiso•10h ago•48 comments

The Tao of Backup

http://www.taobackup.com/index.html
74•vntok•2d ago•15 comments

Turn off Apple Intelligence on macOS 27 and get its disk space back

https://github.com/omlahore/RemoveMacAI
459•privacyisntdead•9h ago•284 comments

Improper redaction reveals Google Data Center water and electricity usage

https://www.1011now.com/2026/09/30/more-questions-than-answers-about-lincolns-google-data-center-...
310•sensanaty•9h ago•426 comments

Fixed Points and Strike Mandates

https://pvk.ca/Blog/2012/02/19/fixed-points-and-strike-mandates/
7•luu•4d ago•1 comments

Quantitative Finance with OCaml

https://qcaml.com/index.html
49•leonry•2d ago•9 comments

Self-hosted HTTP tunnels with SSH and Nginx

https://vincent.bernat.ch/en/blog/2026-http-over-ssh
97•renehsz•6h ago•29 comments

Tell HN: Bob Cringely has died

840•paveworld•1d ago•181 comments

Watson Jr. memo about CDC 6600 (1963)

https://www.computerhistory.org/revolution/supercomputers/10/33/62
33•mooreds•1d ago•18 comments

Homa: The end of TCP for AI clusters [video]

https://www.youtube.com/watch?v=eZ8WWZzoaR0
65•signa11•9h ago•29 comments

Xray-core concealed a certificate verification bypass vulnerability

https://github.com/net4people/bbs/issues/672
67•timbill•11h ago•8 comments

How to scale intent, quality, and artistry with AI [video]

https://www.youtube.com/watch?v=GLvFTMtw4Jk
70•simonjgreen•20h ago•17 comments

Show HN: Glashütte Trash Clock – A 30-minute pendulum clock made from trash

https://niklasroy.com/gtc/
176•r0r0•2d ago•26 comments

Demystifying Tufte's data-ink ratio

https://tuftesrazor.scienceux.org/
20•s4074433•2d ago•5 comments

What is going on with ceiling fans

https://mcmansionhell.com/post/829127919552151552/what-is-going-on-with-ceiling-fans
258•colinprince•4d ago•234 comments

Results from the ASIC puzzle

https://blog.janestreet.com/asic-puzzle-results/
81•eru•2d ago•40 comments

Show HN: AI search for every photo and every frame of video on macOS

https://github.com/allenv0/SCM
146•allenleee•19h ago•66 comments

Bill Draper has died

https://www.nytimes.com/2026/09/30/technology/william-draper-dead.html
98•bookofjoe•16h ago•27 comments

Interview with Chicken Scheme Maintainer Sjamaan/Peter Bex

https://alexalejandre.com/interviews/peter-bex/
25•veqq•2d ago•5 comments

Why don't more developers “use the platform”?

https://nolanlawson.com/2026/10/03/why-dont-more-developers-use-the-platform/
288•vinhnx•1d ago•299 comments

A map of every lighthouse

https://mapped.earth/lighthouses/world
178•karakoram•2d ago•76 comments

The AI industry is booming. Women are getting left behind

https://www.theguardian.com/technology/2026/oct/04/women-ai-jobs-inequality
5•shadow28•19m ago•2 comments

cp: -r or -R?

https://movq.de/blog/postings/2026-09-30/0/POSTING-en.html
112•zdw•4d ago•103 comments

Surely you have ultra-wideband radios on your bins too?

https://sjg.io/writing/binrange-have-you-actually-put-the-bins-out/
142•simonjgreen•1d ago•78 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?