-
Notifications
You must be signed in to change notification settings - Fork 489
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.
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
feat: IPNS Publishing #1973
feat: IPNS Publishing #1973
Conversation
Needs to be eyeballed by a native speaker, but this wins the google search result count for now.
It was useful in puppeteer, but now we use playwright which solves waiting logic way better via text selectors
This is basic copy that encourages sharing gateway link + disclaimer about the need for keeping node online once a day.
Most of fake/guessed progress bars overshoot, as it is better UX to "finishe sooner than be stuck at 100%" This change makes expectation always bit bigger than the rolling average between last two times.
… into feat/1482-settings
One thing that has broken e2e tests time and time again for me is modifying the package-lock and/or package.json with a different version of node. Be sure you're using node=16.12.0 and npm=8.1.0 and then do: git checkout origin/main -- package-lock.json |
@hacdias , One thing that has broken e2e tests time and time again for me is modifying the package-lock and/or package.json with a different version of node. Be sure you're using node=16.12.0 and npm=8.1.0 and then do: git checkout origin/main -- package-lock.json |
I finished migration to @playwright/test in #1983, will merge into this PR shortly. 🤞 |
When someone opens IPNS publishing they now get a hint that more info and key management can be found in Settings
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed E2E tests, overall lgtm, thank you @hacdias for your patience here ❤️
My hope was to have ipns over pubsub enabled everywhere when we merge this,
but I think having it in Desktop is good enough, and things may improve further
when we have delegated IPNS publishing over Reframe.
Let's wait for 👍 from a native speaker / UX folks till the end of this week,
and then merge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alternative text suggestions:
Generate new IPNS Key
- Previous text: Enter pet name of key to create.
- New text: Enter a nickname for this key to generate:
- Description of change: nickname instead of pet name
Drop Down
- I prefer capitalizing the first letter of each word for dropdowns but not necessary
Publish
-
Previous text: Please wait while initial 20 copies of the updated IPNS record are being stored with the help of DHT peers.
-
New Text: Please wait while the initial 20 copies of the updated IPNS record are stored with the help of DHT peers.
-
Description of change: verb tense
-
Previous Text: Copy the link below and share it with your friends. IPNS address will resolve as long as your node remains available on the network to refresh IPNS record once a day.
-
New text: Copy the link below and share it with your friends. The IPNS address will resolve as long as your node remains available on the network once a day to refresh the IPNS record.
-
Description of change: Added “The” before “IPNS address” ; moved "once a day" to middle of the sentence
-
Question: is sharing with friends the most common use case? Consider replacing “your friends” with “others” or "your network"
Just some minor alterations to the text: "Enter pet name of key to create." -> "Enter a name for the new key." "Please wait while initial 20 copies of the updated IPNS record are being stored with the help of DHT peers..." -> "Please wait while an initial 20 copies of the updated IPNS record are being stored with the help of DHT peers..." "IPNS address will resolve as long your node remains available on the network to refresh IPNS record once a day." -> "The IPNS address will resolve as long as your node remains available on the network to refresh the IPNS record once a day." Thanks for this work, very excited to have this feature in the webUI ^-^. |
@lidel I updated the copy based on @juliaxbow's and @TheDiscordian's suggestions. |
Thank you! Merging so these new labels land in Side notes:
|
## [2.18.0](v2.17.3...v2.18.0) (2022-09-09) CID `bafybeidb5eryh72zajiokdggzo7yct2d6hhcflncji5im2y5w26uuygdsm` --- ### Features * IPNS Publishing ([#1973](#1973)) ([4ff4939](4ff4939)) * ux improvements to publish modal ([#1998](#1998)) ([ea4f632](ea4f632)) ### Bug Fixes * **ci:** parsing "ipfs-cluster-ctl peers ls" output ([#1966](#1966)) ([828e460](828e460)) * korean detection ([#2005](#2005)) ([362dab8](362dab8)) * Kubo agent text to link via ReleaseLink [#2010](#2010) ([#2011](#2011)) ([3d04988](3d04988)) * nodejs readme badges ([#1985](#1985)) ([a9e661b](a9e661b)) * remove web ui version and keep revision ([#2000](#2000)) ([42ed78d](42ed78d)) * resolve issues with automated releases ([#1974](#1974)) ([9a7cfad](9a7cfad)) ### Trivial Changes * add missing classnames dependency ([#1977](#1977)) ([c4216b8](c4216b8)) * **deps:** update react-scripts ([#1969](#1969)) ([136b260](136b260)) * pull transifex translations ([#1996](#1996)) ([0de4267](0de4267)) * Pull transifex translations ([#2003](#2003)) ([cc51b15](cc51b15)) * **readme:** NodeJS version support info ([#1986](#1986)) ([829450d](829450d)) * **readme:** update release steps ([#1963](#1963)) ([c5b4822](c5b4822)) * Update .github/workflows/stale.yml [skip ci] ([f15818d](f15818d)) * update storybook and stories ([#2007](#2007)) ([83ceac1](83ceac1)), closes [/github.com/storybookjs/storybook/blob/next/MIGRATION.md#webpack-5](https://github.com/ipfs//github.com/storybookjs/storybook/blob/next/MIGRATION.md/issues/webpack-5)
🎉 This PR is included in version 2.18.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Please see PR #1857 for what happened and background on this. Closes #1482.
Generate New Key
Publishing Keys Settings Menu
Drop Down
Publish