frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Tim Gowers: What sort of maths are LLMs good at?

https://gowers.wordpress.com/2026/08/12/what-sort-of-maths-are-llms-good-at/
73•ColinWright•1h ago•12 comments

Show HN: Woxi - Open-source Mathematica / Wolfram Language reimplementation

https://woxi.ad-si.com
57•adius•1h ago•1 comments

LinkedIn CringeBot 3000

https://www.cringebot3000.com/
248•theanonymousone•4h ago•94 comments

Dutch Train Map Simulator

https://spoorkaart.zaza.dev
47•zazaalaza•2h ago•26 comments

High-Res Photo Shows Sand-Capped Butte Rising from Mars Plain of Polygons

https://petapixel.com/2026/08/04/amazing-high-res-photo-shows-a-butte-rising-from-mars/
19•bookofjoe•6d ago•1 comments

Facebook is paying controversial creators to produce rage-bait content

https://www.abc.net.au/news/2026-08-06/ragebait-how-facebook-is-paying-controversial-creators/106...
128•robtherobber•1h ago•58 comments

Worms: The Future of Yesterday's Worms Today

https://worm.net/
71•doener•5d ago•22 comments

Compression is prediction

https://ngrok.com/blog/compression-is-prediction
561•nikolay•15h ago•227 comments

The hardest working font in Manhattan (2025)

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

Launch HN: Discovered Materials (YC P26) – AI agents to discover new materials

https://discoveredmaterials.com/research/
20•advaith08•3h ago•6 comments

WorldClaw Agentic 3D open-world generation at scale

https://tencent-hunyuan.github.io/Hunyuan3D-WorldClaw/
237•EwanG•13h ago•73 comments

llama.cpp

https://llama.app
258•kristianpaul•6h ago•113 comments

A shell exclamation mark is not for yelling. Be lazy

https://refp.se/articles/your-shell-and-the-lazy-exclamation-mark
95•refp•5d ago•41 comments

Stealing Reasoning Traces from Proprietary LLM APIs

https://stolen-thoughts.com/
635•quantumgarbage•22h ago•284 comments

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

https://www.ft.com/content/e49dfb75-f841-4466-a577-f7aaff8779a0
455•ilamont•23h ago•430 comments

Nvidia Nemotron 3.5 Lightning and NeMo Switchyard

https://blogs.nvidia.com/blog/nemotron-lightning-switchyard-rtx-dgx/
236•droidjj•15h ago•123 comments

Mojo 1.0

https://www.modular.com/blog/modular-26-5-mojo-1-0-is-here
397•dayanruben•18h ago•203 comments

Newfoundland has a hard bread shortage, but why do they eat it?

https://www.cbc.ca/news/canada/newfoundland-labrador/nl-hard-bread-history-shortage-9.7299276
24•empressplay•2d ago•27 comments

Music Generation by a Composer, for Musicians

https://monictheory.com
3•song_synth•4d ago•0 comments

The Human Is the Loop

https://brentfitzgerald.com/posts/the-human-is-the-loop/
124•burnto•9h ago•58 comments

Grok Bot

https://x.ai/bot
302•rvz•18h ago•268 comments

DARPA heavy lift challenge ends with winner at a 3.84:1 payload to weight ratio

https://dronexl.co/2026/08/10/darpa-lift-challenge-results-avidrone/
51•daau•8h ago•35 comments

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

https://photosynthesis.camera
294•sajomes•3d ago•273 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...
90•andsoitis•9h ago•25 comments

Making holograms with a pen plotter

https://blog.jordan.matelsky.com/Penplotter-holography/
169•DemiGuru•16h ago•17 comments

London Underground begins scanning passengers' faces

https://www.btp.police.uk/news/btp/news/england/btp-expands-live-facial-recognition-lfr-trial-int...
356•BlueBerry2001•1d ago•439 comments

Retire the Abstractions

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

Jolt: Clojure compiler implemented with Chez Scheme

https://jolt-lang.github.io
202•mark_l_watson•3d ago•67 comments

Show HN: Tamron Lens Utility Alternative on Linux

https://github.com/yikerman/tamron-lens-control
73•xiaoyu2006•4d ago•8 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/
392•0xedb•18h ago•448 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?