frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

You Could Have Come Up with Kimi Delta Attention

https://blog.doubleword.ai/you-could-have-come-up-with-kimi-delta-attention
188•AnhTho_FR•2h ago•65 comments

Steel Bank Common Lisp version 2.6.7

https://sbcl.org/all-news.html?2.6.7
50•tmtvl•1h ago•6 comments

Delayed Gratification – Proud to Be 'Last to Breaking News'

https://www.slow-journalism.com/
107•speerer•2h ago•48 comments

Zig's Incremental Compilation Internals

https://mlugg.co.uk/posts/incremental-compilation-internals/
96•garyhtou•2h ago•41 comments

7.1 Earthquake in Japan

https://www.data.jma.go.jp/multi/quake/quake_detail.html?eventID=20260728163528&lang=en
722•krembo•10h ago•185 comments

Kimi K3 Architecture Overview and Notes

https://sebastianraschka.com/blog/2026/kimi-k3-architecture-notes.html
90•ModelForge•2h ago•8 comments

How Do I Profile eBPF Code?

https://naveensrinivasan.com/posts/2026-07-22-how-do-i-profile-ebpf-code/
68•snaveen•2h ago•5 comments

iPhone Upgrade Program

https://www.apple.com/shop/iphone/iphone-upgrade-program
29•lkurtz•49m ago•28 comments

Show HN: XY – A Fast, composable, GPU-accelerated interactive plotting library

https://github.com/reflex-dev/xy
56•apetuskey•2h ago•19 comments

Discovering Cryptographic Weaknesses with Claude

https://www.anthropic.com/research/discovering-cryptographic-weaknesses
51•gslin•1h ago•13 comments

New HIV vaccine shows unprecedented success in preclinical study

https://www.lji.org/news-events/news/post/new-hiv-vaccine-shows-unprecedented-success-in-preclini...
386•codebyaditya•5h ago•185 comments

WOFF 1.0: a milestone on W3C's journey of fonts on the web

https://www.w3.org/blog/2026/woff-1-0-a-milestone-on-w3cs-journey-of-fonts-on-the-web/
20•hn_acker•1h ago•0 comments

Kimi Linear: An Expressive, Efficient Attention Architecture

https://arxiv.org/abs/2510.26692
217•ronfriedhaber•7h ago•82 comments

Harmony Explained: Progress Towards a Scientific Theory of Music (2012)

https://arxiv.org/abs/1202.4212
59•surprisetalk•3h ago•45 comments

Now Is the Time to Give LLMs Access to the ACM Digital Library

https://cacm.acm.org/opinion/now-is-the-time-to-give-llms-access-to-the-acm-digital-library/
44•rbanffy•3h ago•15 comments

Using a Gaming PC's RTX 5070 from a separate Linux workstation

https://stephenkrings.com/posts/rtx-5070-linux-gpu-server/
15•microbial•5d ago•2 comments

Substack writers, you need a website

https://elizabethtai.com/2026/06/10/substack-writers-you-need-a-website/
80•speckx•1h ago•71 comments

Anthropeum

https://anthropeum.com/
67•bookofjoe•3h ago•14 comments

DMARC Has Been Public Since 2012. 68.4% of Domains Still Don't Enforce It

https://ciphercue.com/blog/dmarc-enforcement-gap-rua-fragmentation-2026
135•adulion•8h ago•86 comments

So, you want to make a game engine (2023)

https://lisyarus.github.io/blog/posts/so-you-want-to-make-a-game-engine.html#part-3
28•kugurerdem•2h ago•22 comments

How to Survive Boiling Water

https://taxa.substack.com/p/how-to-survive-boiling-water
349•cainxinth•4d ago•74 comments

Stop Killing the Internet: No Digital ID and No Age Verification

https://citizens-initiative.europa.eu/initiatives/details/2026/000011_en
175•doener•3h ago•55 comments

Una Watch: Garmin watch competitor but repairable, open ecosystem and USB-C

https://unawatch.com/
37•pimterry•3h ago•26 comments

Scientific computing in the age of agentic AI

https://openai.com/index/scientific-computing-agentic-ai/
16•mfiguiere•1h ago•1 comments

VMs can't boot with Network Mode set to Bridged on Apple M5 Pro machines

https://github.com/utmapp/UTM/issues/7658
46•IndySun•4h ago•25 comments

Show HN: Formally verified 3D CSG: Trust 93 lines spec, not 1000 lines AI code

https://github.com/schildep/verified-3d-mesh-intersection
90•permute•5h ago•40 comments

Google's Beyond Zero: Enterprise Security for the AI Era

https://spawn-queue.acm.org/doi/10.1145/3819083
115•jordigg•8h ago•64 comments

Xenharmlib (music theory library) adds support for Just Intonation

https://xenharmlib.readthedocs.io/en/latest/whats_new_0_4_0.html
10•retooth•2h ago•1 comments

Show HN: Flashpaper – Self-destructing secret sharing with no database

https://flashpaper.app/
18•minpym•2h ago•3 comments

Solving Fermat: Andrew Wiles

https://www.pbs.org/wgbh/nova/proof/wiles.html
55•1970-01-01•21h ago•24 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?