标签：#hack

Author here. I wrote this as a visual companion to the 2017 FAISS paper ( https://arxiv.org/abs/1702.08734 ), focused on the parts I found hardest to grok from text alone. The article covers a subset of what FAISS does, with the paper as the source of truth. NSG, FastScan, IMI are not covered here, they'll get their own articles. I'd be especially interested in feedback on: - the IVFPQ / IVFADC explanation, particularly the LUT reuse argument - whether the GPU part captures enough of the actual

Hi HN, I am having AI build me a local Gin Rummy trainer and it cannot figure out medium and hard bot strategies, they keep losing to easy! The point of this is to help me learn so I don't really know how to advise it on strategies. Right now it's just looping through tests and modifying but it keeps not improving. Does anyone have any recommendations or guidance for strategies I could suggest to it?

It was discussed a year ago. https://news.ycombinator.com/item?id=44235467

I'm pretty tired of seeing AI-related content everywhere. When I open Hacker News, close to half of the top submissions are AI-related. It's the same on social networks as well. I miss the times when there was a lot of technical content that took time and mental energy to understand. Nowadays, it's pretty hard to discover it. On HN, I see that a lot of technical articles don't make it to the front page, so sometimes I just search for them in the submissions. Not only is there less content, but d

We launched Infracost on HN five years ago ( https://news.ycombinator.com/item?id=26064588 ) where our CLI generated cost estimates for infra-as-code, e.g. "this Terraform PR adds $400/mo". The idea was to shift cloud costs (FinOps) left, so engineers get visibility of costs before deployment and make better decisions. Earlier this year we started seeing agent traffic in our logs and it looked like coding agents were calling our CLI. But that CLI wasn't designed with coding agents in mind. We we

Hackers are convincing Meta’s AI support chatbot to let them take over other peoples’ accounts: A video posted on X showed the step-by-step process to hack someone’s Instagram account. The hacker allegedly used a VPN to spoof the targets’ presumed location to avoid triggering Instagram’s automated account protections. Then, the hacker opened a chat with Meta AI Support Assistant and asked the bot to add a new email address to the target’s account. The chatbot can be seen sending a verification code to the email address provided by the hacker; the hacker then shares the verification code with the chatbot, which prompts the chatbot to show a button to “Reset Password.” The hacker enters a new password and takes over the victim’s account...