00:05:12.176,00:05:15.176
Lance Byrd: https://github.com/dhh1128/did-method-webs

00:05:51.338,00:05:54.338
Lance Byrd: https://dhh1128.github.io/did-method-webs/index.html

00:07:12.563,00:07:15.563
Lance Byrd: https://hackmd.io/@u54fb76oTJW272B17r4YPg/HJfCB_S92

00:14:38.132,00:14:41.132
Alex Andrei: what is the difference?

00:17:16.527,00:17:19.527
Alex Andrei: why would you use dids and keri over bluetooth instead of just using aids over bluetooth

00:17:53.256,00:17:56.256
Daniel Hardman: Alex: DIDComm?

00:18:06.521,00:18:09.521
Daniel Hardman: (SICPA does DIDComm over bluetooth, for ex)

00:19:38.054,00:19:41.054
Alex Andrei: you only get didcomm copatability but from a security perspective there is no need to use keri with didcomm

00:21:37.751,00:21:40.751
Alex Andrei: isn't did webs a subset of did keri?

00:23:31.617,00:23:34.617
Lance Byrd: https://github.com/WebOfTrust/did-keri-resolver

00:35:48.337,00:35:51.337
Alex Andrei: one thing I see is that if we want to have the kels and tels in addition to did diddoc it will grow pretty fast

00:40:05.115,00:40:08.115
Alex Andrei: you need to commit the signature of the status list

00:55:18.371,00:55:21.371
Alex Andrei: so did webs is the global "watcher" in keri terms