private sharing - OrbitDB
trans© trailmarker
Low latency, eventually consistent private sharing using OrbitDB
- purpose :
- Replication latency using OrbitDB
- is considerably lower than WNFS's
- Combine that with
- ephemeral encryption
- - gloss :
- share encryption cyphers, possible since WNFS is encrypted
- in a dynamic manner
- based on shared secrets and some function of
- the time derived from the exchange
- could rely on OrbitDb write access control,
- but careful combining of ephemeral cyphers matching the sharing topology seems possible
- can use log or feed dbs as an event driven programmable two way communication channel
- for eventually consistent near real-time collaboration can use OrbitDB docs store with CRDT
- makes it possible to provide
- private replication
- full verifyable history and provenance if desired
- trans-copyrighted sharing
- OrbitDBs in use can be rotated on a daily basis
- Can save into archive on a daily/hourly basis or after a specified period of inactivity
- Instead of saving directly to WNFS incrfemental updates can be shared
- via orbitdb queues.
- all changes are shared with low latency
- Saving to fission drive can happen when archiving
- While the feed stores maintains all versions
- as a
- Good for giving a higher granularity of change
- When archiving daily logs can be turned into weekly or even mothly summaries
-