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.

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

Save all uploads to MFS (via ipfs.files API) #415

Closed
lidel opened this issue Mar 8, 2018 · 0 comments · Fixed by #810
Closed

Save all uploads to MFS (via ipfs.files API) #415

lidel opened this issue Mar 8, 2018 · 0 comments · Fixed by #810
Labels
exp/intermediate Prior experience is likely helpful help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked

Comments

@lidel
Copy link
Member

lidel commented Mar 8, 2018

Part of UX improvements for sharing local files (#342)

Current behaviour

Right now upload via right-click context menu or browser action menu item adds raw data to IPFS and it is up to user to memorize or save CID.

Feature Description

Would be great to let user manage shared files via WebUI's Files screen.

Given discussion in ipfs/ipfs-gui#10 (comment):

  • when file is uploaded via browser extension it should be automatically added to MFS, so that user can later go back to it or decide to "unpin" it by removing it from MFS.
    • Maybe something like /ipfs-companion-uploads/YYYY-MM-YY_HHMMSS?
    • OR, show a checkbox below (checked by default) saying "Add to My Files at /some/path/" where the default path from Preferences can be chaged inline with super fast autocomplete

References

@lidel lidel added kind/enhancement A net-new feature or improvement to an existing feature help wanted Seeking public contribution on this issue UX exp/intermediate Prior experience is likely helpful P1 High: Likely tackled by core team if no one steps up labels Mar 8, 2018
@lidel lidel added this to the 2018-Q1 milestone Mar 8, 2018
@lidel lidel modified the milestones: 2018-Q1, v2.3.0 Apr 11, 2018
@lidel lidel added the status/ready Ready to be worked label Jun 25, 2018
@lidel lidel modified the milestones: v2.4.0, 2018-Q3 Jul 7, 2018
@lidel lidel modified the milestones: 2018-Q3, 2018-Q4 Sep 20, 2018
@lidel lidel removed this from the 2018-Q4 milestone Oct 8, 2019
@lidel lidel closed this as completed in #810 Dec 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
exp/intermediate Prior experience is likely helpful help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant