frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

I Don't Understand Quantum Physics (2018)

https://www.southampton.ac.uk/~doug/quantum_physics/index.html
114•rramadass•3h ago•79 comments

OBS Studio 33

https://github.com/obsproject/obs-studio/releases/tag/33.0.0
221•pentagrama•8h ago•71 comments

Kimi K3.1 Pro and K3.1 Pro Highspeed

https://www.kimi.ai/blog/kimi-k3-1-pro
953•Jowsey•19h ago•572 comments

Physicists trap a single antimatter particle for a month

https://www.scientificamerican.com/article/physicists-trap-a-single-antimatter-particle-for-a-month/
104•mooreds•2d ago•42 comments

Around a dozen banking apps began specifically permitting GrapheneOS

https://grapheneos.social/@GrapheneOS/117492375462459244
230•privacyishuman•11h ago•58 comments

Today, we hacked what we'd set out to hack: the iPhone

https://blog.calif.io/p/iphone
934•pavel_lishin•20h ago•605 comments

Node2Shell evolves to HTTP2Shell, blast radius affects many HTTP libs and apps

https://www.aikido.dev/blog/python-packages-vulnerable-node2shell-brotli-cve-2026-111497
53•theanonymousone•4h ago•32 comments

Appreciating the beauty of all your body's scars and scratches

https://1000awesomethings.com/2026/10/08/576-appreciating-the-beauty-of-all-your-bodys-scars-and-...
14•surprisetalk•2d ago•8 comments

Twelve years of distributed SQLite

https://philipotoole.com/twelve-years-of-distributed-sqlite/
246•otoolep•11h ago•40 comments

How to run a city builder on 16 MHz

https://larstofus.com/2025/11/16/how-to-run-a-city-builder-on-12-5-mhz/
38•rex64•2d ago•12 comments

How close can pure functional programming get to C?

https://rtfeldman.com/fp-vs-c
153•stmonty•9h ago•27 comments

Apple Music 404 Not Found

https://music.apple.com/this-url-doesnt-exist
808•frizlab•1d ago•243 comments

Local Wikipedia: Wikipedia, but only for things a half hour walk from you

https://edjefferson.com/localwiki/
1418•sohkamyung•1d ago•237 comments

AI-Assisted Paper on Z-Library Cites a TorrentFreak Article That Doesn't Exist

https://torrentfreak.com/ai-assisted-paper-on-z-library-cites-a-torrentfreak-article-that-doesnt-...
37•TangerineDream•1h ago•5 comments

Bringing uv and ty together

https://astral.sh/blog/uv-ty-integration
191•Ravencentric•3d ago•57 comments

A practical guide to AI image generation, from diffusion to agents

https://danielball.com/notes/ai_image_generation.html
128•westsmith•3d ago•36 comments

Tiling Noise – Procedural GPU Patterns

https://catlikecoding.com/godot/procedural-gpu-patterns/09-tiling-noise/
3•ibobev•2d ago•0 comments

Dessa: Conversation Model trained only on speech

https://block.xyz/dessa
412•dsr12•17h ago•152 comments

Apple Security Research Device

https://security.apple.com/research-device/
93•neom•10h ago•41 comments

The Chalk and the Airplane

https://unintendedconsequenc.es/chalk-and-the-airplane/
13•paulorlando•2d ago•0 comments

Show HN: Autonomous root for Tcl Android TV via CVE-2022-22706

https://gitlab.com/c4psu13/mali-pagecache-root
9•t20n•2h ago•0 comments

Hacker reverses Samsung TV, finds on-board AI listening OpenAI account suspended

https://www.reddit.com/r/antiai/comments/1xdv3e5/hacker_reverse_engineers_his_samsung_tv_and_finds/
265•testing22321•7h ago•78 comments

Canadians are running out of time to oppose Bill C-22

https://www.eff.org/deeplinks/2026/10/canadians-are-running-out-time-oppose-dangerous-c-22-survei...
437•hn_acker•1d ago•228 comments

CVE Tracker

https://cve.0xosprey.com/
181•Group_B•15h ago•69 comments

The Real Kevin Bacon

https://pudding.cool/2026/10/kevin-bacon/
328•xnx•3d ago•79 comments

C vs. C#: racing VLC's Gaussian blur

https://martinfinkel.com/blog/gaussian-blur-c-vs-csharp/
101•martz•3d ago•26 comments

The Quake Fan who built the map editor everybody uses

https://funcarena.com/articles/the-quake-fan-who-built-the-map-editor-everybody-uses
143•klaussilveira•2d ago•17 comments

The Best Monopoly Strategy, Tested on 300M Games [video]

https://www.youtube.com/watch?v=S_2eVAaw1UM
35•zdw•3d ago•33 comments

How Block Blast harvests its players for ad money

https://ayoships.com/breakdowns/block-blast
63•motionlessveloc•10h ago•28 comments

One Man's Pan Am 747 Replica [video]

https://www.youtube.com/watch?v=vAFwHGGfPz4
46•Teever•15h ago•4 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?