frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Murati's Thinking Machines Releases Open-Weights 975B Parameter LLM

https://thinkingmachines.ai/inkling/
105•htrp•55m ago•20 comments

I Left Google DeepMind

https://turntrout.com/why-i-left-google-deepmind
47•apsec112•29m ago•9 comments

Inkling: Our Open-Weights Model

https://thinkingmachines.ai/news/introducing-inkling/
59•vimarsh6739•57m ago•8 comments

Codex Micro

https://openai.com/supply/co-lab/work-louder/
159•davidbarker•2h ago•136 comments

Running Gemma 4 26B at 5 tokens/sec on a 13-year-old Xeon with no GPU

https://www.neomindlabs.com/2026/06/08/running-gemma-4-26b-at-5-tokens-sec-on-a-13-year-old-xeon-...
138•neomindryan•3h ago•71 comments

Stripe, Advent offer to buy PayPal for more than $53B

https://www.reuters.com/business/finance/stripe-advent-offer-buy-paypal-more-than-53-billion-sour...
107•rvz•15h ago•63 comments

Mysteries of Telegram Data Centers

https://dev.moe/en/3025
186•theanonymousone•5h ago•68 comments

Show HN: misa77 - a codec that decodes 2x faster than LZ4 (at better ratios)

https://github.com/welcome-to-the-sunny-side/misa77
76•nonadhocproblem•3h ago•26 comments

Collection of Digital Clock Designs

https://clocks.dev
58•levmiseri•2h ago•15 comments

Artie (YC S23) Is Hiring Software Engineers

https://jobs.ashbyhq.com/artie
1•tang8330•2h ago

Prioritize mental health, and why communication is so important

https://ramones.dev/posts/mental-health/
212•ramon156•7h ago•137 comments

Launch HN: Coasty (YC S26) – An API for computer-use agents

https://coasty.ai/docs
23•nkov47•3h ago•0 comments

Towards a Harness That Can Do Anything

https://eardatasci.github.io/c/ambiance/index.html
109•evakhoury•5h ago•60 comments

My midlife crisis Corolla is fast, furious, and modded

https://www.zocalopublicsquare.org/my-midlife-crisis-corolla-fast-furious-fully-modded/
90•gmays•4h ago•190 comments

Sleep regularity is a stronger predictor of mortality risk than sleep duration (2023)

https://academic.oup.com/sleep/article/47/1/zsad253/7280269
571•bilsbie•7h ago•283 comments

What designing 54 computer science cards taught me about graphic design

https://fhoehl.com/designing-algodeck
24•marukodo•2h ago•7 comments

Open-source memory for coding agents, synced over SSH

https://github.com/vshulcz/deja-vu/
61•vshulcz•2h ago•15 comments

Editing React components that never rendered

https://blog.crossui.com/2026/07/editing-react-components-that-never-rendered
9•linb•2d ago•1 comments

When A.I. Is a Member of the Family

https://www.newyorker.com/magazine/2026/07/20/when-ai-is-a-member-of-the-family
40•fortran77•3h ago•45 comments

The Memory Heist

https://www.ayush.digital/blog/the-memory-heist
52•eieio•23h ago•4 comments

Briar is in maintenance mode

https://briarproject.org/news/2026-maintenance-mode/
110•ristello•6h ago•75 comments

Unsolved Problems in MLOps

https://spawn-queue.acm.org/doi/pdf/10.1145/3762989
22•gnyeki•2h ago•3 comments

OpenAI loses trademark dispute at EU court

https://dpa-international.com/economics/urn:newsml:dpa.com:20090101:260715-930-389143/
154•hermanzegerman•4h ago•110 comments

A General Goal-Conditioned Minecraft Model

https://pantograph.com/journal/pan-1
24•agajews•2h ago•9 comments

The Three-Second Theft: Why AI Voice Fraud Outruns Every Defence

https://smarterarticles.co.uk/the-three-second-theft-why-ai-voice-fraud-outruns-every-defence
135•dxs•5h ago•170 comments

The well-calibrated Bayesian [pdf] (1982)

https://fitelson.org/seminar/dawid.pdf
39•Murfalo•4h ago•14 comments

Today I Rescued 7,234 Old GIFs

https://danq.me/2026/07/10/rescuing-7234-gifs/
38•birdculture•3d ago•2 comments

Weathergotchi – an open-source climate Tamagotchi

https://github.com/Michael-Manning/E-Paper-Climate-Logger
98•luanmuniz•8h ago•22 comments

The Conservationist Who Turned 40 Terabytes of Public Data into a Video Game

https://blog.exe.dev/meet-the-conservationist-who-turned-40-terabytes-of-government-data-into-a-v...
72•bryanmikaelian•1d ago•13 comments

Telegram Serverless

https://core.telegram.org/bots/serverless
132•soheilpro•9h 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?