frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Compression is prediction

https://ngrok.com/blog/compression-is-prediction
311•nikolay•7h ago•130 comments

WorldClaw Agentic 3D open-world generation at scale

https://tencent-hunyuan.github.io/Hunyuan3D-WorldClaw/
151•EwanG•5h ago•49 comments

Nvidia Nemotron 3.5 Lightning and NeMo Switchyard

https://blogs.nvidia.com/blog/nemotron-lightning-switchyard-rtx-dgx/
192•droidjj•7h ago•99 comments

Mojo 1.0

https://www.modular.com/blog/modular-26-5-mojo-1-0-is-here
316•dayanruben•10h ago•146 comments

The lifesaving secret hidden inside a horseshoe crab's blue blood

https://whdh.com/news/the-lifesaving-secret-hidden-inside-a-horseshoe-crabs-blue-blood-and-the-ra...
17•andsoitis•1h ago•1 comments

The hardest working font in Manhattan (2025)

https://aresluna.org/the-hardest-working-font-in-manhattan/
31•dcminter•5d ago•2 comments

Stealing Reasoning Traces from Proprietary LLM APIs

https://stolen-thoughts.com/
532•quantumgarbage•14h ago•222 comments

Retire the Abstractions

https://hazyresearch.stanford.edu/blog/2026-08-05-retire-the-abstractions
31•convexstrictly•6d ago•31 comments

OpenAI’s head of ethics leaves less than a year after joining

https://www.ft.com/content/e49dfb75-f841-4466-a577-f7aaff8779a0
317•ilamont•15h ago•355 comments

New Bedford police officer accused of using Flock cameras to track ex-partner

https://newbedfordlight.org/new-bedford-police-officer-accused-of-using-flock-cameras-to-track-an...
56•newsomix9xl•1h ago•31 comments

Show HN: Line9 – A Mermaid rendering engine with its own layout

https://line9.ai/diagram
37•jumpalongjim•5d ago•7 comments

Making holograms with a pen plotter

https://blog.jordan.matelsky.com/Penplotter-holography/
127•DemiGuru•8h ago•13 comments

Grok Bot

https://x.ai/bot
180•rvz•10h ago•152 comments

Show HN: iPhone app takes simultaneous images from 2 lenses, fuses into 1 photo

https://photosynthesis.camera
225•sajomes•3d ago•227 comments

Show HN: Tamron Lens Utility Alternative on Linux

https://github.com/yikerman/tamron-lens-control
32•xiaoyu2006•4d ago•0 comments

Go is an ideal language for AI-assisted software engineering

https://developers.googleblog.com/why-go-is-an-ideal-language-for-ai-assisted-software-engineering/
299•0xedb•10h ago•349 comments

Company Offering '100% Human-Written, Never AI' Medical Research Is 100% AI

https://www.404media.co/company-offering-100-human-written-never-ai-peer-review-is-entirely-ai/
23•Anon84•1h ago•3 comments

How we used to get jobs: A newspaper classifieds story

https://ironicsans.ghost.io/how-we-used-to-get-jobs/
118•speckx•9h ago•94 comments

England set to be one of the first countries to eliminate hepatitis C

https://www.bbc.com/news/articles/c75gk620r22o
498•stevekemp•14h ago•360 comments

The Human Is the Loop

https://brentfitzgerald.com/posts/the-human-is-the-loop/
4•burnto•1h ago•0 comments

Jolt: Clojure compiler implemented with Chez Scheme

https://jolt-lang.github.io
159•mark_l_watson•3d ago•58 comments

pg_clickhouse v0.10: Subquery pushdown and 1000x faster TPC-H queries

https://clickhouse.com/blog/pg_clickhouse-whats-new-july-2026
43•saisrirampur•5h ago•3 comments

Neutrinos from Deep Inside Earth Provide a New Picture of the Mantle

https://www.quantamagazine.org/neutrinos-from-deep-inside-earth-provide-a-new-picture-of-the-mant...
10•rbanffy•14h ago•0 comments

'Every millimetre counts': Inside the beast tunnelling under Sydney Harbour

https://www.smh.com.au/national/nsw/every-millimetre-counts-inside-the-beast-tunnelling-under-syd...
3•hiharryhere•1d ago•2 comments

Nvidia's Risky Business

https://stratechery.com/2026/nvidias-risky-business/
308•jonbaer•17h ago•144 comments

London Underground begins scanning passengers' faces

https://www.btp.police.uk/news/btp/news/england/btp-expands-live-facial-recognition-lfr-trial-int...
246•BlueBerry2001•17h ago•261 comments

Emergent Introspective Awareness in Large Language Models

https://arxiv.org/abs/2601.01828
39•doener•6h ago•14 comments

Manus will return to operating as an independent company

https://manus.im/blog/a-note-to-our-users
141•thm•13h ago•69 comments

CSS properties you should know for better text designs

https://master.dev/blog/typographic-css-tricks/
86•ibobev•10h ago•7 comments

Show HN: Git-knife – Edit commit messages, authors, and dates like a spreadsheet

https://github.com/TheRealYT/git-knife
143•YonathanTesfaye•12h ago•88 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?