create separate email verification flows for web3.storage and nft.storage

[heyjay44]

NB: This is a nice-to-have for MVP and a fast follow if we don't get to it

[travis]

I believe we still don't have a concrete implementation plan for this.

The problem is that we don't send anything that we could use to decide whether to send a web3.storage email or an nft.storage email along with the access/authorize capability execution.

I believe there's also some disagreement or uncertainty about whether authorizing an agent against a web3.storage account should automatically authorize that agent against an nft.storage account. There are implications for the user experience in both w3console and w3cli of this decision so I think we need to figure this out at a product level and then figure out how we implement the desired functionality given the system we have.

@dchoi27 @heyjay44 I'm not sure there's a canonical description of how this should work for the user in w3console or w3cli - if there is could you link that here and if not could you write something up as soon as you have bandwidth? Primarily looking for user flows for:

1. a web3.storage user in w3console
2. an nft.storage user in w3console
3. a web3.storage user in w3cli
4. an nft.storage user in w3cli

Doesn't need to be anything fancy, but it's important that we specify what happens for, eg, a user who has used nft.storage before but is using web3.storage for the first time since that gets at the crux of the implementation challenges here. I'd be happy to chat in a zoom or something if that's helpful.

Also apologies if I'm misremembering a decision we made here!

[dchoi27]

@heyjay44 since we said this wasn't going to be in phase 4, we should change the text of the root issue

@travis i think we're fine to have the single branded email for now, and that it's fine if a user doesn't go through the email flow if they already have an account. the main user story where this might matter is:

• if a developer has their user sign up for web3.storage or NFT.Storage
• that user already has registered for the other product with their email address and has an active agent "logged in"
• they might end up using web3.storage or NFT.Storage without ever seeing the terms of service

this is pretty edge case though, and we can figure out if/how we need to solve it when we integrate w3up with NFT.Storage!