frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete

https://huggingface.co/sweepai/sweep-next-edit-1.5B
184•williamzeng0•8h ago•24 comments

Doctors in Brazil using tilapia fish skin to treat burn victims

https://www.pbs.org/newshour/health/brazilian-city-uses-tilapia-fish-skin-treat-burn-victims
49•kaycebasques•2h ago•21 comments

From stealth blackout to whitelisting: Inside the Iranian shutdown

https://www.kentik.com/blog/from-stealth-blackout-to-whitelisting-inside-the-iranian-shutdown/
78•oavioklein•7h ago•25 comments

Threat actors expand abuse of Microsoft Visual Studio Code

https://www.jamf.com/blog/threat-actors-expand-abuse-of-visual-studio-code/
141•vinnyglennon•7h ago•87 comments

Hands-On Introduction to Unikernels

https://labs.iximiuz.com/tutorials/unikernels-intro-93976514
21•valyala•5d ago•2 comments

Claude's new constitution

https://www.anthropic.com/news/claude-new-constitution
423•meetpateltech•15h ago•406 comments

Show HN: ChartGPU – WebGPU-powered charting library (1M points at 60fps)

https://github.com/ChartGPU/ChartGPU
569•huntergemmer•16h ago•163 comments

Waiting for dawn in search: Search index, Google rulings and impact on Kagi

https://blog.kagi.com/waiting-dawn-search
284•josephwegner•14h ago•159 comments

Binary fuse filters: Fast and smaller than xor filters (2022)

https://arxiv.org/abs/2201.01174
89•redbell•4d ago•6 comments

Your brain on ChatGPT: Accumulation of cognitive debt when using an AI assistant

https://www.media.mit.edu/publications/your-brain-on-chatgpt/
107•misswaterfairy•9h ago•88 comments

eBay explicitly bans AI "buy for me" agents in user agreement update

https://www.valueaddedresource.net/ebay-bans-ai-agents-updates-arbitration-user-agreement-feb-2026/
105•bdcravens•10h ago•104 comments

Skip is now free and open source

https://skip.dev/blog/skip-is-free/
378•dayanruben•16h ago•171 comments

Gathering Linux Syscall Numbers in a C Table

https://t-cadet.github.io/programming-wisdom/#2026-01-17-gathering-linux-syscall-numbers
10•phi-system•4d ago•1 comments

Show HN: High speed graphics rendering research with tinygrad/tinyJIT

https://github.com/quantbagel/gtinygrad
20•quantbagel•4h ago•7 comments

Significant US farm losses persist, despite federal assistance

https://www.fb.org/market-intel/significant-farm-losses-persist-despite-federal-assistance
143•toomuchtodo•6h ago•145 comments

TrustTunnel: AdGuard VPN protocol goes open-source

https://adguard-vpn.com/en/blog/adguard-vpn-protocol-goes-open-source-meet-trusttunnel.html
120•kumrayu•14h ago•38 comments

Show HN: Rails UI

https://railsui.com/
157•justalever•13h ago•84 comments

JPEG XL Test Page

https://tildeweb.nl/~michiel/jxl/
183•roywashere•15h ago•118 comments

Show HN: RatatuiRuby wraps Rust Ratatui as a RubyGem – TUIs with the joy of Ruby

https://www.ratatui-ruby.dev/
112•Kerrick•4d ago•19 comments

Letting Claude play text adventures

https://borretti.me/article/letting-claude-play-text-adventures
106•varjag•5d ago•43 comments

Lix – universal version control system for binary files

https://lix.dev/blog/introducing-lix/
36•onecommit•7h ago•16 comments

Tell HN: 2 years building a kids audio app as a solo dev – lessons learned

99•oliverjanssen•18h ago•41 comments

The WebRacket language is a subset of Racket that compiles to WebAssembly

https://github.com/soegaard/webracket
120•mfru•4d ago•26 comments

Show HN: Differentiable Quantum Chemistry

https://github.com/lowdanie/hartree-fock-solver
26•lowdanie•4d ago•5 comments

Beowulf's opening "What" is no interjection (2013)

https://www.poetryfoundation.org/poetry-news/69208/new-research-opening-line-of-beowulf-is-not-wh...
74•gsf_emergency_6•3d ago•56 comments

Jerry (YC S17) Is Hiring

https://www.ycombinator.com/companies/jerry-inc/jobs/QaoK3rw-software-engineer-core-automation-ma...
1•linaz•10h ago

Golfing APL/K in 90 Lines of Python

https://aljamal.substack.com/p/golfing-aplk-in-90-lines-of-python
68•aburjg•5d ago•14 comments

Can you slim macOS down?

https://eclecticlight.co/2026/01/21/can-you-slim-macos-down/
213•ingve•1d ago•254 comments

SIMD programming in pure Rust

https://kerkour.com/introduction-rust-simd
85•randomint64•2d ago•36 comments

Convert potentially dangerous PDFs to safe PDFs

https://github.com/freedomofpress/dangerzone
147•dp-hackernews•8h ago•48 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?