frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Is BGP Safe Yet? No. Test Your ISP

https://isbgpsafeyet.com/
74•janandonly•1h ago•28 comments

Claude Code Unpacked : A visual guide

https://ccunpacked.dev/
759•autocracy101•9h ago•257 comments

CERN levels up with new superconducting karts

https://home.cern/news/news/engineering/cern-levels-new-superconducting-karts
250•fnands•7h ago•53 comments

Show HN: Sycamore – next gen Rust web UI library using fine-grained reactivity

https://sycamore.dev
45•lukechu10•2h ago•33 comments

Show HN: Baton – A desktop app for developing with AI agents

https://getbaton.dev/
29•tordrt•2h ago•26 comments

Intuiting Pratt Parsing

https://louis.co.nz/2026/03/26/pratt-parsing.html
75•signa11•2d ago•17 comments

Consider the Greenland Shark (2020)

https://www.lrb.co.uk/the-paper/v42/n09/katherine-rundell/consider-the-greenland-shark
28•mooreds•5d ago•5 comments

Show HN: CLI to order groceries via reverse-engineered REWE API (Haskell)

https://github.com/yannick-cw/korb
142•wazHFsRy•2d ago•57 comments

Claude Wrote a Full FreeBSD Remote Kernel RCE with Root Shell (CVE-2026-4747)

https://github.com/califio/publications/blob/main/MADBugs/CVE-2026-4747/write-up.md
130•ishqdehlvi•9h ago•42 comments

Wasmer (YC S19) Is Hiring – Rust and DevRel Positions

https://www.workatastartup.com/companies/wasmer
1•syrusakbary•2h ago

New Patches Allow Building Linux IPv6-Only, Option to Deprecate "Legacy" IPv4

https://www.phoronix.com/news/Linux-IPv6-IPv4-Legacy-Knobs
38•Bender•1h ago•6 comments

Chess in SQL

https://www.dbpro.app/blog/chess-in-pure-sql
115•upmostly•3d ago•24 comments

A dot a day keeps the clutter away

https://scottlawsonbc.com/post/dot-system
430•scottlawson•17h ago•126 comments

Show HN: 1-Bit Bonsai, the First Commercially Viable 1-Bit LLMs

https://prismml.com/
326•PrismML•17h ago•132 comments

TinyLoRA – Learning to Reason in 13 Parameters

https://arxiv.org/abs/2602.04118
206•sorenjan•5d ago•34 comments

TruffleRuby

https://chrisseaton.com/truffleruby/
160•tosh•3d ago•20 comments

I Quit. The Clankers Won

https://dbushell.com/2026/04/01/i-quit-the-clankers-won/
238•domysee•5h ago•245 comments

MiniStack (replacement for LocalStack)

https://ministack.org/
262•kerblang•17h ago•50 comments

The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

https://alex000kim.com/posts/2026-03-31-claude-code-source-leak/
1274•alex000kim•1d ago•516 comments

Bring Back MiniDV with This Raspberry Pi FireWire Hat

https://www.jeffgeerling.com/blog/2026/minidv-with-raspberry-pi-firewire-hat/
87•ingve•3d ago•15 comments

Neanderthals survived on a knife's edge for 350k years

https://www.science.org/content/article/neanderthals-survived-knife-s-edge-350-000-years
190•Hooke•13h ago•145 comments

Slop is not necessarily the future

https://www.greptile.com/blog/ai-slopware-future
275•dakshgupta•1d ago•448 comments

4D Doom

https://github.com/danieldugas/HYPERHELL
243•chronolitus•4d ago•58 comments

OpenAI closes funding round at an $852B valuation

https://www.cnbc.com/2026/03/31/openai-funding-round-ipo.html
486•surprisetalk•18h ago•445 comments

Open source CAD in the browser (Solvespace)

https://solvespace.com/webver.pl
353•phkahler•1d ago•111 comments

Axios compromised on NPM – Malicious versions drop remote access trojan

https://www.stepsecurity.io/blog/axios-compromised-on-npm-malicious-versions-drop-remote-access-t...
1881•mtud•1d ago•758 comments

6o6 v1.1: Faster 6502-on-6502 virtualization for a C64/Apple II Apple-1 emulator

http://oldvcr.blogspot.com/2026/03/6o6-v11-faster-6502-on-6502.html
25•classichasclass•3d ago•1 comments

In Case of Emergency, Make Burrito Bison 3 (2017)

https://juicybeast.com/2017/08/03/in-case-of-emergency-make-burrito-bison-3/
21•amarcheschi•1d ago•8 comments

Teenage Engineering's PO-32 acoustic modem and synth implementation

https://github.com/ericlewis/libpo32
132•ericlewis•4d ago•29 comments

Show HN: Postgres extension for BM25 relevance-ranked full-text search

https://github.com/timescale/pg_textsearch
174•tjgreen•22h ago•47 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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