dennis16384
Joined 2 years ago
Joined 2 years ago
Wasm size from 30Mb to 300kb and 1.5x speedup. It's definitely worth it for performance or distribution size.
Why bring server software to edge devices? Because its fucking awesome!
How do you extract and relate to each other the facts from the documents that require comprehension and not simple similarity matching using common embeddings models?
Recently started some agentic features for paid version, and this lead to a side project https://eatmydata.ai - a question-to-sql-to-dashboard builder, where data doesn't get exposed to AI (with bundled in-browser SQLite vector search, NER and many other features).
The latter is open-sourced under MIT: https://github.com/eatmydata-org/eatmydata
We have low-cardinality data and yes this is safe to share and required to build an actual query.
Then we have high-cardinality and possibly PII - there’s absolutely no reason to share that data, there’s nothing for LLM to analyse there. Also semantic index (vector search) will find relevant records much faster and more accurately that any chain-of-thoughts just with an LLM-authored search fn call.
Further there are continuous numerical values and there’s not much LLM needs to see in there either. We can say, for example, if you look at data distributions when building your analysis, it can drive your analysis logic, but another point of view here is taht it creates unnecessary bias instead.
For example, there is no way neither in Claude nor in ChatGPT to run your own WASM or JS or whatever AI produces directly in user's browser context as a tool/skill - there is no call site for that. The only option is remote server-side.
My whole idea was that AI can perfectly write SQL and dashboard code knowing only the shape of your data and not it's contents. With direct upload to vendor now we're forced to share the contents.