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

Jump to bottom

Ability to copy gateway link to the wrapping directory #69

Open
lidel opened this issue Dec 17, 2018 · 1 comment
Open

Ability to copy gateway link to the wrapping directory #69

lidel opened this issue Dec 17, 2018 · 1 comment
Labels
effort/days Estimated to take multiple days, but less than a week exp/novice Someone with a little familiarity can pick up help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature P3 Low: Not priority right now status/ready Ready to be worked topic/design-front-end Front-end implementation of UX/UI work topic/design-ux UX strategy, research, not solely visual design

Comments

@lidel
Copy link
Member

lidel commented Dec 17, 2018 •
edited
Loading

tl;dr This is about feature parity with old screen in IPFS Companion

Before we switch ipfs-companion to this app (ipfs/ipfs-companion#642) we want to ensure users won't have any feelings of functional regression.

Old upload screen in IPFS Companion opened raw listing in a new tab and some users would prefer to have that ability. There should be a way to copy link to directory listing at the public gateway.

Basically this is a feature request to have:

  • "Sharing link" with share.ipfs.io (current one)
  • "Direct link" with ipfs.io/ipfs/.. (todo)
@lidel lidel mentioned this issue Dec 17, 2018
Closed
4 tasks
@jessicaschilling jessicaschilling added exp/novice Someone with a little familiarity can pick up effort/days Estimated to take multiple days, but less than a week 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 topic/design-front-end Front-end implementation of UX/UI work topic/design-ux UX strategy, research, not solely visual design labels Apr 7, 2020
@SgtPooki SgtPooki added P3 Low: Not priority right now and removed P1 High: Likely tackled by core team if no one steps up labels Nov 29, 2022
@SgtPooki
Copy link
Member

SgtPooki commented Oct 8, 2024

@lidel are we still interested in pointing users to the gateway from share.ipfs.io or should we close this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort/days Estimated to take multiple days, but less than a week exp/novice Someone with a little familiarity can pick up help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature P3 Low: Not priority right now status/ready Ready to be worked topic/design-front-end Front-end implementation of UX/UI work topic/design-ux UX strategy, research, not solely visual design
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lidel @SgtPooki @jessicaschilling