liang
@liang
enuff of the fluffs, to truly allow users "own" their data we need: 1. store data on their own server or locally on their device 2. store data on a public ledger/storage network with guaranteed data availability, and .. encrypted This is very different from owning assets where it is sufficient to just own the key
4 replies
0 recast
5 reactions
liang
@liang
comparing to running their own "server", local-first seems to be the most viable approach as far as distribution and adoption are concerned
1 reply
0 recast
0 reaction
liang
@liang
So the ideal value prop of "data wallet" should include data sync/backup on client device (browser extension, desktop app, mobile)
1 reply
0 recast
0 reaction
liang
@liang
again this is much heavier than asset wallet where we only need to make sure the keys are persisted and secure
1 reply
0 recast
0 reaction
Royal
@royalaid.eth
Dropbox but decentralized?
1 reply
0 recast
0 reaction
liang
@liang
Yes. Dropbox and beyond. more like dropbox + db backup consolidated around and owned by users
1 reply
0 recast
1 reaction
Royal
@royalaid.eth
I have been thinking about this a bit in my free time and have some ideas around it but implementing them always has the Achilles of the DB being a central point of compromise because of how query engines work currently.
2 replies
0 recast
0 reaction
Royal
@royalaid.eth
For an outline, you would take all of the files a user has and chunk them out, encrypt them using forward secrecy, and then store all that metadata in an index, let's say SQLite. You would then upload the SQLite db and have that be encrypted too.
1 reply
0 recast
0 reaction
liang
@liang
Curious why do you need such a DB? for what use case?
1 reply
0 recast
0 reaction