UX flows for AOL subdelegation

[expede]

No description provided.

[depatchedmode]

When you say "subdelegation" do you mean using the AOL I got from Application A to "login" to Application B?

[expede]

@depatchedmode this could have had WAY MORE info in it! 😅

There are a couple scenarios, but essentially anywhere I want to give another app access to some but not all of my capabilities. At least in concept, this may or may not be the same application; maybe it's to a less trusted device.

As some examples:

As a Laconic Wallet user I may only want to give access to my Cosmos account (but not my LNT stuff) for the next week while I'm on my a borrowed iPad that has no password.

As a WNFS user, I want to share this awesome playlist between https://diffuse.sh and a videogame project that I'm working on, but not other things like my vacation photos.

[depatchedmode]

Sweet. This helps clarify the scope.

Moving to and from less trusted devices is a very rich set of flows to explore! Also, was not yet aware of diffuse.sh — checking it out now.

[avivash]

Sweet. This helps clarify the scope.

Moving to and from less trusted devices is a very rich set of flows to explore! Also, was not yet aware of diffuse.sh — checking it out now.

built by @icidasset 🙌🏼

[depatchedmode]

The things that a person will be concerned about when sub-delegating:

• scope of the delegation: what permissions am I granting
• identity of the thing I'm delegating to: who exactly am I granting them to
• time horizon of the delegation: how long are these permissions going to last?
• permanence—how final is this decision? (eg. process for revocation)

I think WNFS' default folder structure, and practices about how it is used, is one of the most powerful first places to construct and improve sub-delegation UX.

[jeffgca]

PDF export from the current state of the FigJAM

App sub-delegation.pdf