frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Beam: Reflection's 501B open-weight model

https://reflection.ai/blog/introducing-beam
415•Philpax•12h ago•130 comments

Example.com just launched the biggest redesign in decades

https://www.debugbear.com/blog/example-dot-com-redesign-history
197•jgx0•8h ago•112 comments

Find the flattest route between any two points in SF

https://flattensf.com/
175•ishan0102•9h ago•59 comments

Resurrecting iChat Audio and Video Conferencing

https://blog.pipetogrep.org/2026/09/11/resurrecting-ichat-audio-and-video-conferencing/
37•thepipetogrep•3h ago•8 comments

Opus 5.5 agents discover two room-temperature magnetic semiconductor candidates

https://www.vals.ai/blogs/room-temperature-magnetic-semiconductors
316•outlier99•10h ago•206 comments

Dust: Pretraining Transformers Without Backpropagation

https://qlabs.sh/research/dust
160•E-Reverance•10h ago•37 comments

Friendship ended with Deno, now Node is my best friend

https://dbushell.com/2026/10/03/deno-to-node/
143•ibobev•9h ago•67 comments

Accountability mechanisms can be joyful

https://liquidbrain.net/blog/accountability-and-joy/
16•luu•2d ago•1 comments

Why Common Lisp is now the best programming language

https://www.vivienhenz.com/common-lisp
131•misterchocolat•4h ago•178 comments

An algorithmic failure beneath the secret ballot

https://blog.citp.princeton.edu/2026/08/03/an-algorithmic-failure-beneath-the-secret-ballot/
70•leecoursey•2d ago•37 comments

Web Search API

https://developers.cloudflare.com/changelog/post/2026-10-02-introducing-web-search-api/
530•tosh•20h ago•240 comments

Anthropic reported diary entry to police, woman faces felony charge

https://www.techspot.com/news/114091-florida-woman-used-claude-diary-anthropic-reported-shoot.html
693•emptybits•1d ago•536 comments

Testing 12 different Zigbee temperature/humidity sensors

https://smarthomescene.com/reviews/best-selling-zigbee-temperature-sensors-tested/
97•walrus01•2d ago•35 comments

Competitive Programmer's Handbook (2018) [pdf]

https://cses.fi/book/book.pdf
178•vinhnx•2d ago•41 comments

Global Solar Atlas: summary of solar power potential globally

https://globalsolaratlas.info/
47•stratts•8h ago•25 comments

Show HN: Photoc – Command-line tools for photographers

https://github.com/ahmetomerv/photoc
28•ahmetomer•2d ago•2 comments

ChatGPT is adding real cartoonists' signatures to fake New Yorker cartoons

https://www.niemanlab.org/2026/10/chatgpt-is-adding-real-cartoonists-signatures-to-fake-new-yorke...
396•rdmuser•8h ago•290 comments

Show HN: Entombed in a Raycaster

https://www.stelabouras.com/blog/entombed-raycaster/
16•stelabouras•2d ago•3 comments

Samon: Designing a Zen Garden Raking Puzzle

https://gwern.net/doc/design/2026-10-03-gwern-samon.html
41•networked•7h ago•18 comments

DEDA – Tracking Dots Extraction, Decoding and Anonymisation Toolkit

https://github.com/dfd-tud/deda
54•greyface-•1d ago•6 comments

Ephemeral Testing

https://lemire.me/blog/2026/10/05/ephemeral-testing/
51•ibobev•8h ago•13 comments

Ocean the Man Who Listens to Whales

https://blue-continuum.com/the-man-who-listens-to-whales
11•dnetesn•1d ago•2 comments

The lamps in my house

https://arslan.io/2026/10/05/the-lamps-in-my-house/
178•farslan•17h ago•83 comments

Texas city demands $2M for public records on Flock usage

https://arstechnica.com/tech-policy/2026/10/texas-city-demands-2m-for-public-records-on-flock-usage/
185•01-_-•9h ago•28 comments

Making a GTK application in Haskell, part 1

https://floreal.tech/blog/2026/making-a-gtk-app-in-haskell-part-1/
153•Vosporos•17h ago•39 comments

Apple and a hacker's future

https://stratechery.com/2026/apple-and-a-hackers-future/
245•maguay•21h ago•213 comments

Qualcomm licenses patents on Huawei’s LogicFolding chip tech

https://www.bloomberg.com/news/articles/2026-10-05/qualcomm-licenses-patents-on-huawei-s-logicfol...
188•0xedb•23h ago•124 comments

We are going to kill "unalive"

https://www.anildash.com/2026/10/06/kill-unalive/
10•Tomte•41m ago•1 comments

The first fully implanted cochlear implant reaches patients

https://spectrum.ieee.org/fully-implantable-cochlear-implant
86•rbanffy•4d ago•70 comments

Linux containers in 500 lines of code (2016)

https://blog.lizzie.io/linux-containers-in-500-loc.html
120•mkornaukhov•17h ago•25 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?