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
| Intro | Intro | 5 min |@liran| Quick Intro. New Members. DIF IPR agreement. |
36
+
| Agenda | Companion Guide Updates | 10 min |@andorsk/Moises|[added dwn and peergos to the comparison guide #229](https://github.com/decentralized-identity/decentralized-web-node/pull/229) <br>[Local, Remote, and Relay Nodes. #225](https://github.com/decentralized-identity/decentralized-web-node/pull/225)|
37
+
|[Ecosystem Updates]()| Updates | 10 min |@andorsk| protocols.preview.benri.io |
38
+
| Agenda | Spec PR Review | 10 min |@csuwildcat|[update the Service Endpoint section of the spec #228](https://github.com/decentralized-identity/decentralized-web-node/pull/228) <br> [added JSON schemas for DWN specification #209](https://github.com/decentralized-identity/decentralized-web-node/pull/209)|
-[Authorization layer should limit the amount of data permitted to be stored by a application #96](https://github.com/decentralized-identity/decentralized-web-node/issues/96)
46
+
-[Add use cases link #83](https://github.com/decentralized-identity/decentralized-web-node/issues/83)
47
+
-[Test Suite Design #213](https://github.com/decentralized-identity/decentralized-web-node/issues/213)
-[as a developer, I can follow docs to run the reference implmentation, so I can test it out and then contribute improvements or passing test-suites #144](https://github.com/decentralized-identity/decentralized-web-node/issues/144)
51
+
-[Support both folder based and schema based object storage #190](https://github.com/decentralized-identity/decentralized-web-node/issues/190)
- Grant: Read|Write access to individual files or folders
84
+
- Conventional login (username + password). Key derivation is from there.
85
+
- Hide metadata
86
+
- Server can't tell if blob is directory of file
87
+
- Technical Difficult:
88
+
- Don't want to depend on DNS
89
+
- 2018: Decided HTTP over P2P Streams
90
+
- Peergos Implementation:
91
+
- Peergos
92
+
- Question: Alan
93
+
- Correlation Inference?
94
+
- Don't consider server based timing attacks are not in scope.
95
+
- Liran: Identity Portion:
96
+
- Node identity
97
+
- User identity <- least happy with PKI global append only log signed statements of username. Add people by username over UX. Considering removing PKI entirely.
98
+
- Question: Capability based.
99
+
- Everthing split into writing subspaces.
100
+
- KP Control
101
+
- W/e Changes you write are atomic.
102
+
- Sandbox application.
103
+
- Not sure if it makes sense in Peergos
104
+
- Dan:
105
+
- How can apps expose public information in public way? Champs. Maps to encrypted blobs.Keep capability of Champ in sync with real data. Look up and do traversal. Web interface. Can publish a website. Can view in any gateway.
106
+
- Henry:
107
+
- Were there challenges around encryption, e.g.
108
+
1. Sharing keys to friends/external participants
109
+
2. Key rolling
110
+
- Cryptree
111
+
- Voila <- 2008
112
+
- Care alot about being post quantum.
113
+
- Grant a read capability is basically sharing a key.
114
+
- Expensive: Revoke write access, rotate all the keys.
115
+
- Sharing capabilities: each person has an inbox. Public encryption key. People write to that to share capabilities.
116
+
- How many?
117
+
- 10 Self Hosters
118
+
119
+
### Issues Discussed:
120
+
121
+
-[Requiring fine-grained capabilities #142
122
+
](https://github.com/decentralized-identity/decentralized-web-node/issues/142) To revisit after Spec alignment. Milestone 1.
123
+
-[Revocation Subtleties #138
124
+
](https://github.com/decentralized-identity/decentralized-web-node/issues/138) - To revisit after spec alignment. Milestone 1.
-https://github.com/decentralized-identity/decentralized-web-node/pull/231 : Going to see if we can get Ian to comment on this. @andorsk to draft a response.
0 commit comments