frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Hacker wipes Romania's land registry database

https://news.risky.biz/risky-bulletin-hacker-wipes-romanias-entire-land-registry-database/
336•speckx•3h ago•188 comments

China's open-weights AI strategy is winning

https://werd.io/american-ai-is-locked-down-and-proprietary-its-losing/
196•benwerd•2h ago•180 comments

Corners Don't Look Like That: Regarding Screenspace Ambient Occlusion (2012)

https://nothings.org/gamedev/ssao/
96•firephox•1h ago•32 comments

Over 30% of new ArXiv submissions now read as AI-written

https://unslop.run/blog/measuring-ai-writing-on-arxiv
15•dopamine_daddy•30m ago•4 comments

We're Squandering LEDs' Potential to Save Our Night Skies

https://spectrum.ieee.org/led-light-pollution
126•defrost•4h ago•80 comments

Airport Simulator

https://airport.apunen.com/
393•apunen•6h ago•97 comments

Firefox Merges Support for Vulkan Video Decoding

https://github.com/search
102•DemiGuru•3h ago•22 comments

Perfection Is Not Over-Engineering

https://var0.xyz/posts/perfection-is-not-over-engineering.html
84•var0xyz•2h ago•47 comments

The Voice of Google

https://www.newyorker.com/culture/the-weekend-essay/the-voice-of-google
30•littlexsparkee•1h ago•11 comments

Kimi K3, Qwen 3.8, and Anthropic's (Potential) Unravelling

https://www.emergingtrajectories.com/lh/frontier-lab-economics/
109•cl42•1h ago•110 comments

Exploit brokers pay $500k for WordPress RCEs. I found one with GPT5.6 and $25

https://slcyber.io/research-center/exploit-brokers-pay-500000-for-a-wordpress-rce-i-found-one-wit...
325•infosecau•8h ago•169 comments

Launch HN: Bloomy (YC S26) – AI-powered mastery learning for K-12

3•alexsouthmayd•35m ago•16 comments

Czechia moves to ban mobile phones in schools from September 2027

https://www.expats.cz/czech-news/article/czech-news-in-brief-for-july-20-2026-monday-top-afternoo...
10•Markoff•1h ago•4 comments

Shinjuku Station in 3D

https://satoshi7190.github.io/Shinjuku-indoor-threejs-demo/
40•Gecko4072•3h ago•10 comments

The EU is about to sell our most sensitive data to the US for visa-free travel

https://edri.org/our-work/the-eu-is-about-to-sell-our-most-sensitive-data-to-the-us-for-visa-free...
342•rapnie•4h ago•193 comments

I Stopped "Creating Content"

https://refactoringenglish.com/blog/why-i-stopped-creating-content/
10•mtlynch•1h ago•4 comments

NYC Subway Signals: A Complete Guide

https://www.nycsubway.org/wiki/Subway_Signals%3A_A_Complete_Guide
16•at1as•2h ago•6 comments

Satan's 19th-Century Bank Note (2017)

https://www.historytoday.com/miscellanies/satans-19th-century-bank-note
32•Caiero•15h ago•1 comments

Show HN: Wheesper – Start an anonymous discussion with a link

https://wheesper.com/
11•whatdoyouthink2•1h ago•14 comments

Inertia-1: An Open Exploration to a Unified Motion Foundation Model

https://yang-ai-lab.github.io/Inertia-1/
32•hasheddan•3h ago•1 comments

SaaS *is* dead. But not because AI "killed" it, because AI killed it

https://avivcarmi.com/saas-is-dead/
9•avivcarmis1•1h ago•0 comments

Controlling Reasoning Effort in LLMs

https://magazine.sebastianraschka.com/p/controlling-reasoning-effort-in-llms
11•ibobev•2h ago•0 comments

Another Entry in the "Stuff Im Glad Im Not Responsible for" Ledger

https://blog.cloudflare.com/dnssec-nta-ede-33/
4•c_f_•5d ago•1 comments

Ziggity – A terminal UI for Git, written in Zig

https://github.com/simoarpe/ziggity
6•TheSorcerer•1h ago•2 comments

Soofi – Sovereign Open Source Foundation Models

https://www.soofi.info/
23•Fake4d•4h ago•9 comments

Cross sectioning insects in an electron microscope with a femtosecond laser [video]

https://www.youtube.com/watch?v=NwhVJ7cv9B4
4•surprisetalk•1h ago•0 comments

Annoying and alarming things about OpenCode

https://wren.wtf/shower-thoughts/stop-using-opencode/
305•alekq•4h ago•209 comments

Tested Kimi K3 for Coding

https://www.dotnetperls.com/2026_7_18_tested-kimi-k3-coding
23•speckx•3h ago•6 comments

Sensing warm and cool: how the body detects temperature changes

https://news.uq.edu.au/2026-07-sensing-warm-and-cool-how-body-detects-temperature-changes
32•hhs•2d ago•5 comments

ECC and DDR5

https://etbe.coker.com.au/2026/07/19/ecc-ddr5/
76•zdw•1d ago•64 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?