frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Click (2016)

https://clickclickclick.click/
207•andrewzeno•3h ago•44 comments

Anthropic co-founder to present AI encyclical alongside Pope Leo XIV

https://www.vaticannews.va/en/pope/news/2026-05/pope-leo-xiv-first-encyclical-magnifica-humanitas...
113•cucho•3h ago•69 comments

Anthropic acquires Stainless

https://www.anthropic.com/news/anthropic-acquires-stainless
370•tomeraberbach•9h ago•255 comments

Hyperpolyglot Lisp: Common Lisp, Racket, Clojure, Emacs Lisp

https://hyperpolyglot.org/lisp
134•veqq•7h ago•28 comments

We stopped AI bot spam in our GitHub repo using Git's –author flag

https://archestra.ai/blog/only-responsible-ai
419•ildari•11h ago•190 comments

We let AIs run radio stations

https://andonlabs.com/blog/andon-fm
174•lukaspetersson•8h ago•162 comments

The Quiet Renovation at Bitwarden

https://blog.ppb1701.com/the-quiet-renovation-at-bitwarden
539•DaSHacka•2d ago•247 comments

Show HN: Files.md – Open-source alternative to Obsidian

https://github.com/zakirullin/files.md
557•zakirullin•12h ago•281 comments

Show HN: Number Gacha, a gacha game distilled to its essence

https://isabisabel.com/gacha/
51•babel16•5d ago•18 comments

Regex Chess: A 2-ply minimax chess engine in 84,688 regular expressions

https://nicholas.carlini.com/writing/2025/regex-chess.html
8•surprisetalk•4d ago•0 comments

Earth's Radio Bubble: Every signal we've ever sent into space

https://www.thescientificdrop.com/2026/05/earths-radio-bubble-every-signal-weve.html
32•jonbaer•17h ago•23 comments

Project Glasswing: what Mythos showed us

https://blog.cloudflare.com/cyber-frontier-models/
290•Fysi•12h ago•108 comments

Elon Musk has lost his lawsuit against Sam Altman and OpenAI

https://techcrunch.com/2026/05/18/elon-musk-has-lost-his-lawsuit-against-sam-altman-and-openai/
799•nycdatasci•8h ago•421 comments

The Futility of Lava Lamps: What Random Means

https://loup-vaillant.fr/articles/lava-lamps-and-randomness
52•birdculture•2d ago•37 comments

Agora-1: The Multi-Agent World Model

https://odyssey.ml/introducing-agora-1
83•olivercameron•7h ago•16 comments

When can the C++ compiler devirtualize a call?

https://quuxplusone.github.io/blog/2021/02/15/devirtualization/
15•lionkor•1d ago•1 comments

Designing an FPGA Calculator from Scratch

https://baltazarstudios.com/calculator/
51•zdw•1d ago•5 comments

Two computers, one monitor, zero fiddling (2025)

https://alexplescan.com/posts/2025/08/16/kvm/
176•ankitg12•3d ago•97 comments

The FBI Wants to Buy Nationwide Access to License Plate Readers

https://www.404media.co/the-fbi-wants-to-buy-nationwide-access-to-license-plate-readers/
230•cdrnsf•6h ago•92 comments

The Fil-C Optimized Calling Convention

https://fil-c.org/calling_convention
115•pizlonator•2d ago•21 comments

Coding on Paper

https://wickstrom.tech/2026-05-16-coding-on-paper.html
44•owickstrom•1d ago•8 comments

Loopmaster – Livecoding Music IDE

https://loopmaster.xyz/
71•stagas•7h ago•19 comments

Show HN: InsForge – Open-source Heroku for coding agents

https://github.com/InsForge/InsForge
34•mrcoldbrew•10h ago•6 comments

Cutting inference cold starts by 40x with LP, FUSE, C/R, and CUDA-checkpoint

https://modal.com/blog/truly-serverless-gpus
73•charles_irl•8h ago•16 comments

Alignment pretraining: AI discourse creates self-fulfilling (mis)alignment

https://arxiv.org/abs/2601.10160
25•anigbrowl•4h ago•10 comments

Iran starts Bitcoin-backed ship insurance for Hormuz strait

https://www.bloomberg.com/news/articles/2026-05-18/iran-starts-bitcoin-backed-shipping-insurance-...
266•srameshc•9h ago•437 comments

Shutterstock to pay $35M over hard-to-cancel subscriptions

https://www.ftc.gov/news-events/news/press-releases/2026/05/shutterstock-pay-35-million-settle-ft...
136•Lihh27•6h ago•62 comments

What Is Date:Italy?

http://aesthetikx.info/blog/date_italy.html
133•jollyjerry•2d ago•54 comments

Understanding Singleflight in Go

https://www.codingexplorations.com/blog/understanding-singleflight-in-golang-a-solution-for-elimi...
55•ghostbit•2d ago•8 comments

Voice AI Systems Are Vulnerable to Hidden Audio Attacks

https://spectrum.ieee.org/voice-ai-audio-attacks
110•SVI•14h ago•29 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•1y ago

Comments

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

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

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