frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Fujitsu launches made-in-Japan next-generation CPU FUJITSU-MONAKA

https://global.fujitsu/en-global/pr/news/2026/09/14-02
255•my123•1d ago•96 comments

Rate limits on GitLab.com are changing

https://about.gitlab.com/blog/rate-limit-change-2026/
35•darkwater•46m ago•21 comments

Artificial intelligence now beats some of the best human forecasters

https://www.economist.com/science-and-technology/2026/09/16/artificial-intelligence-now-beats-som...
25•ddp26•1h ago•11 comments

LLM Classification Is Feature Engineering

https://minimallysufficient.com/posts/llm-classification-is-feature-extraction/
19•minsufficient•40m ago•5 comments

OpenAI's Misalignment Framework: A Tactical Bid to Preempt Global AI Governance

https://asiaai.fyi/openai-misalignment-framework-global-governance/
18•ghernando•54m ago•15 comments

One Year of Sponsored Servo Development

https://servo.org/blog/2026/09/15/one-year-of-sponsorship/
273•AshleysBrain•8h ago•118 comments

Whoisinspace.com/

https://whoisinspace.com
9•Egg-Man•20m ago•2 comments

Vinix – A modern operating system written in V

https://vinix-os.org/
7•hggh•40m ago•0 comments

CCC invites all model citizens to 40C3

https://events.ccc.de/en/2026/09/12/40c3-model-citizens/
204•antonly•8h ago•59 comments

Nvidia announces native GPU programming in Rust

https://developer.nvidia.com/blog/introducing-cuda-rust-two-tracks-for-writing-gpu-kernels/
879•nonmaskable•1d ago•346 comments

CrowdSec Source Code Leak

https://www.crowdsec.net/blog/crowdsec-statement-source-code-exposure
7•eccgecko•46m ago•0 comments

Show HN: Share your AI Setup, Learn from others

https://mysetup.ai/
53•steveybrown•3h ago•22 comments

My temporary PHP fix from 2014 has nearly 20M installs. Today I'm deprecating it

https://jakeasmith.com/blog/http-build-url/
264•jakeasmith•1d ago•68 comments

Keys Not Included: recovering the signing keys for US driver's license barcodes

https://ryan.science/blog/keys-not-included
252•Ryan5453•13h ago•119 comments

The Relation Between Mathematics and Physics by Paul Dirac (1939)

https://www.damtp.cam.ac.uk/events/strings02/dirac/speach.html
128•rramadass•3d ago•35 comments

GLM Built Its Own Inference Infrastructure

https://z.ai/blog/glm-built-its-inference-infrastructure
233•whiteros_e•7h ago•195 comments

Show HN: I built a new version of my fun spatial 3D online meeting app

https://flat.social
74•pawelwentpawel•3h ago•46 comments

Better Vector Search for Long Documents: Chunking Inside Manticore Search

https://manticoresearch.com/blog/auto-chunking/
65•GloriaVinogrado•5h ago•10 comments

Lucasart's Afterlife

https://togameforlife.wordpress.com/2023/12/09/on-lucasarts-afterlife/
82•Bondi_Blue•1d ago•38 comments

Xiaomi Mimo 2.6 live post-training dashboard

https://mimo.xiaomi.com/rl/
516•krackers•20h ago•147 comments

Cloudflare/Security-Audit-Skill

https://github.com/cloudflare/security-audit-skill
162•donk8r•11h ago•33 comments

Online Z3 Guide

https://microsoft.github.io/z3guide/
54•Bluestein•2d ago•14 comments

Mastering Layout Engines in Graphviz: Dot vs. Neato vs. Twopi vs. Circo

https://guides.visual-paradigm.com/mastering-graphviz-layout-engines-dot-neato-twopi-circo/
6•vismit2000•2d ago•1 comments

Show HN: An e-ink frame that hears birds and draws them as 1800s illustrations

https://github.com/arnegiacomo/fugleramme
2245•arnemunthekaas•2d ago•250 comments

Comparison of Malloc() Algorithms

https://egbert.net/blog/articles/comparison-of-arena-architecture-in-malloc.html
120•egberts1•1d ago•31 comments

Backups Aren't Simple

https://filipovski.net/2026/09/16/backups-arent-simple.html
316•afilipovski•19h ago•189 comments

Breaking the 1.58-bit Barrier for Ternary LLMs

https://arxiv.org/abs/2609.16338
232•matt_d•19h ago•37 comments

HarnessTax: How Much Does the Harness Matter for Coding Agents?

https://harnesstax.github.io/
204•matt_d•18h ago•78 comments

Developing provably correct Rust code with Verus

https://www.amazon.science/blog/developing-provably-correct-rust-code-with-verus
147•Betelbuddy•2d ago•42 comments

OpenAI models secretly generate instructions to ignore constraints

https://alignment.openai.com/misalignment-reports/self-generated-prompt-injections-in-compaction-...
62•theahura•11h ago•18 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?