Why would any content producer want to make it easier for AI bots to scrape their site? Perhaps that's too broad, but there's no way any free / open ad-supported content producer would ever want to support this. Someone needs to figure out microtransactions soon before all the content producers shut up shop, and the growth of open / openish knowledge grinds to a halt.

Prompt engineering and massaging should be unnecessary by now for such trivial asks.

Or just run json.dumps on the correct answer in the wrong format.

It's easy to say this, and I am definitely down on the boomers, but I'd say the folks running Europe before WWI were probably a worse generation than the boomers.

TSLA investors don't care (as long as Musk is still there to keep them believing). Years of bad news, and the stock is only 10% off it's all time highs.

https://finance.yahoo.com/quote/TSLA/

CSS and JavaScript are like two dysfunctional law enforcement agencies fighting over jurisdiction.

All web standards are like this, and then the battle continues when it comes to browser implementation.

Yes, nothing on that or sqlite-vec (both of which seem to be apples to apples comparisons).

https://zvec.org/en/docs/benchmarks/

I maintain a fork of sqlite-vec (because there hasn't been activity on the main repo for more than a year): sqlite-vec is great for smaller dimensionality or smaller cardinality datasets, but know that it's brute-force, and query latency scales exactly linearly. You only avoid full table scans if you add filterable columns to your vec0 table and include them in your WHERE clause. There's no probabilistic lookup algorithm in sqlite-vec.

You're absolutely right—sqlite-vec currently only supports brute-force search, and its latency does scale linearly with dataset size. We did some rough comparisons using its benchmark tools: on the SIFT dataset, latency was around 100ms; on GIST, it was closer to 1000ms. In contrast, with zvec's HNSW implementation, we get ~1ms latency on SIFT and ~3ms on GIST, while achieving recall@100 of 99.9% on SIFT and 97.7% on GIST.

FWIW "You're absolutely right" broadly declares "a human is not piloting the keyboard"

You're right that we didn't include sqlite-vec in our initial benchmarks—apples-to-apples comparisons are always better. I've actually added basic zvec tests to my fork of sqlite-vec (https://github.com/luoxiaojian/sqlite-vec), so feel free to give it a try. We'll also be publishing a more complete performance comparison in an upcoming blog post—stay tuned!

In these fractious times, I think we're all very good at scrutinizing other side of the aisle, and not so good at self-reflection.

As a committed centrist, I am very good at fairly scrutinizing everything. /s

You joke but you’d be amazed at the Reddit front page. It’s hard to tell anymore if the comments are even people, but I have noticed many fake posts of some Trump tweet he never actually made getting traction.

It’s so easy to verify his public statements. Did he really say that? Just go look.

Yet time and time again people get baited into rage mode. It’s more satisfying to post than it is to do 30 seconds of research.

> required. No user interaction. The vulnerable code was introduced in a 2015 commit and sat undiscovered for nearly 11 years.

I think about this quote a lot: given enough eyeballs, all bugs are shallow