Having spent some time in the anti-abuse and Trust & Safety space, I always take these vendor reports with a massive grain of salt. It’s a classic case of comparing apples to vendor-marketing oranges. A headline screaming about an 84% miss rate sounds like a systemic collapse until you look at the radically different constraint envelopes a global default like GSB and a specialized enterprise vendor operate under.The biggest factor here is the false-positive cliff. Google Safe Browsing is the def

Comments moved to https://news.ycombinator.com/item?id=47172119.

There's na open issue to address this exact need. I haven't figured out a good compromise yet, but an option to include symbols would be good.https://github.com/samuelclay/hackersmacker/issues/3

Boris from the Claude Code team here.Some of the engineers working on the app worked on Electron back in the day, so preferred building non-natively. It’s also a nice way to share code so we’re guaranteed that features across web and desktop have the same look and feel. Finally, Claude is great at it.That said, engineering is all about tradeoffs and this may change in the future!