frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

SQLite is all you need for durable workflows

https://obeli.sk/blog/sqlite-is-all-you-need-for-durable-workflows/
125•tomasol•1h ago•61 comments

Notes from the Mistral AI Now Summit in Paris

https://koenvangilst.nl/lab/mistral-ai-now-summit
211•vnglst•3h ago•53 comments

The dead economy theory

https://www.owenmcgrann.com/p/the-dead-economy-theory
327•WillDaSilva•4h ago•432 comments

On Rendering Diffs

https://pierre.computer/writing/on-rendering-diffs
36•amadeus•43m ago•1 comments

Bijou64: A variable-length integer encoding

https://www.inkandswitch.com/tangents/bijou64/
171•justinweiss•4h ago•63 comments

Rothko for your current weather conditions

https://rothko.joonas.wtf/
44•jxmorris12•1h ago•6 comments

It's hard to justify buying a Framework 12

https://www.jeffgeerling.com/blog/2026/its-hard-to-justify-framework-12/
125•watermelon0•4h ago•219 comments

GTA 6 Developers Unionize

https://rockstarintel.com/gta-6-developers-announce-rockstar-games-union/
409•AndrewKemendo•4h ago•252 comments

Liquid AI reveals 8B-A1B MoE trained on 38T

https://www.liquid.ai/blog/lfm2-5-8b-a1b
54•simjnd•3h ago•7 comments

CAPTCHAs can still detect AI agents

https://research.roundtable.ai/captchas-detect-ai/
49•timshell•3h ago•30 comments

Show HN: TV Explorer. Adding advanced UI to free online TV

https://tvexplorer.live
41•dtagames•3h ago•7 comments

Is AI causing a repeat of frontend’s lost decade?

https://mastrojs.github.io/blog/2026-05-23-is-AI-causing-a-repeat-of-frontends-lost-decade/
208•xyzal•8h ago•191 comments

Robinhood now lets your AI agents trade stocks

https://techcrunch.com/2026/05/27/robinhood-now-lets-your-ai-agents-trade-stocks/
57•wapasta•2h ago•88 comments

Shift will clean homes for free to train future robots

https://www.theverge.com/ai-artificial-intelligence/939765/ai-training-data-startup-shift-free-cl...
5•evilsimon•32m ago•1 comments

Letter from the Duke of Wellington to the British Foreign Office (1809)

https://wellsoc.org/society-member-pages/anecdotes-of-wellington/
17•backuprestore•2h ago•1 comments

High Density Living, 2000 Years Ago: Inside the Roman Apartment Building

https://commonedge.org/high-density-living-2000-years-ago-inside-the-roman-apartment-building/
126•surprisetalk•7h ago•41 comments

We should be more tired than the model

https://vickiboykis.com/2026/05/28/we-should-be-more-tired-than-the-model/
121•tosh•7h ago•97 comments

I am retiring from tech to live offline

https://openpath.quest/2026/i-am-retiring-from-tech-to-live-offline/
605•PinkG•5h ago•420 comments

Local Git remotes

https://cblgh.org/posts/local-git-remotes/
69•surprisetalk•7h ago•56 comments

CVE-Bench: testing LLM agents on real-world vulnerability patches

https://giovannigatti.github.io/cve-bench/
3•logickkk1•19m ago•1 comments

Someone used my open source project to phish people

https://andrej.sh/posts/phishing-through-my-open-source-project
68•andrejsshell•6h ago•37 comments

Cedana (YC S23) Is Hiring

https://www.ycombinator.com/companies/cedana/jobs/d1vYocG-forward-deployed-engineer-ai-hpc
1•neelm•7h ago

Expertise in the age of AI

https://www.moderndescartes.com/essays/ai_and_expertise/
76•brilee•6h ago•78 comments

Real-time LLM Inference on Standard GPUs: 3k tokens/s per request

https://blog.kog.ai/real-time-llm-inference-on-standard-gpus-3-000-tokens-s-per-request/
184•NicoConstant•10h ago•81 comments

ATLAS: Autoformalized Textbook Library At Scale

https://github.com/facebookresearch/atlas-lean
21•vrm•1d ago•3 comments

AI will be used to estimate age of asylum seekers from next year

https://www.bbc.co.uk/news/articles/ce3pe36qe7ro
22•vylorn•1h ago•6 comments

Durable execution, the hard way

https://github.com/hatchet-dev/durable-execution-the-hard-way
41•abelanger•1d ago•3 comments

Is this sustainable?

https://jamiehurst.co.uk/2026-05-24_ai-sustainable
84•ColinEberhardt•9h ago•92 comments

The Secret Garden of Rock-Paper-Scissors

https://theshamblog.com/the-secret-garden-of-rock-paper-scissors/
31•scottshambaugh•5h ago•7 comments

Poll: How often do you check "newest"?

64•ColinWright•7h ago•81 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?