-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Allow users to use p2p-keys to publish content #15422
Comments
@karenkliu Are you ok with this location in the menu? Possibly move options to More Tools section. More Tools >Share local file using IPFS >
|
Export does not require repo lock and it is safe to do even when ipfs daemon is running. This enables apps like Brave browser to do import/export without stopping/starting daemon. Ref. brave/brave-browser#15422
@rebron Have it as a top-line item in the menu makes it easier to find, so I think this is fine. However it doesn't make sense that it gets its own section. I would think of it as an additional browser feature and put it underneath Sync without a divider line. |
Verified
Partially verified (majority of publishing files/folders) via #16020 (comment), which covers the following:
Publishing new content over old one for same key should be successfulSteps:
If the IPFS node is stopped or keys are not available, the to-be-published items should not be addedSteps:
|
Description
Add a new block to the IPFS Settings to manage p2p-keys:
the self item would be the default key shown as disabled which you can’t remove
In the context menus add a submenu to select existing key or a new one, if new one selected the user will be navigated to the settings page keys management block
if no keys selected the content will be published to IPFS only, otherwise to IPNS
The text was updated successfully, but these errors were encountered: