frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Ntsc-rs – open-source video emulation of analog TV and VHS artifacts

https://ntsc.rs/
32•gregsadetsky•47m ago•7 comments

Zeroserve: A zero-config web server you can script with eBPF

https://su3.io/posts/introducing-zeroserve
111•losfair•5h ago•28 comments

Nvidia is proposing a beast of a CPU system for Windows PCs

https://twitter.com/lemire/status/2062880075117113739
153•tosh•7h ago•303 comments

You Can Run

https://magazine.atavist.com/2026/mccann-cocaine-fugitives
47•bryanrasmussen•4h ago•12 comments

Meta confirms 1000s of Instagram accounts were hacked by abusing its AI chatbot

https://this.weekinsecurity.com/meta-confirms-thousands-of-instagram-accounts-were-hacked-by-abus...
54•speckx•1h ago•15 comments

Benchmarks in Leipzig

https://arxiv.org/abs/2606.05818
101•root-parent•6h ago•40 comments

Show HN: Infinite canvas notes in the non-Euclidean Poincaré disk

https://uonr.github.io/poincake/
63•uonr•4d ago•8 comments

How LLMs work

https://www.0xkato.xyz/how-llms-actually-work/
751•0xkato•2d ago•207 comments

Pentagon raised threat of Israeli spying on U.S. to highest level, sources say

https://www.nbcnews.com/politics/national-security/pentagon-raised-threat-israeli-spying-us-highe...
169•MilnerRoute•1h ago•96 comments

Google will pay SpaceX $920M per month for compute

https://techcrunch.com/2026/06/05/google-will-pay-spacex-920m-per-month-for-compute/
319•ramanan•8h ago•472 comments

WoofWare.PawPrint, a Deterministic .NET Runtime

https://www.patrickstevens.co.uk/posts/2026-06-04-announcing-woofware-pawprint/
25•Smaug123•2d ago•7 comments

Pokemon Emerald Ported to WebAssembly (100k FPS)

https://pokeemerald.com/
196•tripplyons•8h ago•59 comments

Running Python code in a sandbox with MicroPython and WASM

https://simonwillison.net/2026/Jun/6/micropython-in-a-sandbox/
50•theanonymousone•5h ago•17 comments

Lambda isn't leaking memory, your metrics are lying to you

https://engineering.taktile.com/blog/onnx-memory-usage-on-lambda/
8•tlarkworthy•2d ago•0 comments

Police in England and Wales told to halt AI use in court statements

https://www.ft.com/content/229e5949-3ebc-4151-8a86-a01b5e259241
109•nmstoker•4h ago•39 comments

Moving beyond fork() + exec()

https://lwn.net/SubscriberLink/1076018/16f01bbbb8e0d1f0/
189•jwilk•5h ago•189 comments

Summer of '85: DOSBOS is rejected by ANALOG Computing

https://www.goto10retro.com/p/summer-of-85-dosbos-is-rejected-by
27•ibobev•2d ago•7 comments

Building Rust Procedural Macros from the Grounds Up

https://www.learnix-os.com/ch02-03-implementing-the-bitfields-proc-macro.html
61•Sagi21805•6d ago•13 comments

S&P 500 rejects SpaceX, also blocking entry for OpenAI and Anthropic

https://arstechnica.com/tech-policy/2026/06/sp-500-blocks-fast-spacex-entry-wont-waive-rule-for-u...
1214•maltalex•15h ago•422 comments

Mbodi AI (YC P25) Is Hiring Founding Machine Learning Engineer (Robotics)

https://www.ycombinator.com/companies/mbodi-ai/jobs/WYAcNkX-founding-machine-learning-engineer
1•chitianhao•8h ago

Trees to Flows and Back: Unifying Decision Trees and Diffusion Models

https://arxiv.org/abs/2605.00414
28•rsn243•7h ago•5 comments

Python JIT project was asked to pause development

https://discuss.python.org/t/an-announcement-from-the-steering-council-regarding-the-jit-project/...
101•kbumsik•4h ago•35 comments

Tribute to Jiro Yamada, Automotive Artist (1960-2025) [video]

https://www.youtube.com/watch?v=rJ2gQ5Md60U
33•NaOH•23h ago•2 comments

Splash Is a Colour Format

https://www.todepond.com/lab/splash/
28•tobr•2d ago•20 comments

New method turns ocean water into drinking water, without waste

https://www.rochester.edu/newscenter/what-is-desalination-definition-ocean-water-704732/
475•speckx•1d ago•199 comments

The intracies of modern camera lens repair (2024)

https://salvagedcircuitry.com/sigma-45mm.html
226•transistor-man•19h ago•83 comments

Ask HN: Why is the HN crowd so anti-AI?

283•Ekami•17h ago•484 comments

Ask HN: What was your "oh shit" moment with GenAI?

491•andrehacker•1d ago•872 comments

Show HN: Soft Body Jiggle Physics

https://github.com/xloveee/jiggle-physics
43•vesperance•4d ago•17 comments

Social Cache Busting

https://www.autodidacts.io/social-cache-busting/
117•surprisetalk•4d ago•43 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?