feat: Use Blob protocol #118
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was mainly a sweep of uses of `h-screen`, as it was breaking on viewports shorter than the page contents, which was particularly nasty on the Pricing page, which is long. I've also: * Tweaked how the rooster shows up on small-width screens * Made the "Terms of Service" text on the login screen black rather than white for readability * Made the hamburger menu icon red rather than write for readability * Changed "w3up" to "Storacha" Unfortunately, we don't have Storybook and Chromatic (or similar) to see all the diffs, but I've screenshotted what I could. Note that these are all full-page screenshots; the fact that the befores are cut off at the top is exactly the problem I was solving here. 🙂 Plenty of this is subjective; thoughts, feedback, and corrections are more than welcome. ### Before      ### After     
alanshaw
requested changes
Sep 4, 2024
# Issue If the `NEXT_PUBLIC_W3UP_PROVIDER` environment variable is not set, the app will use `did:web:web3.storage` as the default storage provider. That works well if we are pointing to Prod environment (https://up.web3.storage), however, if we use the Staging environment (https://staging.up.web3.storage) it will fail to provision the space because the default provider is invalid for Staging. # Fix - Verify if the Space Provisioning result contains an error. If so, throw the error to prevent the user from continuing the flow and attempting to upload files. - Updated Docs and sample Env Vars. --------- Co-authored-by: Alan Shaw <[email protected]>
So we're all on the same version (and package manager).
Just a tiny copy change.
I've updated the workflow to use the `old-main` branch to deploy the `https://console.web3.network` app.
I've fixed the `deploy-storacha.yml` workflow to build previews and changelogs, run tests, and create releases using the same conditionals we had while deploying to `https://console.web3.storage`.
# Goals use up.storacha.network for service URL # Implementation update deploy scripts in github.
🤖 I have created a release *beep* *boop* --- ## [1.10.0](w3console-v1.9.1...w3console-v1.10.0) (2024-09-20) ### Features * change email ([7c7beb7](7c7beb7)) * **copy:** Add missing comma ([#115](#115)) ([97f1ac3](97f1ac3)) * Improved layout styling, and other tales ([#114](#114)) ([d0a2208](d0a2208)) * more styles ([d4e8efa](d4e8efa)) * styles for upload page ([6c54798](6c54798)) * trigger deploy ([a8f1089](a8f1089)) * wording ([ffe9b1b](ffe9b1b)) ### Bug Fixes * apostrophe ([681b9b8](681b9b8)) * check ref ([f406ac9](f406ac9)) * deploy-storacha.yml needs to use the new main branch ([#122](#122)) ([65644c8](65644c8)) * deploy.yml needs to use the old-main branch ([#120](#120)) ([713af05](713af05)) * quotes ([bcf209b](bcf209b)) * **space-creator:** check provision result before proceeding ([#119](#119)) ([5ea5940](5ea5940)) * use correct branch name ([f81e090](f81e090)) * use main branch ([698974b](698974b)) ### Other Changes * add storacha deploy action ([39345e6](39345e6)) * Set `packageManager` ([#117](#117)) ([c9436fc](c9436fc)) * update deploy name ([f7c1340](f7c1340)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
@Peeja I've released the |
### Add Share via Email Feature **Context**: This PR introduces the Share via Email feature, allowing users to share spaces using either an email address or DID. Depending on the input, we render different buttons and actions (e.g., sharing via email or generating a downloadable UCAN). Once shared via email, the “Shared With” panel lists all shared emails (did:mailto) along with their capabilities, fetched from the delegations stored in the client. **Short Demo**: https://www.loom.com/share/b33ee2f22a5b44628e5d9fc3d599dbf7?sid=0b008211-fc28-4cd4-a716-e67f44067661 **Minor Notes**: - The Share button dynamically changes based on whether the user provides an email or DID. - The delegation list is displayed with relevant capabilities in the “Shared With” panel.
Fix for issues - storacha/project-tracking#131 - #93 The issue happens when we try to delegate `*` to the DID of the audience. I've updated the code to delegate the same capabilities we use in the `client.shareSpace` method.
Fixes: #94 When you import an Space from the UCAN file it generates several components as Space Preview:  Ideally, it would render only one component for the Space that was imported:  This PR fixes that component and includes the information icon to show the capabilities delegated to that shared Space.
🤖 I have created a release *beep* *boop* --- ## [1.11.0](w3console-v1.10.0...w3console-v1.11.0) (2024-09-24) ### Features * share spaces via email ([#123](#123)) ([896079b](896079b)) ### Bug Fixes * import space preview ([#127](#127)) ([1f2acf6](1f2acf6)) * share space via ucan file ([#126](#126)) ([ba934a2](ba934a2)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
<img width="1356" alt="Screenshot 2024-09-25 at 18 34 57" src="https://github.com/user-attachments/assets/eaefb7b7-9231-4823-a2f2-b31d87d94457"> --------- Co-authored-by: Alan Shaw <[email protected]>
🤖 I have created a release *beep* *boop* --- ## [1.12.0](w3console-v1.11.0...w3console-v1.12.0) (2024-10-02) ### Features * add old web3 storage migrator ([#129](#129)) ([ba45a5f](ba45a5f)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Merged
Website preview 🔗✨ |
Peeja
added a commit
that referenced
this pull request
Oct 11, 2024
Reopens #118 against `main`, and should address @alanshaw's [feedback](#118 (review)) (making the Shard page work again).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Waiting for
@w3ui/[email protected]…As of PR draft, it depends on
@w3ui/[email protected], which doesn't exist yet. Once that's published, this should be re-pnpm installed to get a correct lockfile, and then amended.Closes storacha/project-tracking#123