frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Beginning January 2026, all ACM publications will be made open access

https://dl.acm.org/openaccess
1544•Kerrick•14h ago•166 comments

1.5 TB of VRAM on Mac Studio – RDMA over Thunderbolt 5

https://www.jeffgeerling.com/blog/2025/15-tb-vram-on-mac-studio-rdma-over-thunderbolt-5
295•rbanffy•7h ago•103 comments

History LLMs: Models trained exclusively on pre-1913 texts

https://github.com/DGoettlich/history-llms
359•iamwil•7h ago•129 comments

We pwned X, Vercel, Cursor, and Discord through a supply-chain attack

https://gist.github.com/hackermondev/5e2cdc32849405fff6b46957747a2d28
727•hackermondev•10h ago•289 comments

Texas is suing all of the big TV makers for spying on what you watch

https://www.theverge.com/news/845400/texas-tv-makers-lawsuit-samsung-sony-lg-hisense-tcl-spying
676•tortilla•2d ago•323 comments

Noclip.website – A digital museum of video game levels

https://noclip.website/
90•ivmoreau•3h ago•11 comments

The state of the kernel Rust experiment

https://lwn.net/SubscriberLink/1050174/63aa7da43214c3ce/
28•dochtman•5d ago•3 comments

GPT-5.2-Codex

https://openai.com/index/introducing-gpt-5-2-codex/
433•meetpateltech•11h ago•230 comments

Getting bitten by Intel's poor naming scenes

https://lorendb.dev/posts/getting-bitten-by-poor-naming-schemes/
6•LorenDB•26m ago•2 comments

How China built its ‘Manhattan Project’ to rival the West in AI chips

https://www.japantimes.co.jp/business/2025/12/18/tech/china-west-ai-chips/
290•artninja1988•11h ago•303 comments

Prompt caching: 10x cheaper LLM tokens, but how?

https://ngrok.com/blog/prompt-caching/
21•samwho•2d ago•3 comments

Skills for organizations, partners, the ecosystem

https://claude.com/blog/organization-skills-and-directory
254•adocomplete•12h ago•142 comments

Telegraph chess: A 19th century tech marvel

https://spectrum.ieee.org/telegraph-chess
20•sohkamyung•6d ago•2 comments

Show HN: Picknplace.js, an alternative to drag-and-drop

https://jgthms.com/picknplace.js/
217•bbx•2d ago•92 comments

Lite^3, a JSON-Compatible Zero-Copy Serialization Format

https://github.com/fastserial/lite3
32•cryptonector•6d ago•7 comments

Great ideas in theoretical computer science

https://www.cs251.com/
75•sebg•7h ago•14 comments

Show HN: Stop AI scrapers from hammering your self-hosted blog (using porn)

https://github.com/vivienhenz24/fuzzy-canary
189•misterchocolat•2d ago•131 comments

The Code That Revolutionized Orbital Simulation [video]

https://www.youtube.com/watch?v=nCg3aXn5F3M
33•surprisetalk•4d ago•2 comments

Reconstructed Commander Keen 1-3 Source Code

https://pckf.com/viewtopic.php?t=18248
9•deevus•2h ago•0 comments

Firefox will have an option to disable all AI features

https://mastodon.social/@firefoxwebdevs/115740500373677782
354•twapi•11h ago•306 comments

T5Gemma 2: The next generation of encoder-decoder models

https://blog.google/technology/developers/t5gemma-2/
121•milomg•10h ago•22 comments

Delty (YC X25) Is Hiring an ML Engineer

https://www.ycombinator.com/companies/delty/jobs/MDeC49o-machine-learning-engineer
1•lalitkundu•8h ago

Oliver Sacks put himself into his case studies – what was the cost?

https://www.newyorker.com/magazine/2025/12/15/oliver-sacks-put-himself-into-his-case-studies-what...
35•barry-cotter•9h ago•71 comments

I've been writing ring buffers wrong all these years (2016)

https://www.snellman.net/blog/archive/2016-12-13-ring-buffers/
94•flaghacker•2d ago•34 comments

Meta Segment Anything Model Audio

https://ai.meta.com/samaudio/
188•megaman821•2d ago•26 comments

Two kinds of vibe coding

https://davidbau.com/archives/2025/12/16/vibe_coding.html
61•jxmorris12•8h ago•55 comments

FunctionGemma 270M Model

https://blog.google/technology/developers/functiongemma/
187•mariobm•11h ago•48 comments

How to hack Discord, Vercel and more with one easy trick

https://kibty.town/blog/mintlify/
138•todsacerdoti•10h ago•31 comments

SMB Direct – SMB3 over RDMA – The Linux Kernel Documentation

https://docs.kernel.org/filesystems/smb/smbdirect.html
3•tambourine_man•4h ago•0 comments

Your job is to deliver code you have proven to work

https://simonwillison.net/2025/Dec/18/code-proven-to-work/
701•simonw•15h ago•562 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•7mo 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•7mo ago
Thanks for the response, guess that makes sense.
pabs3•7mo 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?