frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

DeepSeek V4 Pro 0813

https://openrouter.ai/deepseek/deepseek-v4-pro-0813
720•explosion-s•8h ago•270 comments

Delta

https://zed.dev/blog/introducing-delta
371•khy•6h ago•121 comments

Tailscale Traces Database Corruption to 16y/o SQLite WAL-Reset Bug

https://tailscale.com/blog/sqlite-wal-reset-bug
777•ropbear•10h ago•138 comments

Qwen3.8-2.4T

https://huggingface.co/Qwen/Qwen3.8-2.4T-A95B
481•Philpax•9h ago•102 comments

Happy 45th Birthday to the IBM PC and Model F/XT

https://sharktastica.co.uk/articles/pc-fxt-45
16•tart-lemonade•1h ago•1 comments

What's New in Flutter 3.47

https://flutter.dev/blog/whats-new-in-flutter-3-47
21•gumby271•1h ago•10 comments

Principia Mathematica is modern and insightful

https://okmij.org/ftp/Computation/Impressions/PrincipiaMathematica.html
22•matt_d•1h ago•2 comments

Show HN: Ballet – Workflow automation that writes integrations against any API

https://www.ballet.dev/
11•danielkimber•54m ago•1 comments

Why Target Common Lisp for Code Generation?

http://funcall.blogspot.com/2026/08/why-vibe-code-in-lisp.html
22•oumua_don17•16h ago•18 comments

2026 Eclipse Webcams

https://jonty.github.io/2026_eclipse_webcams/
457•zoenolan•13h ago•124 comments

Tim King, AmigaDOS developer, has died

https://amiga-news.de/en/news/AN-2026-08-00070-EN.html
230•doener•10h ago•28 comments

HTML over WebSockets: real-time SPAs with barely any JavaScript

https://en.andros.dev/blog/ef4968f5/html-over-websockets-real-time-spas-with-barely-any-javascript/
140•redbell•8h ago•106 comments

Build Wide, Ship Narrow

https://adapt.com/blog/build-wide-ship-narrow
11•ashumz•1h ago•0 comments

Grok 4.6

https://x.ai/news/grok-4-6
391•iLuddite•9h ago•388 comments

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

https://discoveredmaterials.com/research/
113•advaith08•17h ago•21 comments

Someone is running mass vulnerability scans, spoofing AI bots like ClaudeBot

https://knownagents.com/insights
226•gavinhking•10h ago•164 comments

uBlock Origin Is Giving Up the Fight to Keep Ads Off Facebook

https://digitalescapetools.com/2026/08/ublock-origin-stops-chasing-facebook-ads.html
285•Markoff•13h ago•388 comments

Why tiny JPEGs look different in Chrome

https://guillaumetech.github.io/posts/jpg-scaling-chrome/
247•gutechh•10h ago•59 comments

Pixel Watch 5

https://blog.google/products-and-platforms/devices/pixel/pixel-watch-5/
95•ortusdux•8h ago•179 comments

Process as a Proxy for Motivation

https://bengodfrey.dev/blog/process/
20•sudo-bendg•2h ago•1 comments

Program images and portable Scheme back ends for Jolt

https://yogthos.net/posts/2026-08-07-portable-jolt.html
4•yogthos•4d ago•0 comments

Reflex (YC W23) Is hiring Growth and GTM Roles

https://www.ycombinator.com/companies/reflex/jobs/71x5GFb-growth-engineer
1•apetuskey•7h ago

A Tale of Dynamic Programming (2022)

https://iagoleal.com/posts/dynamic-programming/
68•Brajeshwar•3d ago•3 comments

I built a browser-native SysEx librarian for 80s/90s synthesizers

https://bipluk.com/
8•halfradaition•2h ago•5 comments

Debugging Information for Inlined Functions

https://lwn.net/Articles/1083985/
19•pykello•3d ago•0 comments

Breaking the WAL

https://antithesis.com/blog/2026/wal-reset-bug/
48•wwilson•4h ago•31 comments

Grok 4.6 scores 61 on the Artificial Analysis Intelligence Index

https://artificialanalysis.ai/articles/grok-4-6-benchmarks-and-analysis
311•wertyk•8h ago•314 comments

Shade Map

https://shademap.app
138•fredley•11h ago•41 comments

Lovable raises $400M Series C

https://lovable.dev/blog/series-c
89•thoughtpeddler•8h ago•84 comments

AI is removing the middle class of software engineering?

https://blog.florianherrengt.com/ai-removing-middle-class-software-engineering.html
697•florianherrengt•11h ago•630 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?