frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Qwen 3.8 27B is excellent, but it defaults to overthinking things

https://simonwillison.net/2026/Aug/16/qwen-38-27b/
450•bilsbie•9h ago•202 comments

GIMP Development Update

https://www.gimp.org/news/2026/08/16/dev-update-august-2026/
146•lumpa•6h ago•75 comments

Linear algebra done right

https://linear.axler.net/
67•the-mitr•3h ago•29 comments

Beware the Permanent Periphery

https://asteriskmag.com/issues/15/beware-the-permanent-periphery
11•m-hodges•6d ago•5 comments

A third world engineer responds to “RISC-V: They should have known better”

https://rvembedded.com/blog_post/12/
499•Narishma•16h ago•264 comments

Anthropic's 'watermark' text adulteration in Claude is a perversion of writing

https://daringfireball.net/2026/08/anthropics_watermark_text_adulteration_in_claude_is_a_perversi...
249•ropbear•11h ago•230 comments

Reticulum – Decentralized Mesh Network

https://reticulum.network/
117•sudo_cowsay•9h ago•32 comments

Claude: System Prompts

https://platform.claude.com/docs/en/release-notes/system-prompts
654•tosh•20h ago•254 comments

Gakutensoku

https://en.wikipedia.org/wiki/Gakutensoku
24•benbreen•3d ago•3 comments

AGI-64 Brings Sierra Adventures to the Commodore 64

https://meanhamster.com/news/agi-64-brings-sierra-adventures-to-the-commodore-64
82•erickhill•7h ago•10 comments

Rhombus 1.1 is now available

https://blog.racket-lang.org/2026/08/rhombus-v1.1.html
78•spdegabrielle•8h ago•24 comments

Low-Tech Ceramic Water Filter

https://wiki.lowtechlab.org/wiki/Filtre_%C3%A0_eau_c%C3%A9ramique/en
179•Bluestein•5d ago•47 comments

Show HN: Vocal Slice – Cut audio by selecting text, fully on-device

https://vocalslice.com/
39•terranivium•6d ago•26 comments

Design 3D-printable parts by talking

https://nurb.dev/
17•mkmk•2d ago•10 comments

How do I permanently disable random Google Photos popup to backup photos? (2024)

https://support.google.com/photos/thread/256212140/how-do-i-permanently-disable-google-photos-pop...
105•dt3ft•3d ago•73 comments

SIMD in the 90s: Programming Intel's Pentium MMX

https://pikuma.com/blog/programming-intel-pentium-mmx-simd
114•ibobev•3d ago•48 comments

HackEurope 2026: A short rant on AI and hackathons

https://duti.dev/blog/2026/spr/
23•mindracer•1h ago•12 comments

Applying a photosynthetic process to treat “dry eye”

https://www.science.org/content/blog-post/taking-tip-plants-eyes
43•gumby•8h ago•12 comments

Interview with Amit Patel, Creator of “Solar Realms Elite” (2013)

https://breakintochat.com/blog/2013/02/18/amit-patel-creator-of-solar-realms-elite/
54•bananaboy•1w ago•13 comments

Dancing with friends and enemies: boids' swarm intelligence (2012)

https://community.wolfram.com/groups/-/m/t/122095
41•surprisetalk•5d ago•5 comments

Prolly: A content-addressed ordered map built on prolly trees

https://github.com/crabbuild/prolly
43•forhappy•8h ago•3 comments

The AI Credit Resale Economy

https://vectoral.com/blog/who-are-the-token-brokers
284•mlenhard•18h ago•116 comments

Red queen hypothesis – A new way forward for self-improving AI

https://www.cst.cam.ac.uk/news/red-queen-hypothesis-new-way-forward-self-improving-ai
59•hardlianotion•13h ago•14 comments

Protobuf has LSP support

https://buf.build/blog/protobuf-lsp
152•theanonymousone•14h ago•101 comments

Strong gravitational lensing and microlensing of supernovae (2024)

https://infoscience.epfl.ch/entities/publication/644cad8a-6c9b-4b02-bcf3-b8b6e8c614c5
10•andsoitis•6h ago•1 comments

The Life and Death of Direct File [pdf]

https://www.ischool.berkeley.edu/sites/default/files/vinton_report_5.pdf
185•ronbenton•8h ago•91 comments

Tell HN: Cloudflare silently injects its analytics when you switch nameservers

492•stagas•15h ago•134 comments

MathCode, Mathematical Coding Agent

https://math-ai-org.github.io/mathcode/
90•homarp•15h ago•28 comments

Stripe will reportedly acquire OpenRouter for $7B+

https://techcrunch.com/2026/08/16/stripe-will-reportedly-acquire-ai-gateway-startup-openrouter-fo...
345•zacharyozer•12h ago•209 comments

$12B of US ratepayers' money wasted on a modeling mistake in PJM

https://newsletter.semianalysis.com/p/12b-of-us-ratepayers-money-wasted
44•_delirium•3h ago•20 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?