frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Leaking YouTube creators' private videos

https://javoriuski.com/post/youtube
139•javxfps•1h ago•47 comments

Google Books (or similar) all book scans – $200k bounty (2025)

https://software.annas-archive.gl/AnnaArchivist/annas-archive/-/work_items/234
61•Cider9986•1h ago•10 comments

Potential session/cache leakage between workspace instances or consumer accounts

https://github.com/anthropics/claude-code/issues/74066
206•chatmasta•4h ago•94 comments

Explanation of everything you can see in htop/top on Linux (2019)

https://peteris.rocks/blog/htop/
257•theanonymousone•6h ago•30 comments

No more than 100 000 faint satellites should orbit Earth

https://www.eso.org/public/news/eso2607/
12•Breadmaker•46m ago•0 comments

Curveball

https://mightyburger.net/projects/curveball/
22•toilet•1h ago•2 comments

BareMetal RAM Dumper – Bare-metal x86 tool for Cold Boot Attack experiments

https://github.com/pIat0n/BareMetal-RAM-Dumper
5•liffik•26m ago•1 comments

Windows CE Dreamcast Community Edition (wince-dc)

https://github.com/maximqaxd/wince-dc
38•msephton•3h ago•4 comments

Astrophysicists Puzzle over Webb’s New Universe

https://www.quantamagazine.org/astrophysicists-puzzle-over-webbs-new-universe-20260702/
150•jnord•8h ago•87 comments

Designing DB partitions you don't have to babysit

https://explainanalyze.com/p/designing-partitioning-you-dont-have-to-babysit/
24•rtolkachev•3d ago•1 comments

Finland's last analogue landline phones go silent after 150 years

https://www.euronews.com/next/2026/06/30/finlands-last-analogue-landline-phones-go-silent-after-1...
24•ohjeez•1h ago•0 comments

Plein Air

https://art.joonas.wtf/
5•bookofjoe•1h ago•0 comments

Maybe you should learn something

https://www.marginalia.nu/log/a_135_learn/
342•tylerdane•14h ago•166 comments

Neural Render Proxies for Interactive and Differentiable Lighting

https://studios.disneyresearch.com/2026/07/01/neural-render-proxies-for-interactive-and-different...
9•tobr•2d ago•0 comments

Meta data center water discharges suspended for contaminating water supply

https://www.tomshardware.com/tech-industry/data-centers/cheyenne-suspends-data-center-fill-and-fl...
34•sensanaty•1h ago•4 comments

Breaking the Bird Barrier: Scientist Decodes Zebra Finch Language

https://www.freepressjournal.in/education/breaking-the-bird-barrier-scientist-decodes-zebra-finch...
53•yyyk•3d ago•11 comments

The Vespa at 80

https://www.cbc.ca/news/world/vespa-italy-postwar-design-9.7252641
108•cf100clunk•3d ago•93 comments

Postgres data stored in Parquet on S3: LTAP architecture explained

https://www.databricks.com/blog/lakebase-ltap-rethinking-database-storage
128•andrenotgiant•3d ago•42 comments

The bottleneck might be the air in the room

https://blog.mikebowler.ca/2026/07/03/co2-and-decision-making/
655•gslin•11h ago•363 comments

Costco is the anti-Amazon

https://phenomenalworld.org/analysis/the-anti-amazon/
522•bookofjoe•1d ago•506 comments

Night Witches – all-female Soviet aviator regiment WW2

https://en.wikipedia.org/wiki/Night_Witches
64•gverrilla•3d ago•25 comments

Leanstral 1.5: Proof abundance for all

https://mistral.ai/news/leanstral-1-5/
324•programLyrique•19h ago•91 comments

Performance per dollar is getting faster and cheaper

https://www.wafer.ai/blog/glm52-amd
323•latchkey•20h ago•128 comments

What ORMs have taught me: just learn SQL (2014)

https://wozniak.ca/blog/2014/08/03/1/index.html
104•ciconia•3d ago•126 comments

Rob Pike – 'Concurrency Is Not Parallelism' [video]

https://vimeo.com/49718712
23•jruohonen•1h ago•11 comments

Mir Books – Books from the Soviet Era

https://mirtitles.org
141•clmul•3d ago•70 comments

The Reports of Jim Carrey's Death Are a Failure Mode

https://tane.dev/2026/07/the-reports-of-jim-carreys-death-are-a-failure-mode/
25•taubek•6h ago•26 comments

Giant trees have no trouble pumping water to top branches: new research

https://news.exeter.ac.uk/faculty-of-environment-science-and-economy/giant-trees-have-no-trouble-...
249•hhs•19h ago•110 comments

Steam Controller Auto-Charge – pilot to magnetic charging puck using CV

https://github.com/FossPrime/Steam-Controller-Auto-Charge
187•zdw•19h ago•47 comments

Jamesob's guide to running SOTA LLMs locally

https://github.com/jamesob/local-llm
388•livestyle•1d ago•175 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?