frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Someone bought 30 WordPress plugins and planted a backdoor in all of them

https://anchor.host/someone-bought-30-wordpress-plugins-and-planted-a-backdoor-in-all-of-them/
749•speckx•9h ago•214 comments

GitHub Stacked PRs

https://github.github.com/gh-stack/
492•ezekg•6h ago•273 comments

Lean proved this program correct; then I found a bug

https://kirancodes.me/posts/log-who-watches-the-watchers.html
131•bumbledraven•3h ago•71 comments

DaVinci Resolve releases Photo Editor

https://www.blackmagicdesign.com/products/davinciresolve/photo
37•thebiblelover7•1h ago•5 comments

WiiFin – Jellyfin Client for Nintendo Wii

https://github.com/fabienmillet/WiiFin
78•throwawayk7h•4h ago•30 comments

Design and implementation of DuckDB internals

https://duckdb.org/library/design-and-implementation-of-duckdb-internals/
39•mpweiher•3d ago•3 comments

Nothing Ever Happens: Polymarket bot that always buys No on non-sports markets

https://github.com/sterlingcrispin/nothing-ever-happens
370•m-hodges•12h ago•193 comments

Write less code, be more responsible

https://blog.orhun.dev/code-responsibly/
44•orhunp_•2d ago•22 comments

How to make Firefox builds 17% faster

https://blog.farre.se/posts/2026/04/10/caching-webidl-codegen/
143•mbitsnbites•8h ago•23 comments

US appeals court declares 158-year-old home distilling ban unconstitutional

https://nypost.com/2026/04/11/us-news/us-appeals-court-declares-158-year-old-home-distilling-ban-...
324•t-3•13h ago•237 comments

Rust Threads on the GPU

https://www.vectorware.com/blog/threads-on-gpu/
8•PaulHoule•4d ago•2 comments

Servo is now available on crates.io

https://servo.org/blog/2026/04/13/servo-0.1.0-release/
432•ffin•15h ago•140 comments

Make tmux pretty and usable (2024)

https://hamvocke.com/blog/a-guide-to-customizing-your-tmux-conf/
328•speckx•12h ago•208 comments

Building a CLI for all of Cloudflare

https://blog.cloudflare.com/cf-cli-local-explorer/
273•soheilpro•11h ago•87 comments

GAIA – Open-source framework for building AI agents that run on local hardware

https://amd-gaia.ai/docs
104•galaxyLogic•8h ago•24 comments

Air Powered Segment Display? [video]

https://www.youtube.com/watch?v=E1BLGpE5zH0
60•ProfDreamer•2d ago•9 comments

The AI revolution in math has arrived

https://www.quantamagazine.org/the-ai-revolution-in-math-has-arrived-20260413/
32•sonabinu•4h ago•16 comments

Show HN: Ithihāsas – a character explorer for Hindu epics, built in a few hours

https://www.ithihasas.in
120•cvrajeesh•8h ago•28 comments

Android now stops you sharing your location in photos

https://shkspr.mobi/blog/2026/04/android-now-stops-you-sharing-your-location-in-photos/
309•edent•15h ago•282 comments

What we learned building a Rust runtime for TypeScript

https://encore.dev/blog/rust-runtime
47•vinhnx•2d ago•11 comments

I just want simple S3

https://blog.feld.me/posts/2026/04/i-just-want-simple-s3/
110•g0xA52A2A•2d ago•66 comments

N-Day-Bench – Can LLMs find real vulnerabilities in real codebases?

https://ndaybench.winfunc.com
42•mufeedvh•5h ago•11 comments

Tracking down a 25% Regression on LLVM RISC-V

https://blog.kaving.me/blog/tracking-down-a-25-regression-on-llvm-risc-v/
101•luu•1d ago•20 comments

Visualizing CPU Pipelining (2024)

https://timmastny.com/blog/visualizing-cpu-pipelining/
68•flipacholas•9h ago•9 comments

B-trees and database indexes (2024)

https://planetscale.com/blog/btrees-and-database-indexes
91•tosh•10h ago•37 comments

If you started a company two years ago, many assumptions are no longer true

https://steveblank.com/2026/03/17/your-startup-is-probably-dead-on-arrival/
154•tie-in•2d ago•125 comments

Why it’s impossible to measure England’s coastline

https://www.bbc.com/travel/article/20260410-why-its-impossible-to-measure-englands-coastline
18•BiraIgnacio•3h ago•17 comments

MEMS Array Chip Can Project Video the Size of a Grain of Sand

https://spectrum.ieee.org/mems-photonics
80•bookofjoe•13h ago•36 comments

Ascending into the Realm of Japanese Charts

https://www.chartography.net/p/ascending-into-the-realm-of-japanese
46•speckx•7h ago•1 comments

Just Enough Chimera Linux

https://www.dwarmstrong.org/chimera-install-zfs/
48•speckx•7h ago•11 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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