Biweekly Sync Up May 29th, Tuesday 3pm UTC

[pgte]

• Meeting: https://protocol.zoom.us/j/586782711
• Notes: https://cryptpad.fr/code/#/1/edit/QetfopclzrLUFM44vJxepg/5VwZGP+x9+YeSaM6hGVVxzWT/

See you then!

[pgte]

Some discussions in the agenda for tomorrow's meeting:

• identity:
  • discuss proposal for key management and address book (PR)
• peer-crdt-ipfs:
  • specific protocol to increase sync speed
  • add vector clocks to enable this
  • handshake protocol
• garbage collection:
  • how to infer causal stability as presented here
• ACLs:
  • should we implement “Access Control for Weakly Consistent Data Stores” (see discussion in CRDT: ACL #25)?

If you have other item please add them in advance to the notes pad.

[pgte]

#Meeting nodes:

Dynamic Data and Capabilities WG — May 29th, 2018

• Lead: Pedro Teixeira (@pgte)
• Notetaker: @joaosantos15
• Attendees:
  • @gpestana
  • @diasdavid
  • @joaosantos15
  • @satazor
  • @pgte
  • @lance
  • @fritzy
• Zoom.us meeting URL
• Recording

Agenda

• Ask everyone to put their name into the list of attendees

• Ask for a volunteer to take notes

• Everyone can add items to this agenda for things they would like to discuss

• Round of intros and updates

  • Introduce yourself and your interest in this subject
  • What have you accomplished since the last meeting?
  • Were there any blockers? If so, which ones? Is it still blocked? Why?
  • What is the next important thing you should focus on?

• Discussions:

  • identity:
    • discuss proposal for key management and address book (PR)
    • discuss a URI datastore that can be replicated, see Identity Hub
    • discuss address-book overlap with Decentralized LDAP: crowdsourced contact list, private contact list, etc.
  • peer-crdt-ipfs:
    • specific protocol to increase sync speed
    • add vector clocks to enable this
    • handshake protocol
    • spec here: RFC: Replication protocol ipfs-shipyard/peer-crdt-ipfs#5
  • garbage collection:
    • how to infer causal stability as presented here
  • ACLs:
    • should we implement "Access Control for Weakly Consistent Data Stores" (see discussion in CRDT: ACL #25)?

• Questions

2 Week Updates:

@pgte

• Concluded:
  • Helped João Santos on a fun hack: Ethereum-based log in into Peer-Pad, materialised in this PR
  • Completed, documented and released delta-crdts package
  • Specified proposal for fast sync for peer-crdt-ipfs
• In progress:
  • Joined discussions with João Santos and André Cruz about identity management in peer-star
• Blocked:
• Next:

@gpestana

• Concluded:
• Merged feat(json-crdt): Adds explanation about JSON-CRDT
• Reading about snapshotting and garbage collection for CRDTs
• Blocked:
• Next:
• Find some issue to work on?

@satazor

• Concluded:
• In progress: Identity (did, auth, address-book)
• Blocked:
• Next:

Questions

• Q: What are the priorities to work on?
  A:
• Q: Is there a way to track all the current endeavours and discussions? (Examples: open problems, building blocks, etc)
  A:

Other notes

@fritzy Peer identity: There is working code with DID DOcuments and creating proofs, and an identity service, in shipyard that can be converted to a REST DID-Method. (add link later). @satazor questioned about the need for a centralized server to make it work.

@pgte mentioned that a method to support several DID methods would be an option.

@satazor mentioned the concept of an identity hub: https://github.com/decentralized-identity/hubs/blob/master/explainer.md#stores

@diasdavid MFS, you can create virtual directories, but can also me used as a UNIX file system. IPFS Drive,1,2,3.
Read about MFS, Files API and Shared Volumes at:

• Great video - https://www.youtube.com/watch?v=FX_AXNDsZ9k
• https://github.com/Gozala/ipfs-drive
• ipfs drive ipfs/specs#174
• Unite the Files API 🗂 ipfs/specs#98
• in a go-ipfs node, do ipfs files —help
• Files API spec ipfs/specs#88 (issue about the spec not existing yet)
• https://github.com/ipfs/js-ipfs-mfs wip in js

Dream API:

• The class that represents the type adds the function to do access control.
• See how the Dream API relates to Identity.

@diasdavid @pgte discussed using accumulators (need help to complete here)

Discussion:

• @pgte suggests making short summaries about the various Identity platforms (uPort, Peer-Identity, btcr, etc).

• Use a passphrase on Identity, or rely on device keys?

• View each proposal's attack vectors and analyze them.

• Analyze The Update Framework

• Docker Notary

• Key rotation discussion - Key Rotation ipfs/specs#31

• Privacy issues:

  • Know who has access to a document

  • Know what the document has

  • Encryption at rest & encrypt at transmission

[pgte]

Video URL: https://www.youtube.com/watch?v=U1GK88QiX2Q