frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Boot a Virtual iPhone via Apple's Virtualization.framework

https://github.com/Lakr233/vphone-cli
190•hentrep•6h ago•63 comments

GUIs should be fully keyboard-driven

https://ckardaris.com/blog/2026/08/28/keyboard-driven-guis.html
697•ckardaris•14h ago•337 comments

TurboKV: Insanely fast Rust key-value store

https://github.com/kingroryg/turbokv
49•rgbimbochamp•3h ago•14 comments

Htmx 4.0

https://four.htmx.org/announcements/2026-08-28-htmx-4.0.0-is-released
586•rmsaksida•16h ago•144 comments

Our decision on Cursor following its acquisition by SpaceX

https://openai.com/index/our-decision-on-cursor-following-its-acquisition-by-spacex/
287•meetpateltech•3h ago•107 comments

9th Circuit sides with states in Kalshi gambling fight

https://azmirror.com/2026/08/28/9th-circuit-sides-with-states-in-kalshi-gambling-fight-potentiall...
104•hungryhobbit•5h ago•79 comments

StemDeck, a free, open-source and local AI stem separator

https://github.com/stemdeckapp/stemdeck
53•thclpr•4h ago•12 comments

Does the Sumerian King List Align with Paleoclimate Events?

https://www.vectorian.be/articles/2026-06-07/sumerian-king-list-paleoclimate-alignment-explorer/
75•dev_l1x_be•5h ago•26 comments

U.S. sanctions against the A/I Collective

https://www.inventati.org/
540•exiguus•16h ago•519 comments

I accidentally turned LLM memory into program analysis

https://pwning.systems/posts/llm-memory-program-analysis/
78•matt_d•6h ago•14 comments

Just the rumour of a bug is enough to find an exploit these days

https://anil.recoil.org/notes/rumour-is-the-exploit
282•avsm•13h ago•102 comments

Inception-style curved map for turn-by-turn directions

https://www.orbify.eu/demo/
460•smoser•17h ago•149 comments

Monzo Stand-In

https://monzo.com/blog/tolerating-full-cloud-outages-with-monzo-stand-in
40•coffeefuel•4d ago•0 comments

PPWR lands another blow to an precarious tabletop industry

https://www.rascal.news/ppwr-lands-another-blow-to-an-already-precarious-tabletop-industry/
43•healsdata•5h ago•31 comments

Review: Chuwi's $449 Unibook laptop is a funhouse-mirror MacBook Neo

https://arstechnica.com/gadgets/2026/08/review-chuwis-449-unibook-laptop-is-a-funhouse-mirror-mac...
16•rbanffy•4d ago•5 comments

Experiments with Plotter Art

https://sometimes.digital/posts/experiments-with-plotter-art/
27•surprisetalk•4d ago•1 comments

Kumander Linux – A Linux Distro with a Windows 7 Desktop

https://www.kumander.org/
26•linuxkernal•3h ago•5 comments

Curvature Beziers: Improving on a timeless recipe

https://acko.net/blog/curvature-beziers/
99•leephillips•4d ago•11 comments

The Twelve-Factor App (2025)

https://12factor.net/
249•jxmorris12•1d ago•131 comments

Box of 300 Love Letters Showed Up, What Whimsical WWII Soldier Who Wrote Them?

https://www.smithsonianmag.com/history/this-box-of-300-love-letters-showed-up-out-of-the-blue-who...
3•gmays•4d ago•1 comments

Identifying fake cosmetics using AI

https://groverlab.org/hnbfpr/2026-08-26-ai-counterfeit-cosmetics.html
44•wgrover•7h ago•19 comments

GLM-5.3 is now open-weight

https://huggingface.co/zai-org/GLM-5.3
638•jeudesprits•14h ago•218 comments

Flyway for freeloaders, rollback implemented in Python

https://aconcan.io/blog/flyway-for-freeloaders/
4•aconcan•3d ago•0 comments

Visual Analysis of Binary Files

https://binvis.io/#/
71•vismit2000•3d ago•21 comments

Autonomous Mathematical Discovery in an Open-World Multi-Agent Environment

https://arxiv.org/abs/2608.23691
93•stephenchung•12h ago•23 comments

EasyEffects can improve laptop speaker sound quality

https://www.osnews.com/story/145883/easyeffects-should-be-part-of-every-linux-distribution-and-de...
119•birdculture•14h ago•50 comments

Processing in Memory: DRAM Is About to Do Math

https://ben3d.ca/blog/processing-in-memory
84•bhouston•2d ago•35 comments

Verschlimmbesserung: The Word Your Software Updates Need

https://geekyschmidt.com/post/2026-08-25-verschlimmbesserung/
120•speckx•15h ago•73 comments

Migrating to HTTPX2

https://github.com/openai/openai-python/blob/main/httpx2.md
190•tosh•17h ago•81 comments

Twitterwebviewer.com Service Discontinued

https://twitterwebviewer.com/?
13•nothrowaways•1h ago•2 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?