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

Re-think WebUI as 'explorer' app that can connect to any IPFS node #40

Open
olizilla opened this issue Mar 16, 2018 · 1 comment
Open

Re-think WebUI as 'explorer' app that can connect to any IPFS node #40

olizilla opened this issue Mar 16, 2018 · 1 comment
Labels
dif/hard Having worked on the specific codebase is important effort/weeks Estimated to take multiple weeks kind/enhancement A net-new feature or improvement to an existing feature need/analysis Needs further analysis before proceeding P2 Medium: Good to have, but can wait until someone steps up status/deferred Conscious decision to pause or backlog topic/design-ux UX strategy, research, not solely visual design

Comments

@olizilla
Copy link
Member

There should be no friction for an app to connect to a locally running IPFS node. It's useful to be able to connect to an IPFS node running on another machine. Companion supports this now, as it used to require an external IPFS node to run, but cannot install one as it is packaged and distributed as a WebExtension.

We should consider not bundling WebUI with go-ipfs (See: #4) as it causes people to open up their api port to the public internet, which is a significant security issue. Rethinking WebUI as an IPFS dashboard / explorer / workbench app (like say a database explorer app) that can configured to connect to any IPFS node, local or remote, and have it display stats and a file browser #9 and IPLD explorer #11 would be really interesting.

The current state of things is described here: https://github.com/ipfs-shipyard/pm-ipfs-gui/blob/master/research/README.md#control-which-ipfs-node-you-connect-to
@hacdias
Copy link
Member

hacdias commented Mar 17, 2018

I strongly agree with this one. We could have one domain always pointing to the latest version of WebUI which wouldn't depend on the go-ipfs version/release.

@ericronne ericronne added design topic/design-visual Visual design ONLY, not part of a larger UX effort and removed design labels May 22, 2019
@jessicaschilling jessicaschilling added kind/enhancement A net-new feature or improvement to an existing feature and removed kind/improvement labels Apr 1, 2020
@jessicaschilling jessicaschilling changed the title Design: Control which IPFS node you connect to Re-think WebUI as 'explorer' app that can connect to any IPFS node Apr 7, 2020
@jessicaschilling jessicaschilling added dif/hard Having worked on the specific codebase is important effort/weeks Estimated to take multiple weeks need/analysis Needs further analysis before proceeding P2 Medium: Good to have, but can wait until someone steps up status/deferred Conscious decision to pause or backlog topic/design-ux UX strategy, research, not solely visual design and removed topic/design-visual Visual design ONLY, not part of a larger UX effort labels Apr 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dif/hard Having worked on the specific codebase is important effort/weeks Estimated to take multiple weeks kind/enhancement A net-new feature or improvement to an existing feature need/analysis Needs further analysis before proceeding P2 Medium: Good to have, but can wait until someone steps up status/deferred Conscious decision to pause or backlog topic/design-ux UX strategy, research, not solely visual design
Projects
No open projects
IPFS-GUI (PL EngRes)
Status: Needs Grooming
Milestone
No milestone
Development

No branches or pull requests
4 participants
@olizilla @jessicaschilling @hacdias @ericronne