Module own_device
Expand description
Using an action on another of the person’s own devices and hearing its answer.
An app on one device names one of the person’s enrolled devices, an
application and one of that application’s actions; the host on this
device admits the request, carries it to the other device as an ordinary
InvokeRequest on a workspace both devices
share, follows it there, and records the other device’s outcome as this
invocation’s. Nothing here is a new wire format: the other device sees
the same request any of the person’s devices sends it, and decides it
for the device the transport authenticated.
Only the person at this device reaches it, for an application’s own actions: an agent, a bot, a Shortcut or another device gets no reach across devices it lacks here.
Structs§
- Checked
- One admitted own-device invocation, checked: the device’s key, the application, the action and what the action is given.
- Invocation
- What an own-device invocation asks for: application
app’s actionactionon its resourceresource, on the device whose public key isdevice, witharguments.
Constants§
- INVOKE
- Invoke an action on one of the person’s devices; answers its outcome.
- PROVIDER
- The provider the host answers own-device invocations under.
- RESOURCE
- The resource the invocation is an action of.
Functions§
- decode_
device - A device key from its 64 lowercase hex digits.
- target