You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 1, 2024. It is now read-only.
Lately have been thinking about the pieces necessary to take this from a hackathon project into a fully developed product for average users. Will be working on a comprehensive, but mainly focused on "backend" (@slavik0329 did 99% of frontend), list here.
Expect edits to this list
Multi-device Identities/Accounts
atm the user has to copy and share public keys with friends.
should be a petname system with ability to query global name systems to bootstrap a contact
File-system CRDT should be stored on disk, not in memory. traversing directories must remain snappy
File-system CRDT hackathon encryption needs to be upgraded to something with stronger security properties
There are two parts to this. 1) encrypting the CRDT which will involves decentralized multi-party encryption 2) encrypting uploaded file data
Reliable replication layer for File-system CRDT
sucks that end devices have to stay online for people to share files...
utilize IPLD/IPNS pinners like web3.storage at first
Once a good solution for a collaborative file-system is built, then the fun begins.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Lately have been thinking about the pieces necessary to take this from a hackathon project into a fully developed product for average users. Will be working on a comprehensive, but mainly focused on "backend" (@slavik0329 did 99% of frontend), list here.
Once a good solution for a collaborative file-system is built, then the fun begins.
The text was updated successfully, but these errors were encountered: