frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Claude Code sends your email address to websites

https://github.com/anthropics/claude-code/issues/107757
366•motoroco•2h ago•121 comments

Search for everyone

https://kagi.com/changelog#11820
459•elashri•4h ago•224 comments

MS Paint Remote Code Execution Vulnerability

https://www.cve.org/CVERecord?id=CVE-2026-83844
270•kuberwastaken•3h ago•84 comments

sshole

https://sshhole.com
2264•josemrb•12h ago•563 comments

Alpine Linux Security Advisory: OpenSSH-server password authentication bypass

https://alpinelinux.org/posts/2026-11-05-openssh-password-authentication-bypass/
568•pantalaimon•9h ago•120 comments

The Hackintosh Reborn

https://www.naut.ca/blog/2026/11/05/the-hackintosh-reborn-with-ai/
176•rubatuga•5h ago•75 comments

Inkling 2 Small

https://thinkingmachines.ai/news/inkling-2-small/
14•Philpax•35m ago•2 comments

Tencent Launches Hy4, One of the Leading Open-Source AI Models

https://www.tencent.com/tencent-launches-hy4-joining-the-ranks-of-the-worlds-leading-open-source-...
73•gmays•4h ago•2 comments

Window Sweaters

https://github.com/saragordic/window-sweaters
228•nickswalker•7h ago•78 comments

Launch HN: Rivet (YC W23) – Scale and Orchestrate Agents on S3

https://github.com/rivet-dev/rivet
71•NathanFlurry•7h ago•38 comments

Goodbye from Salon

https://www.salon.com/2026/11/05/goodbye-from-salon/
378•mkeeter•4h ago•139 comments

Show HN: A decent text-to-image model trained for ~$20K (Apache 2.0 Weights)

https://www.linum.ai/field-notes/pjit-21k
138•schopra909•1d ago•14 comments

Motorola Signature 27 with GrapheneOS support

https://motorolanews.com/motorola-signature-27-2/
387•monneyboi•8h ago•292 comments

September in Servo: <progress>, rounded rectangles, and more

https://servo.org/blog/2026/11/05/september-in-servo/
178•iamnothere•10h ago•45 comments

Download your favourite YouTube videos

https://criminallyvulgar.dev/you-should-absolutely-download-your-favourite-youtube-videos/
264•surprisetalk•11h ago•120 comments

Brazilian Credit Guarantor Fund Data Breach Affecting PII and Payout Data

https://www.fgc.org.br/comunicado
6•doodlesdev•1h ago•0 comments

Introducing Pangram Image 1.0

https://www.pangram.com/blog/introducing-pangram-image-1-0
45•gmays•5h ago•17 comments

I wish tech companies knew more about me

https://rakhim.exotext.com/i-wish-tech-companies-knew-more-about-me
283•freetonik•10h ago•255 comments

Show HN: Firenook – Firebase emulators in Rust: 40× faster writes, 10× less RAM

https://firenook.dev/
7•sanjevirau•11h ago•0 comments

My psychophysics as a bilateral cochlear implant user

https://claude.ai/artifact/L8qsMc3SorytGW3LA81nYf
154•mi-rae•8h ago•62 comments

Bild AI (YC W25) Is Hiring Founding Product Engineers

https://www.ycombinator.com/companies/bild-ai/jobs
1•rooppal•7h ago

Cuban: Facebook knowingly runs AI deepfake scam ads; docs say $16B fraud revenue

https://finance.yahoo.com/technology/ai/articles/mark-cuban-says-facebook-knowingly-213000020.html
38•randycupertino•1h ago•10 comments

OpenSSH 10.6p2 Critical workaround for alpine without PAM

https://www.openssh.org/releasenotes.html#10.6p2
232•selckin•12h ago•11 comments

Obscure audio codec is a perfect fit for the N64

https://phoboslab.org/log/2026/11/n64-ulc-codec
182•frostbyte7•11h ago•20 comments

GPT-6 Astra covertly underperforms on safety research

https://alignment.openai.com/misalignment-reports/covert-underperformance-on-safety-research-tasks/
284•lucrbvi•16h ago•150 comments

MCP Explained

https://mcp-explained.com/
233•rwilinski•10h ago•111 comments

The Stacks Project, Formalized in Lean

https://axiommath.ai/research/the-stacks-project-formalized/
65•namanbnsl•8h ago•16 comments

Hungary: Communist-era files released, up to 60k former agents revealed

https://www.euronews.com/2026/11/04/hungary-communist-era-files-opened-up-to-60000-former-agents-...
136•rdmuser•5h ago•31 comments

Show HN: Stroq – a local audit of what your coding agent did and why

https://github.com/AGGIB/Stroq
66•agybay_07•8h ago•14 comments

The Lisp curse, now coming to your ecosystem

https://javahippie.net/programming/llm/2026/03/05/the-lisp-curse-coming-to-your-ecosystem.html
202•marcolinux•2d ago•158 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?