Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

description of beta migration #139

Closed
wants to merge 2 commits into from
Closed

description of beta migration #139

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4f02b7c
description of beta migration
jchris Nov 7, 2022
d35639a
copy from David
jchris Nov 11, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions packages/access-api/src/utils/html.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,6 +86,13 @@ export const ValidateEmail = ({ delegation, ucan, qrcode }) => (
{delegation.capabilities[0].nb.identity.replace('mailto:', '')} was
confirmed. You may close this window.
</p>
<p>
During the beta period, uploads via w3up will only appear via the beta
APIs, and not on the website. Eventually, existing uploads from the old
APIs will be migrated to this API. Please use a unique email address for
beta accounts that you would like to link to NFT.Storage after the beta
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't this be web3.storage instead of nft.storage ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is for NFT.Storage, so people who are looking for free NFT storage know what to do. Maybe the wording needs to be more clear.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but isn't this true for web3.storage also ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

basically we will treat all account as web3 storage accounts unless the user tell us they are nft.storage accounts. @dchoi27 mind looking at the verbiage?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be more confusing to the user if we tell them existing web3.storage uploads will be migrated to w3up, rather than w3up uploads getting migrated to web3.storage (from their perspective, it should be one and the same). Let's go with something like:

During the beta period, uploads via w3up will only appear via the beta APIs, and not on the web3.storage or NFT.Storage websites, even if the associated email addresses are the same.

At the end of the beta period, web3.storage and NFT.Storage's upload APIs and existing accounts will be upgraded to use w3up. Uploads via the w3up beta be migrated to web3.storage by default and, if applicable, combined with the relevant existing web3.storage account (based on email address). If you would rather have your beta w3up account be associated with the NFT.Storage product (e.g., you are only storing off-chain NFT data), please email us at support@nft.storage. All w3up uploads associated with a given registered email will only be able to be associated with one of either web3.storage or NFT.Storage when these uploads are migrated.

period.
</p>
<details style={{ maxWidth: '80vw', overflow: 'overlay' }}>
{' '}
<summary>More details</summary>
Expand Down