dmezzetti
With TxtAI, I've seen a large uptick in PRs (https://github.com/neuml/txtai/pulls?q=is%3Apr+is%3Aclosed+s...). While the extreme verbosity of Claude messages and commits is very annoying (plus the constant defending itself on why it's a bug), I do think it's a positive that more people are enabled.
It does require reviewing the PRs. Some can be tricky just like a human. For example I did merge this PR (https://github.com/neuml/txtai/pull/1136) and it would have completely broke search. But a human could also do that.
From an open source standpoint, I say the more the better. You just have to be willing to do the work to review and no not just having AI agents to review what the AI agents are submitting. There still needs to be a human in the loop, if you care about quality.
If you're interested in an ONNX version and a permissively licensed TTS Tokenizer, I built a pipeline for that a while back: https://huggingface.co/NeuML/kokoro-base-onnx
I've been working on small local models for years with txtai (https://github.com/neuml/txtai). I've published close to 100 models that can run local for RAG, Agents, Vector Search and more (https://huggingface.co/NeuML/collections).
Keep up the great work!
Top 3 posts as of this moment are all about Claude.
Related paper that's a good read: https://arxiv.org/abs/1908.08962
It would be great to see how it compares to Faiss / HNSWLib etc. I'd will consider integrating it into txtai as an ANN backend.
But scaring people off from security reports also isn't a great idea either.
A cautionary tale for many of these types of tech platforms, this one included.
Even with a following, most of the time when you publish it goes into the abyss. Every once in a while something hits but most of the time it takes a lot of patience and resolve. I've had some good visibility over the years from Reddit and Hacker News (though any post I make now on HN is marked as [dead]). It's not always fair and others can "pay" to get the visibility.
I've seen some of the other comments talking about the burden of OSS but I haven't felt that. I set my own agenda and fix what I want to fix. If someone wants to change my priorities that becomes a paid effort.
You can do the same with DuckDB and Postgres too.
Also when someone finds a bug, the maintainers are under no obligation to fix it or fix it with any timeline or even debug what's going on. If someone wants an immediate response they should provide compensation.
A common misconception is that OSS developers do everything for free. They do what THEY want for free. If YOU want to change their priorities, companies need to compensate for that.
In general RAG != Vector Search though. If a SQL query, grep, full text search or other does the job then by all means. But for relevance-based search, vector search shines.
For those into vector storage in general, one thing that has interested me lately is the idea of storing vectors as GGUF files and bring the familiar llama.cpp style quants to it (i.e. Q4_K, MXFP4 etc). An example of this is below.
https://gist.github.com/davidmezzetti/ca31dff155d2450ea1b516...
I just put this example together today: https://gist.github.com/davidmezzetti/d2854ed82f2d0665ec7efd...