frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Turbovec – Google's TurboQuant for vector search in Rust

https://github.com/RyanCodrai/turbovec
40•fittingopposite•56m ago•8 comments

How does IKEA come up with names for its products?

https://www.ikea.com/se/en/customer-service/knowledge/articles/6f564c4d-2ccc-46de-b643-545a3948dc...
50•NaOH•52m ago•23 comments

Using the railway network as a flatbed scanner

https://philo.gay/linecam/
304•otherayden•6h ago•52 comments

Fixing a bricked Framework laptop

https://quantum5.ca/2026/08/16/fixing-bricked-amd-7040-series-framework-13-laptop-with-20-tools/
251•jp_sc•5h ago•164 comments

The Amazon tax

https://seths.blog/2026/08/the-amazon-tax/
565•herbertl•5h ago•398 comments

Cursor launches Origin, GitHub alternative

https://cursor.com/changelog/origin-code-hosting
270•tomasreimers•1d ago•216 comments

Data centers raise nearby temperatures by up to 4 degrees in Phoenix

https://asmedigitalcollection.asme.org/sustainablebuildings/article/7/2/024501/1233035/Data-Cente...
146•cwwc•1h ago•158 comments

And then the men with guns tell you to do it anyway

https://shkspr.mobi/blog/2026/08/and-then-the-men-with-guns-tell-you-to-do-it-anyway/
26•_djo_•1h ago•1 comments

Linux 7.3 improves performance when running out of vRAM

https://pixelcluster.dev/VRAM-Overcommit/
444•flaburgan•11h ago•199 comments

We've flown a radiation-blocking vest to the Moon and back, and it worked

https://arstechnica.com/science/2026/08/weve-flown-a-radiation-blocking-vest-to-the-moon-and-back...
33•rbanffy•4d ago•14 comments

Superpowers, Not Superintelligence

https://bond.now/news/superpowers-not-superintelligence
25•edbernays•2h ago•27 comments

Launch HN: machine0 (YC S26) – Persistent CPU and GPU VMs from the CLI

https://machine0.io
26•bwm•2h ago•25 comments

Python Polars Cheatsheet (based on our O'Reilly book)

https://opensource.posit.co/resources/cheatsheets/polars/
112•jeroenjanssens•5h ago•17 comments

Claude Code May–August 2026 weekly limits promotion

https://support.claude.com/en/articles/15910845-claude-code-may-august-2026-weekly-limits-promotion
214•tyre•2h ago•159 comments

Splitting a Git Commit

https://blog.gnoack.org/post/git-history-split
83•signa11•3d ago•38 comments

Teaching my kid to code with a modern MUD

https://tau.dev/2026/08/07/canon
184•andrewjanke•6d ago•50 comments

Memory prices climb 500% in 12 months

https://www.tomshardware.com/pc-components/ram/memory-prices-climb-500-percent-in-12-months-up-to...
242•haunter•1d ago•179 comments

Show HN: PantheonGPU – GPU health testing and AI workload benchmarking

https://pantheongpu.com/
4•saqibkhan1992•16m ago•0 comments

Evolve: An incremental game about evolving a civilization

https://pmotschmann.github.io/Evolve/
14•frozenseven•3d ago•5 comments

Show HN: macOS data protection keychain for Electron apps

https://github.com/biw/keychain-store
10•biwills•1h ago•0 comments

Show HN: Openleetcode – local LeetCode runner where tests live in the repo

https://github.com/therepanic/openleetcode
24•therepanic•3h ago•9 comments

Babies born under sugar rationing grew into adults with lower cancer risk

https://theconversation.com/babies-born-under-sugar-rationing-grew-into-adults-with-lower-cancer-...
177•zeristor•4h ago•37 comments

Fairphone is now officially available in the United States

https://www.fairphone.com/nl/stories/the-fairphone-gen-6-is-all-about-giving-you-more
291•Vinnl•6h ago•145 comments

Universal health coverage could save $1T and 114k lives a year: study

https://ysph.yale.edu/news-article/universal-health-coverage-could-save-one-trillion-dollars-and-...
510•karakoram•1d ago•605 comments

California's new tire efficiency rules could save drivers $1B a year

https://grist.org/transportation/californias-new-tire-efficiency-rules-could-save-drivers-1b-a-year/
89•littlexsparkee•16h ago•114 comments

Google has acquired the data of failed US airline Spirit

https://www.theregister.com/ai-and-ml/2026/08/18/google-buys-crashed-airline-spirits-data-at-auct...
511•pseudolus•8h ago•354 comments

Code-native generation of highly programmable 3D assets (2026)

https://arxiv.org/abs/2607.22738
36•baigy•4h ago•34 comments

Rethinking Database Programming

https://acadia.engineering/blog/rethinking-database-programming
205•honungsburk•11h ago•104 comments

Ask HN: GitHub employees what's going on? Why?

158•sharts•1d ago•120 comments

Diesel Margins Top $100 a Barrel to Reach Record High as Supply Crunch Grows

https://www.bloomberg.com/news/articles/2026-08-18/diesel-margins-top-100-a-barrel-to-reach-recor...
45•toomuchtodo•2h ago•16 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?