frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

The lost joy of music piracy

https://www.pigeonsandplanes.com/read/music-piracy-what-cd-oink-nine-inch-nails-streaming
365•mcgin•5h ago•210 comments

Inkling: Our Open-Weights Model

https://thinkingmachines.ai/news/introducing-inkling/
998•vimarsh6739•16h ago•249 comments

Where are YC founders now? OpenAI and Anthropic, mostly

https://joinedanthropic.com
42•ohong•2h ago•10 comments

If you want to create a button from scratch, you must first create the universe

https://madcampos.dev/blog/2026/07/accessibility-from-scratch/
147•treve•6h ago•65 comments

Teardown: A Generic 7-Port USB 3.0 Hub That Wasn't

https://goughlui.com/2026/07/09/teardown-a-generic-7-port-usb-3-0-hub-that-wasnt/
71•speckx•3d ago•27 comments

1,300 Beautiful Wildlife Illustrations from the 19th Century Now Restored

https://www.openculture.com/2026/07/explore-1300-beautiful-wildlife-illustrations-from-the-19th-c...
106•gslin•7h ago•17 comments

Grok Build is open source

https://github.com/xai-org/grok-build
461•skp1995•14h ago•505 comments

SQLite should have (Rust-style) editions

https://mort.coffee/home/sqlite-editions/
281•gnyeki•12h ago•125 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
204•bilsbie•13h ago•75 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...
448•rvz•1d ago•260 comments

In defense of not understanding your codebase

https://www.seangoedecke.com/in-defense-of-not-understanding-your-codebase/
13•saikatsg•3d ago•11 comments

Bluesky Trademarks ATProto

https://atproto.com/blog/at-protocol-trademark
109•chaosharmonic•9h ago•48 comments

Reynard: A real Firefox web browser for iOS 13 or later

https://github.com/minh-ton/reynard-browser
55•AbuAssar•6h ago•14 comments

I also filed the corners off my MacBook

https://www.brt.fyi/posts/mac-book-filing/
197•maxbrt•1d ago•100 comments

Making 768 servers look like 1

https://planetscale.com/blog/making-768-servers-look-like-1
86•hisamafahri•7h ago•16 comments

The Tokio/Rayon Trap and Why Async/Await Fails Concurrency

https://pmbanugo.me/blog/why-async-await-complect-concurrency
71•LAC-Tech•8h ago•43 comments

High-Bandwidth Flash offers efficient storage for model weights

https://spectrum.ieee.org/high-bandwidth-flash
49•Gaishan•1d ago•17 comments

Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes

https://www.petekeen.net/homelab-resolved/
33•zrail•4d ago•25 comments

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

https://davidobando.github.io/gsharp/
100•serial_dev•4d ago•70 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-...
289•neomindryan•19h ago•188 comments

Job queues are deceptively tricky

https://typesanitizer.com/blog/job-queues.html
92•ingve•2d ago•29 comments

Can LLMs Perform Deep Technical Comprehension of Computer Architecture Papers

https://arxiv.org/abs/2607.11859
58•Jimmc414•8h ago•14 comments

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

https://coasty.ai/docs
37•nkov47•18h ago•12 comments

Command Line Interface Guidelines

https://clig.dev/
135•subset•3d ago•31 comments

LLM Networking with MikroTik

https://blog.greg.technology/2026/07/14/llm-networking-with-mikrotik.html
91•gregsadetsky•12h ago•42 comments

Netstrings (1997)

https://cr.yp.to/proto/netstrings.txt
21•signa11•5h ago•10 comments

Dense Arena Interning: The Engine of Compiler Performance

https://aikoschurmann.com/blog/string-interning-compilers
8•g0xA52A2A•3d ago•1 comments

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

https://elbowgreasegames.substack.com/p/misfits-attic-announces-duskers-20
130•spacemarine1•15h ago•39 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...
57•andsoitis•11h ago•13 comments

Collection of Digital Clock Designs

https://clocks.dev
248•levmiseri•18h ago•47 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?