ArVID220u | 1 year ago | on: Snyk security researcher deploys malicious NPM packages targeting cursor.com
ArVID220u's comments
ArVID220u | 2 years ago | on: How We Made PostgreSQL a Better Vector Database
According to the single-threaded QPS experiments, your DiskANN solution should clock in at about 4.5ms latency (1000ms/224QPS) whereas pgvector is about 5.8ms latency (1000ms/173QPS). How is that possible? My (very shallow) knowledge of DiskANN vs HNSW tells me that DiskANN should generally have higher latency than HNSW — DiskANN needs to touch the SSD while HNSW only touches RAM.
Also, compared to pgvector and HNSWPQ in faiss, how much less RAM does your DiskANN-based solution use?
ArVID220u | 3 years ago | on: GPT-4 is phenomenal at Code
ArVID220u | 3 years ago | on: Show HN: Anysphere, home for important, long-form conversations
ArVID220u | 3 years ago | on: Show HN: Anysphere, home for important, long-form conversations
ArVID220u | 3 years ago | on: Show HN: Anysphere, home for important, long-form conversations
I do agree that there is a general problem where companies make hyperbolic claims, especially when it comes to security/privacy. For example, “zero trust” has been abused by so many people that even in the cases where it might apply, you cannot say that it applies to you because the term has lost its meaning. In our case, users do not need to place any trust in our servers, but we decided not to call it “zero trust” because people have taken it to mean “trust your employees less” or something else similarly outrageous.
If you have any suggestions for how we can improve our messaging here I’d love to take them. In other words, how could we convey that we are indeed the only completely private communication platform, without provoking a reaction similar to yours?
ArVID220u | 3 years ago | on: Show HN: Anysphere, home for important, long-form conversations
we did not hire snyk, but we reached out to them after seeing this and they apologized. we did not get any confirmation of what exactly they were trying to do here (but i think your explanation that someone there suspected a dependency confusion vulnerability is plausible. though it's pretty irresponsible imo to do that on public npm and actually sending up the env variables)