Sorry I missed the 2min warning for the end of the call. Thank you for the call, I think it was a great discussion and I’m looking forward to continuing it!
As a next step, I’m proposing that we organize ourselves such that we can push the different action items we’ve been discussing further. From the discussions so far, they seem to be
- Showcasing and communicating DeAI projects and innovations on the IC (within the community and beyond)
- Working out unique value propositions for consumers and users of DeAI
- Educational materials and documentation
- Wish list of features and components that’d be beneficial for development (incl. GPU subnet as a community effort)
- Technical initiatives like on-chain vector databases
What do you think about these? Are any other items missing?
Would you like to work on any of these items or even take the lead?
And I unfortunately just noticed that the screen recording software I used didn’t capture the audio correctly, so the recording is not very helpful. Any good solutions for the recordings anyone can propose?
These are the few notes I took:
- migrating libraries: size (below 2MB) → zipping, no multi-threading
- FAISS: one dependency might be challenging
- Vector db: size limit challenging? e.g. Quadrant (in Rust)
- Wish list: dynamic library (shared across projects, instead of every project hosting library itself), native system AI/LLM, consumer-facing benefits consideration
- @ildefons showcase post: Introduction of MotokoLearn V0.1: on-chain training and inference of machine learning models
Please add to these notes with your own.