frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

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

https://github.com/Niko1221/Strata
492•snehesht•8h ago•250 comments

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

https://github.com/omlahore/RemoveMacAI
143•privacyisntdead•1h ago•66 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-...
103•sensanaty•1h ago•126 comments

A map of every lighthouse

https://mapped.earth/lighthouses/world
132•karakoram•2d ago•63 comments

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

https://www.youtube.com/watch?v=eZ8WWZzoaR0
22•signa11•1h ago•3 comments

'Neanderthals Among Us' review

https://www.historytoday.com/archive/review/neanderthals-among-us-peter-sahlins-review
41•pepys•1d ago•35 comments

I asked Claude build a physically accurate O'Neill cylinder you can walk around

https://island-three.gruberbuilds.workers.dev/
21•bilsbie•1h ago•17 comments

Results from the ASIC puzzle

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

Show HN: Build with Python – a beginner course where your code draws

https://scimigo.com/en/learn/build-with-python/01-draw-with-python
11•davidwshao•2h ago•3 comments

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

https://niklasroy.com/gtc/
147•r0r0•2d ago•19 comments

Tell HN: Bob Cringely has died

771•paveworld•20h ago•162 comments

A man who listens to whales

https://blue-continuum.com/the-man-who-listens-to-whales
7•dnetesn•2d ago•0 comments

Page Table Memory Consumption

https://frn.sh/pagetables/
19•shellpipe•3d ago•0 comments

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

https://www.youtube.com/watch?v=GLvFTMtw4Jk
25•simonjgreen•12h ago•7 comments

Declaring a bird extinct: The median wait is 36 years after the last sighting

https://birdshistory.com/how-long-to-declare-a-bird-extinct/
10•Heidi_70•22h ago•4 comments

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

https://github.com/allenv0/SCM
125•allenleee•12h ago•59 comments

Incentives in Academic Research

https://www.msoos.org/2026/10/incentives-in-academic-research/
13•zero_k•3h ago•7 comments

The evolution of effective altruism

https://www.economist.com/international/2026/10/01/how-effective-altruism-conquered-the-world
41•bazzmt•8h ago•53 comments

A Minsky machine in ncurses terminfo

https://seriot.ch/computation/terminfo/
27•beefburger•2d ago•8 comments

Bill Draper has died

https://www.nytimes.com/2026/09/30/technology/william-draper-dead.html
44•bookofjoe•9h ago•12 comments

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

https://nolanlawson.com/2026/10/03/why-dont-more-developers-use-the-platform/
263•vinhnx•17h ago•270 comments

Automating my 35mm film scanning pipeline

https://shannadige.com/blog/darkroom/
47•shannadige•1d ago•34 comments

The work by Valve's Timur Kristóf on improving old AMD GPUs on Linux

https://www.phoronix.com/news/XDC-2026-Valve-Timur-AMDGPU
443•speckx•1d ago•86 comments

What is going on with ceiling fans

https://mcmansionhell.com/post/829127919552151552/what-is-going-on-with-ceiling-fans
149•colinprince•3d ago•124 comments

cp: -r or -R?

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

Fog-Bank: Archiving the oldest webcam feed

https://fog-bank.org/net
9•rdmuser•16h ago•2 comments

Agents don't need memory, they need documentation

https://liao.gg/blog/agents-dont-need-memory
326•kmeh•1d ago•202 comments

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

https://sjg.io/writing/binrange-have-you-actually-put-the-bins-out/
122•simonjgreen•1d ago•66 comments

Emitting metadata early makes building/checking Rust up to twice as fast

https://github.com/PowderworksCode/headstart
111•knuckleheads•15h ago•30 comments

LeCun has "zero concerns" about AI wiping out humanity, recent "rogue" incidents

https://fortune.com/2026/10/01/ai-godfather-yann-lecun-has-zero-concerns-about-human-extinction-s...
362•Anon84•1d ago•660 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?