frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Half-Baked Product

https://weli.dev/blog/half-baked-product/
331•weli•4h ago•75 comments

Virginia bans sale of geolocation data

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

Right to Local Intelligence

https://righttointelligence.org/
320•thoughtpeddler•12h ago•104 comments

Wordgard: The new in-browser rich-text editor from the creator of ProseMirror

https://wordgard.net/
52•indy•3h ago•18 comments

CarPlay Is Additive

https://www.caseyliss.com/2026/7/2/carplay-is-additive-you-dolts
362•sprawl_•11h ago•485 comments

Alibaba to ban Claude Code in workplace over alleged backdoor risks, source says

https://www.reuters.com/world/china/alibaba-ban-claude-code-workplace-over-alleged-backdoor-risks...
146•nsoonhui•3h ago•100 comments

How working with a blind client revealed invisible accessibility gaps

https://iinteractive.com/resources/blog/read-only
32•fortyseven•3d ago•14 comments

crustc: entirety of `rustc`, translated to C

https://github.com/FractalFir/crustc
308•Philpax•13h ago•60 comments

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

https://mathstodon.xyz/@iblech/116769502749142438
493•IngoBlechschmid•20h ago•209 comments

The Safari MCP server for web developers

https://webkit.org/blog/18136/introducing-the-safari-mcp-server-for-web-developers/
123•coloneltcb•10h ago•28 comments

Podman v6.0.0

https://blog.podman.io/2026/07/introducing-podman-v6-0-0/
559•soheilpro•22h ago•223 comments

Reality has a surprising amount of detail (2017)

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

Gun Mistakes in Fiction Writing: Handgun Edition

https://www.swiftsilentdeadly.com/blog/gun-mistakes-in-fiction-writing-handgun-edition
37•bushwart•1h ago•45 comments

Quake in 13 Kilobytes (2021)

https://js13kgames.com/games/q1k3
59•mortenjorck•6d ago•7 comments

Q&A with Micron's VP and GM of Memory

https://morethanmoore.substack.com/p/q-and-a-with-microns-vp-and-gm-of
12•zdw•2d ago•5 comments

Commodore 64 Basic for PostgreSQL

https://thombrown.blogspot.com/2026/07/load-plcbmbasic81-commodore-64-basic.html
14•hans_castorp•3h ago•5 comments

Exapunks (2018)

https://www.zachtronics.com/exapunks/
302•yu3zhou4•17h ago•103 comments

Immich 3.0

https://github.com/immich-app/immich/discussions/29439
471•hashier•22h ago•231 comments

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

https://manticoresearch.com/blog/onnx-embeddings-speedup/
66•snikolaev•8h ago•10 comments

The Beauty of Tautologies

https://scottsumner.substack.com/p/the-beauty-of-tautologies
3•surprisetalk•2d ago•2 comments

Underwater Suit-Wearing Cyborg Insect Capable of Diving and Terra-Aqua Travel

https://www.nature.com/articles/s41467-026-74235-1
53•gscott•3d ago•21 comments

The short leash AI coding method for beating Fable

https://blog.okturtles.org/2026/07/short-leash-ai-method/
149•Riseed•17h ago•182 comments

An American Privacy Emergency

https://scottaaronson.blog/?p=9902
333•flowercalled•12h ago•98 comments

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

https://apple.github.io/foundationdb/flow.html
78•sourdecor•21h ago•22 comments

Postgres transactions are a distributed systems superpower

https://www.dbos.dev/blog/co-locating-workflow-state-with-your-data
191•KraftyOne•17h ago•83 comments

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

https://github.com/HUANGCHIHHUNGLeo/claude-real-video
142•cortexosmain•17h ago•46 comments

A Special Wireless-Free Nikon Camera Is Publicly Available for the First Time

https://petapixel.com/2026/06/24/a-special-wireless-free-nikon-camera-is-publicly-available-for-t...
70•HardwareLust•1w ago•58 comments

Superpowers 6

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

Great Salt Lake Tracker

https://growtheflowutah.org/laketracker/
108•cfowles•16h ago•38 comments

This is my attempt to get Vulkan going on NetBSD

https://github.com/segaboy/vulkan-netbsd
113•segaboy81•17h ago•33 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?