frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Inkling: Our Open-Weights Model

https://thinkingmachines.ai/news/introducing-inkling/
750•vimarsh6739•9h ago•188 comments

SQLite should have (Rust-style) editions

https://mort.coffee/home/sqlite-editions/
141•gnyeki•4h ago•58 comments

G# – A modern .NET language with Go, Kotlin, and Swift ergonomics

https://davidobando.github.io/gsharp/
41•serial_dev•4d ago•12 comments

Grok Build is open source

https://github.com/xai-org/grok-build
300•skp1995•6h ago•346 comments

Governments, companies, nonprofits should invest in free, open source AI [pdf]

https://www.siegelendowment.org/wp-content/uploads/2026/07/fortune-david-siegel-open-source-ai.pdf
101•bilsbie•5h ago•45 comments

Stripe and Advent have made a joint offer to acquire PayPal – sources

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

Bluesky Trademarks ATProto

https://atproto.com/blog/at-protocol-trademark
15•chaosharmonic•1h ago•1 comments

LLM Networking with MikroTik

https://blog.greg.technology/2026/07/14/llm-networking-with-mikrotik.html
59•gregsadetsky•4h ago•22 comments

Metal-Organic Frameworks, Chemistry's New Miracle Materials (2018)

https://chemistry.berkeley.edu/news/meet-metal-organic-frameworks-chemistry%E2%80%99s-new-miracle...
43•andsoitis•4h ago•10 comments

Job queues are deceptively tricky

https://typesanitizer.com/blog/job-queues.html
32•ingve•1d ago•6 comments

CatchCat – Pokémon Go for Cats, IRL

https://www.catchcat.lol/
11•marojejian•5d ago•3 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-...
245•neomindryan•11h ago•159 comments

Show HN: One More Letter

https://playonemoreletter.com/
52•hmate9•4h ago•31 comments

Duskers, the scary command line game, is getting a sequel

https://elbowgreasegames.substack.com/p/misfits-attic-announces-duskers-20
99•spacemarine1•7h ago•24 comments

Brainless: Shadcn components that look like Claude Code, Codex and Grok

https://brainless.swerdlow.dev
103•benswerd•7h ago•21 comments

Command Line Interface Guidelines

https://clig.dev/
80•subset•3d ago•13 comments

Book prizes don't work how you think

https://rebeccamakkai.substack.com/p/book-prizes-dont-work-how-you-think
88•samclemens•1d ago•41 comments

Nul Characters in Strings in SQLite

https://sqlite.org/nulinstr.html
35•basilikum•4h ago•10 comments

Prioritize mental health, and why communication is so important

https://ramones.dev/posts/mental-health/
297•ramon156•15h ago•256 comments

Voxatron

https://www.lexaloffle.com/voxatron.php
70•lsferreira42•7h ago•19 comments

Mysteries of Telegram Data Centers (2022)

https://dev.moe/en/3025
243•theanonymousone•13h ago•132 comments

Collection of Digital Clock Designs

https://clocks.dev
189•levmiseri•10h ago•36 comments

P2P local file transfer based on WebRTC

https://pairdrop.net/
38•halb•4h ago•16 comments

The Anti-Mac User Interface (1996)

https://www.nngroup.com/articles/anti-mac-interface/
60•ninglor•4h ago•20 comments

Designing APIs for Agents

https://www.freestyle.sh/blog/opinion/designing-apis-for-agents
59•benswerd•2d ago•28 comments

Artie (YC S23) Is Hiring Software Engineers

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

Towards a harness that can do anything

https://eardatasci.github.io/c/ambiance/index.html
179•evakhoury•13h ago•92 comments

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

https://github.com/welcome-to-the-sunny-side/misa77
134•nonadhocproblem•11h ago•40 comments

Show HN: Firefox in WebAssembly

https://developer.puter.com/labs/firefox-wasm/
146•coolelectronics•6h ago•86 comments

Today I Rescued 7,234 Old GIFs

https://danq.me/2026/07/10/rescuing-7234-gifs/
115•birdculture•3d ago•10 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?