frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Linux 7.3 improves performance when running out of vRAM

https://pixelcluster.dev/VRAM-Overcommit/
220•flaburgan•4h ago•58 comments

Rethinking Database Programming

https://acadia.engineering/blog/rethinking-database-programming
87•honungsburk•4h ago•37 comments

How Bluesky draws its logo on screenshots

https://timmarinin.net/2026/bluesky-screenshots/
562•gavide•13h ago•367 comments

GPT-5.6 Sol Pricing Cut by 50%

https://openrouter.ai/openai/gpt-5.6-sol
494•Topfi•14h ago•308 comments

Google buys crashed airline Spirit's data at auction, because AI

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

Quake Shareware, a CD-ROM just a little too full

https://fabiensanglard.net/quake_shareware_cd/index.html
379•shdon•13h ago•161 comments

IBM Simon (1994): the original smartphone, explained in its own ad [video]

https://www.youtube.com/watch?v=xoTFywZpPcc
46•kls0e•2d ago•13 comments

Fairphone 6 and PostmarketOS working main camera

https://catcrafts.net/posts/fairphone-6-postmarketos-working-main-camera
228•pizzaiolo•13h ago•49 comments

Ranking the Most Brilliantly Colored Birds with Data

https://moultano.wordpress.com/2026/08/14/fairly-ranking-the-most-brilliant-birds/
37•moultano•2d ago•3 comments

A Preview of DuckDB v2.0

https://duckdb.org/2026/08/17/duckdb-20-highlights
656•ibotty•22h ago•116 comments

Israel creates fake think tank in likely attempt to dupe AI chatbots

https://responsiblestatecraft.org/israel-influence-chatgpt/
616•DeepLogin•15h ago•374 comments

The Benchmarkpocalypse

https://danluu.com/benchpocalypse/
127•cyndunlop•9h ago•36 comments

Exercise intensity modulates interorgan communication and is associated with

https://www.cell.com/cell-reports-medicine/fulltext/S2666-3791%2826%2900405-2?_returnURL=https%3A...
49•newsomix9xl•7h ago•16 comments

Olo (Color)

https://en.wikipedia.org/wiki/Olo_(color)
468•inigyou•6d ago•84 comments

AI-Generated GitHub Copilot “Autofix” Allowed Compromise of Snowflake's Jira

https://www.wiz.io/blog/red-agent-snowflake-copilot-cicd-bug
383•galnagli•21h ago•147 comments

As Wisconsin cities flee Flock, its shared camera network loses value

https://arstechnica.com/tech-policy/2026/08/as-wisconsin-cities-flee-flock-its-shared-camera-netw...
9•xoa•25m ago•1 comments

GPU Offload in Rust: Portable, Safe, and Fast

https://arxiv.org/abs/2608.13759
225•linggen•17h ago•47 comments

Finger: Social network that never died

https://en.andros.dev/blog/54572bc7/finger-the-1971-social-network-that-never-died/
22•andros•4h ago•8 comments

Shattered skeleton is first confirmed death from trebuchet

https://www.science.org/content/article/shattered-skeleton-scottish-castle-first-confirmed-death-...
79•hermitcrab•4d ago•52 comments

An update on leaving Gmail for Fastmail

https://moddedbear.com/an-update-on-leaving-gmail-for-fastmail/
259•neogodless•18h ago•162 comments

The Road to MS-DOS 2.0

https://nemanjatrifunovic.substack.com/p/the-road-to-ms-dos-2
83•whobre•6d ago•36 comments

GPT 5.6 Sol is the best "vision" model OpenAI ever released

https://blog.roboflow.com/openai-gpt-5-6/
345•plurby•23h ago•163 comments

Repair Cafe – Fix Your Broken Items

https://www.repaircafe.org/
132•rglover•12h ago•25 comments

How to disable or avoid intrusive AI

https://www.librarian.net/notoai/
309•ColinWright•21h ago•184 comments

Sun Clock

https://sunclock.net/
244•Gecko4072•19h ago•81 comments

Climbing Guide as a Shared Infrastructure

https://irz.fr/en/articles/openclimbing-open-guide-en/
25•zbycz•2d ago•10 comments

Judge sets framework for Nine PBS to retrieve archival data

https://current.org/2026/08/judge-sets-framework-for-nine-pbs-to-retrieve-archival-data/
172•qingcharles•19h ago•66 comments

AI;DR (AI; Didn't Read)

https://www.rickmanelius.com/p/aidr-ai-didnt-read
928•mooreds•16h ago•566 comments

Los Puesteros, solitary men who look after ranches and livestock in Patagonia

https://www.newyorker.com/culture/photo-booth/the-lonely-men-at-the-end-of-the-world
153•bookofjoe•17h ago•55 comments

India has paved the way for charging merchants a fee on UPI transactions

https://www.bbc.com/news/articles/c8xnwqe00v1o
161•monkey_monkey•16h ago•201 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?