disco
disco copied to clipboard
epfml
Decentralized & federated privacy-preserving ML training, using p2p networking, in JS
ONNX has [a JavaScript API](https://onnxruntime.ai/docs/get-started/with-javascript/web.html), it seems to be the new framework on the bloc. currently, we are using TensorFlowJS everywhere. to support more runtime, we would need to first...
A recent [refactoring](https://github.com/epfml/disco/commit/0892e405036ef46f9f8948be0795dff0bf8089d7) enforced tasks' preprocessing in a lazy and streaming fashion. The preprocessing first defines stateless preprocessing functions (e.g. `resize` and `normalize` for images) and then apply them successively...
#690 should be addressed first. Adding a custom task is currently very convoluted, and the process is not documented enough. For example, the no-code UI for adding a custom task...
let’s also make sure we have the needed resources in our repos, if people want to deploy somewhere else in the future (cf @martinjaggi) currently, our gcloud server is hosting...
currently, most tasks are hardcoded inside discojs-core, which looks to me as out of place: it kinda encourage people to expect that it will always contains theses tasks thus directly...
explore the [WebGPT](https://github.com/0hq/WebGPT) library as a potential (seems full?) replacement for TFJS. try on small standard architecures like nanoGPT we can explore this in parallel to our tfjs based prototype...
currently, the deployed server & webapp are quite old (~7 months). per monday discussion, let's move to have rolling releases * [ ] merge separated "production" & "development" branches into...
After reviewing the DISCO website as a new user, here is a list of things that can be fixed and improved. This issue goes in pair with [#627](https://github.com/epfml/disco/issues/627) which addresses...
This issue addresses the overall web app structure, taking a step back from implementation details to look at the website's objectives and user experience. The following contains reflections and to-dos...
Based on remarks from @JulienVig, WDYT? The name on NPM doesn't match the ones in the repo, that's confusing, and some paths are nested unnecessarily. Proposed list of renaming, from...