frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Linux Sandboxes and Fil-C

https://fil-c.org/seccomp
217•pizlonator•10h ago•61 comments

Using E-Ink tablet as monitor for Linux

https://alavi.me/blog/e-ink-tablet-as-monitor-linux/
106•yolkedgeek•4d ago•45 comments

Recovering Anthony Bourdain's Li.st's

https://sandyuraz.com/blogs/bourdain/
199•thecsw•11h ago•66 comments

I fed 24 years of my blog posts to a Markov model

https://susam.net/fed-24-years-of-posts-to-markov-model.html
175•zdw•12h ago•76 comments

I tried Gleam for Advent of Code

https://blog.tymscar.com/posts/gleamaoc2025/
277•tymscar•16h ago•158 comments

Closures as Win32 Window Procedures

https://nullprogram.com/blog/2025/12/12/
65•ibobev•9h ago•10 comments

Cat Gap

https://en.wikipedia.org/wiki/Cat_gap
105•Petiver•4d ago•19 comments

An Implementation of J

https://www.jsoftware.com/ioj/ioj.htm
56•ofalkaed•8h ago•21 comments

No-Tifier (2017)

https://subject.space/projects/no-tifier/
18•aebtebeten•3d ago•1 comments

Lean Theorem Prover Mathlib

https://github.com/leanprover-community/mathlib4
30•downboots•7h ago•0 comments

If a Meta AI model can read a brain-wide signal, why wouldn't the brain?

https://1393.xyz/writing/if-a-meta-ai-model-can-read-a-brain-wide-signal-why-wouldnt-the-brain
74•rdgthree•7h ago•34 comments

“You should never build a CMS”

https://www.sanity.io/blog/you-should-never-build-a-cms
49•handfuloflight•3h ago•25 comments

VPN location claims don't match real traffic exits

https://ipinfo.io/blog/vpn-location-mismatch-report
354•mmaia•13h ago•213 comments

Therapeutic use of cannabis and cannabinoids: A review

https://jamanetwork.com/journals/jama/fullarticle/2842072?guestAccessKey=a368e622-e374-4a0c-8d3b-...
41•bookofjoe•7h ago•30 comments

The Rise of Computer Games, Part I: Adventure

https://technicshistory.com/2025/12/13/the-rise-of-computer-games-part-i-adventure/
91•cfmcdonald•12h ago•33 comments

Mystery Science Theater 3000: The Definitive Oral History of a TV Masterpiece

https://www.wired.com/2014/04/mst3k-oral-history/
44•indigodaddy•6d ago•6 comments

Useful patterns for building HTML tools

https://simonwillison.net/2025/Dec/10/html-tools/
283•simonw•3d ago•81 comments

Heavy metal is healing teens on the Blackfeet Nation

https://www.hcn.org/issues/57-11/heavy-metal-is-healing-teens-on-the-blackfeet-nation/
57•cdrnsf•5h ago•20 comments

Create a Markdown Editor in Ruby on Rails

https://blog.appsignal.com/2025/12/10/create-a-markdown-editor-in-ruby-on-rails.html
3•amalinovic•3d ago•0 comments

Dhtml Lemmings (2004)

https://www.elizium.nu/scripts/lemmings/index.php
27•tetris11•5d ago•9 comments

Why Twilio Segment moved from microservices back to a monolith

https://www.twilio.com/en-us/blog/developers/best-practices/goodbye-microservices
224•birdculture•12h ago•190 comments

Go Proposal: Secret Mode

https://antonz.org/accepted/runtime-secret/
188•enz•4d ago•87 comments

An off-grid, flat-packable washing machine

https://www.positive.news/society/flat-pack-washing-machine-spins-a-fairer-future/
85•ohjeez•10h ago•50 comments

Branch, Test, Deploy: A Git-Inspired Approach for Data

https://motherduck.com/blog/git-for-data-part-1/
5•surprisetalk•5d ago•0 comments

Ask HN: How can I get better at using AI for programming?

322•lemonlime227•17h ago•344 comments

Cryptids

https://wiki.bbchallenge.org/wiki/Cryptids
110•frozenseven•1w ago•16 comments

From Azure Functions to FreeBSD

https://jmmv.dev/2025/12/from-azure-functions-to-freebsd.html
91•todsacerdoti•6d ago•16 comments

Using Python for Scripting

https://hypirion.com/musings/use-python-for-scripting
127•birdculture•6d ago•88 comments

EasyPost (YC S13) Is Hiring

https://www.easypost.com/careers
1•jstreebin•16h ago

Researchers seeking better measures of cognitive fatigue

https://www.nature.com/articles/d41586-025-03974-w
134•bikenaga•3d ago•36 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•7mo ago

Comments

balloob•7mo 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•7mo ago
Discussion for the other article in the series:

https://news.ycombinator.com/item?id=44011381

tomhow•7mo ago
Comments moved thither. Thanks!
pabs3•7mo ago
They are two different articles, I don't think that was correct.
tomhow•6mo 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•6mo ago
Thanks for the response, guess that makes sense.
pabs3•6mo 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?