Bruce Conrad

Totally understand the hope that implementers will move away from deprecated protocols. That being said, I need to second the suggestion to make the change in the spec. We (ACA-Pico)...

As a workaround, I am introducing this ruleset into a protected repo, having installed it in the root pico (which doesn't otherwise participate in the application). It then can serve...

Have tested this with a couple of rulesets, and it works. Waiting for a change to see how well Flush works.

The one proviso is that it cannot be used to hold/install a ruleset into itself. Hence using a pico that doesn't otherwise participate in any way in the application.

While the new ruleset was written in the context of a protected repo, it leaks no information from that project, and is general-purpose. It will be maintained [in the PicoStack...

On the invitee side of a new connection, it might suffice to add this to the `receive_invite` rule: ``` } fired { raise dido event "send_trust_ping" attributes event:attrs.put("did", invite{"from"}) +...

Can we have a brief meeting, at your convenience, to talk through this? @joshmann35

The community has decided to deprecate `did:peer:3` and so we should use [DID Peer Numalgo 4](https://hackmd.io/@dbluhm/did-peer-4) instead.

There is a sample implementation here: https://github.com/dbluhm/did-peer-4

More detailed code can be found here: https://github.com/dbluhm/did-peer-4-ts Along with the associated web application, here: https://dbluhm.github.io/did-peer-4-ts/