frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Linux support is coming to Snapdragon X2 Series

https://www.qualcomm.com/news/onq/2026/09/snapdragon-summit-agentic-ai-pcs-linux
310•aaronday•7h ago•137 comments

Claude discovers a novel enzyme system with CRISPR-like repeats

https://www.anthropic.com/news/claude-discovers-novel-enzyme-system
596•raahelb•12h ago•605 comments

ArXiv receives multiyear commitments to support it as an independent nonprofit

https://blog.arxiv.org/2026/09/23/arxiv-receives-multiyear-investment/
132•JohnHammersley•7h ago•16 comments

Feds Target AI Critics as "Foreign Agents"

https://www.kenklippenstein.com/p/feds-think-ai-critics-are-foreign
226•nmeagent•5h ago•205 comments

Early rogue AI agent activity and attempts to hack found on urlquery.net

https://transluce.org/agent-activity
7•snikolaev•1h ago•1 comments

VSCode's SSH Agent Is Bananas (2025)

https://fly.io/blog/vscode-ssh-wtf/
191•Rapzid•9h ago•119 comments

Ideas on modernizing the open-source desktop

https://lwn.net/SubscriberLink/1095425/2d9f411252325784/
49•signa11•3h ago•26 comments

Making portable my unportable transputer C compiler

https://nanochess.org/transputer_c_compiler.html
31•nanochess•2d ago•4 comments

Contrastive Language Models

https://contrastive-lm.notion.site/
16•erichocean•2h ago•4 comments

Virtio-nvgpu: Near-native Nvidia GPU access inside a KVM guest

https://github.com/nestrilabs/virtio-nvgpu
58•WanjohiRyan•5h ago•27 comments

Meta VR Glasses

https://www.meta.com/vr-glasses/
347•polymorph1sm•6h ago•303 comments

The "Windows XP Box" (2003)

https://www.mini-itx.com/projects/windowsxpbox/
116•doubletwoyou•2d ago•16 comments

Lazydraw: Terminal ASCII editor for drawing diagrams and sketches

https://github.com/mpospirit/lazydraw
10•masterpos•1d ago•1 comments

Fixing the Portobello Police Station Clock

https://pointinthecloud.com/2026-04-11-211700.html
415•avidly•15h ago•95 comments

Why 'What's Opera, Doc?' looks like that

https://animationobsessive.substack.com/p/why-whats-opera-doc-looks-like-that
32•CharlesW•14h ago•2 comments

Mercury 2.5 LLM hits 770 tokens per second

https://artificialanalysis.ai/models/mercury-2-5
88•Retro_Dev•8h ago•54 comments

Six-year-old breaks women's world Rubik's Cube record [video]

https://www.youtube.com/watch?v=UCMRgvyTm08
31•1659447091•1h ago•10 comments

Making Tailscale Faster

https://tailscale.com/blog/making-tailscale-faster
140•yarapavan•12h ago•51 comments

Italian parliament votes for return to nuclear energy

https://apnews.com/article/italy-nuclear-chernobyl-4891b6b7c7791ae84db6b0bf0f7cf567
709•geox•13h ago•456 comments

The mystery animal on an ancient god's head

https://signoregalilei.com/2026/09/13/the-mystery-animal-on-an-ancient-gods-head/
88•surprisetalk•1d ago•26 comments

Lambda MicroEgg

https://www.philipzucker.com/lambda_miller_egg/
35•philzook•3d ago•1 comments

Australia says OpenAI agent hacked into government website

https://www.channelnewsasia.com/world/australia-openai-agent-breach-government-portal-6406411
108•doppp•5h ago•70 comments

A brief history of Windows scroll bar shortcuts

https://devblogs.microsoft.com/oldnewthing/20260922-00/?p=112719/
132•tybulewicz•12h ago•67 comments

Tokens too cheap to meter

https://jyn.dev/tokens-too-cheap-to-meter/
278•teoruiz•21h ago•192 comments

Show HN: An open-source manufacturing ERP/MES/QMS

https://carbon.ms/self-hosted
24•barbinbrad•5h ago•12 comments

Data liberation: Apache Kafka's native cluster mirroring

https://developers.redhat.com/articles/2026/09/22/data-liberation-apache-kafka-native-cluster-mir...
7•fvaleri•1d ago•1 comments

Solving for faster SHA-1 collision detection

https://sam.dev/blog/faster-sha1-collision-detection
18•srijs•2d ago•5 comments

LensVLM: Compressing long context as images, expanding only relevant pages

https://huggingface.co/apple/LensVLM-9B
68•victormustar•11h ago•7 comments

Gemini 3.8 text-to-speech

https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-3-8-text-to-speech/
289•swolpers•15h ago•129 comments

FLAWED's Flaws and What This Means for Industry Research

https://suhacker.ai/p/flaweds-flaws-and-what-this-means-for-industry-research/
19•tob_scott_a•5h ago•4 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?