frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

The Free Market Lie: Why Switzerland Has 25 Gbit Internet and America Doesn't

https://stefan.schueller.net/posts/the-free-market-lie/
160•talonx•59m ago•79 comments

Virginia bans sale of geolocation data

https://www.hunton.com/privacy-and-cybersecurity-law-blog/virginia-bans-sale-of-geolocation-data
641•toomuchtodo•8h ago•109 comments

CarPlay Is Additive

https://www.caseyliss.com/2026/7/2/carplay-is-additive-you-dolts
145•sprawl_•4h ago•187 comments

crustc: entirety of `rustc`, translated to C

https://github.com/FractalFir/crustc
203•Philpax•6h ago•34 comments

Right to Local Intelligence

https://righttointelligence.org/
106•thoughtpeddler•5h ago•41 comments

Is the iPhone birth control? Causal evidence from AT&T's 2007-2011 monopoly [pdf]

https://www.nber.org/system/files/working_papers/w35310/w35310.pdf
29•Terretta•17h ago•9 comments

Since Linux 6.9, LUKS suspend stopped wiping disk-encryption keys from memory

https://mathstodon.xyz/@iblech/116769502749142438
433•IngoBlechschmid•13h ago•192 comments

Reality has a surprising amount of detail (2017)

https://johnsalvatier.org/blog/2017/reality-has-a-surprising-amount-of-detail
196•vinhnx•5d ago•71 comments

14× faster embeddings: how we rebuilt the ONNX path in Manticore

https://manticoresearch.com/blog/onnx-embeddings-speedup/
7•snikolaev•1h ago•0 comments

Exapunks (2018)

https://www.zachtronics.com/exapunks/
254•yu3zhou4•10h ago•84 comments

An American Privacy Emergency

https://scottaaronson.blog/?p=9902
239•flowercalled•5h ago•81 comments

PeerTube is a free, decentralized and federated video platform

https://github.com/Chocobozzz/PeerTube
558•doener•17h ago•260 comments

Podman v6.0.0

https://blog.podman.io/2026/07/introducing-podman-v6-0-0/
438•soheilpro•14h ago•174 comments

Mystery identity of 'Green Boots' climber is finally solved after DNA test

https://www.dailymail.com/news/article-15943905/Mystery-identity-Green-Boots-climber-macabre-land...
81•FireBeyond•6h ago•41 comments

How to ask for help from people who don't know you

https://pradyuprasad.com/writings/how-to-ask-for-help/
455•FigurativeVoid•15h ago•68 comments

Immich 3.0

https://github.com/immich-app/immich/discussions/29439
261•hashier•15h ago•121 comments

Superpowers 6

https://blog.fsck.com/2026/06/15/Superpowers-6/
112•seahorseemoji•2d ago•46 comments

Perform DFU Restores on Apple Silicon Macs with Macvdmtool (2021)

https://www.bkurtz.io/posts/macvdmtool/
11•gregsadetsky•3d ago•1 comments

Postgres transactions are a distributed systems superpower

https://www.dbos.dev/blog/co-locating-workflow-state-with-your-data
143•KraftyOne•10h ago•61 comments

The short leash AI coding method for beating Fable

https://blog.okturtles.org/2026/07/short-leash-ai-method/
90•Riseed•10h ago•109 comments

Great Salt Lake Tracker – Grow the Flow

https://growtheflowutah.org/laketracker/
82•cfowles•9h ago•31 comments

FoundationDB's Flow – Bringing Actor-Based Concurrency to C++11

https://apple.github.io/foundationdb/flow.html
50•sourdecor•14h ago•7 comments

This is my attempt to get Vulkan going on NetBSD

https://github.com/segaboy/vulkan-netbsd
93•segaboy81•10h ago•19 comments

Every AI Visibility Tool Is Lying to You

https://canonry.ai/blog/ai-visibility-tools-are-lying
4•arberx•1h ago•0 comments

Show HN: zkGolf – Competitive optimization of formally verified circuits

https://zk.golf/
51•rot256•13h ago•6 comments

EFF letter to FTC on X consent order [pdf]

https://www.eff.org/deeplinks/2026/06/eff-and-allies-xs-ftc-petition-waive-privacy-violation-orde...
125•Terretta•9h ago•46 comments

Claude-real-video - any LLM can watch a video

https://github.com/HUANGCHIHHUNGLeo/claude-real-video
107•cortexosmain•10h ago•31 comments

Lightning Memory-Mapped Database Manager (LMDB) 1.0

http://www.lmdb.tech/doc/
73•radiator•9h ago•41 comments

Cowboys, Frontiersmen, Settlers, Townspeople, Cityfolk

https://huntersoftwareconsulting.com/posts/2026-06-28-company-phase-changes/
3•mooreds•3d ago•0 comments

Show HN: Inkwell – An RSS reader for e-ink devices

https://kendal.codeberg.page/inkwell/
44•imkendal•13h ago•5 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?