frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Doing gigabit Ethernet over my British phone wires

https://thehftguy.com/2026/01/22/doing-gigabit-ethernet-over-my-british-phone-wires/
203•user5994461•4h ago•116 comments

FOSS "Just Fork It" Delusion

https://hamishcampbell.com/foss-just-fork-it-delusion/
35•mimasama•1h ago•35 comments

XHTML Club

https://xhtml.club/
23•bradley_taunt•1h ago•25 comments

Many Small Queries Are Efficient in SQLite

https://www.sqlite.org/np1queryprob.html
48•tosh•3h ago•38 comments

I Like GitLab

https://www.whileforloop.com/en/blog/2026/01/21/i-like-gitlab/
56•lukas346•4h ago•30 comments

Internet Archive's Storage

https://blog.dshr.org/2026/01/internet-archives-storage.html
206•zdw•3d ago•54 comments

MS confirms it will give the FBI your Windows PC data encryption key if asked

https://www.windowscentral.com/microsoft/windows-11/microsoft-bitlocker-encryption-keys-give-fbi-...
33•blacktulip•1h ago•8 comments

Unrolling the Codex agent loop

https://openai.com/index/unrolling-the-codex-agent-loop/
382•tosh•17h ago•178 comments

How I Estimate Work as a Staff Software Engineer

https://www.seangoedecke.com/how-i-estimate-work/
32•mattjhall•4h ago•1 comments

80386 Multiplication and Division

https://nand2mario.github.io/posts/2026/80386_multiplication_and_division/
68•nand2mario•8h ago•14 comments

Proof of Corn

https://proofofcorn.com/
423•rocauc•20h ago•279 comments

Show HN: Coi – A language that compiles to WASM, beats React/Vue

121•io_eric•3d ago•47 comments

JVIC: New web-based Commodore VIC 20 emulator

https://vic20.games/#/basic/24k
8•lance_ewing•2h ago•2 comments

Management Time: Who's Got the Monkey? [pdf]

https://www.med.unc.edu/uncaims/wp-content/uploads/sites/764/2014/03/Oncken-_-Wass-Who_s-Got-the-...
19•rintrah•4d ago•2 comments

Modetc: Move your dotfiles from kernel space

https://maxwell.eurofusion.eu/git/rnhmjoj/modetc
33•todsacerdoti•6h ago•16 comments

Extracting verified C++ from the Rocq theorem prover at Bloomberg

https://bloomberg.github.io/crane/
75•clarus•4d ago•5 comments

When employees feel slighted, they work less

https://penntoday.upenn.edu/news/penn-wharton-when-employees-feel-slighted-they-work-less
61•consumer451•4d ago•52 comments

“Let people help” – Advice that made a big difference to a grieving widow

https://www.npr.org/2026/01/20/nx-s1-5683170/let-them-the-small-bit-of-advice-that-made-a-big-dif...
96•NaOH•11h ago•16 comments

Traintrackr – Live LED Maps

https://www.traintrackr.co.uk/
66•recursion•5d ago•24 comments

Some C habits I employ for the modern day

https://www.unix.dog/~yosh/blog/c-habits-for-me.html
187•signa11•5d ago•109 comments

Telli (YC F24) is hiring eng, design, growth [on-site, Berlin]

https://careers.telli.com/
1•sebselassie•7h ago

Gas Town's agent patterns, design bottlenecks, and vibecoding at scale

https://maggieappleton.com/gastown
357•pavel_lishin•22h ago•370 comments

The fix for a segfault that never shipped

https://www.recall.ai/blog/the-fix-for-a-segfault-that-never-shipped
13•davidgu•3d ago•2 comments

Banned C++ features in Chromium

https://chromium.googlesource.com/chromium/src/+/main/styleguide/c++/c++-features.md
203•szmarczak•18h ago•172 comments

Ask HN: What's the current best local/open speech-to-speech setup?

191•dsrtslnd23•1d ago•49 comments

Microsoft gave FBI set of BitLocker encryption keys to unlock suspects' laptops

https://techcrunch.com/2026/01/23/microsoft-gave-fbi-a-set-of-bitlocker-encryption-keys-to-unlock...
928•bookofjoe•20h ago•584 comments

Comma openpilot – Open source driver-assistance

https://comma.ai
307•JumpCrisscross•13h ago•166 comments

New YC homepage

https://www.ycombinator.com/
272•sarreph•20h ago•148 comments

Booting from a vinyl record (2020)

https://boginjr.com/it/sw/dev/vinyl-boot/
328•yesturi•1d ago•110 comments

Mental Models (2018)

https://fs.blog/mental-models/
113•hahahacorn•17h ago•17 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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