Open b1conrad opened 1 year ago
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"})
+ raise dido event "invitation_accepted" attributes {
+ "invite":invite, "my_did":new_did{"id"}
+ }
}
}
The dido:invitation_accepted
event could then be selected by a rule (in another ruleset) that could obtain
"invitee"
event:attrs{["invite","label"]}
event:attrs{"my_did"}
event:attrs{["invite","from"]}
event:attrs{"invite"}
, such as perhaps the time when the invitation was created (computed as time:new(event:attrs{["invite","created_time"]}*1000)
)@b1conrad This is doable, and I'm in the process of implementing it.
Can we have a brief meeting, at your convenience, to talk through this? @joshmann35
We need the
dido
library to raise an event at the moment when a DID exchange results in a connection being established. This needs to happen both for the pico receiving the invitation and the one that generated it. An application ruleset (that usesio.picolabs.did-o
as a module) would react to this event and maintain a list of connections, on top of thedidMap
function that the did-o ruleset already provides (the app ruleset is not part of what is asked for here, but is the rationale).Event attributes need to include