New name!

[daviddias]

Following the lead of ipfs/ipfs-desktop#561, we also want to find a better name for the IPFS WebUI.

Please submit your proposals by creating a separate comment per proposal and give votes with 👍 👎 on that comment.

[daviddias]

IPFS Control Room

[daviddias]

IPFS Admin Panel

[daviddias]

IPFS Admin Console

[daviddias]

IPFS Dashboard

IPFS Admin (makes even more sense if we also name :5001 the "admin port", which would be a good thing)

IPFS Control (makes even more sense if we also name :5001 the "control port", which would be a good thing)

Voted 👎 on IPFS Dashboard because it sounds a bit too harmless to me. This is a webapp that gives you full privileges over the ipfs node, and not just by means of its functionality, but simply by being on the same port as the API (:5001). In other server-ish projects a dashboard is often something that's okay to put on the internet. (With some projects, you're even encouraged to.)

It would be good to pick a name that conveys some degree of delicacy.

(I'd also like to propose to make the majority vote here non-binding. I wouldn't care if it were only a matter of finding a name that's nice, but it's also a matter of preventing security missteps by users before they even arise.)

[bentoncbainbridge]

IPFS Space Center

[victorb]

ipfs-webui

[daviddias]

I hear your points @lgierth, I believe that something that might be causing the confusion is that we have nice things for users to interact with (DAG explorer, files, connections) mixed with Admin features (config). I'm starting to feel that we should have a Dashboard & an Admin Panel

[Admin-DataRoads]

Voted 👍 on IPFS Control because it's concise and conveys similar gravitas to admin level config. I also agree with @diasdavid though, that the separation between read-only access features and configuration-write features are a very important distinction -- important enough to separate the tools capable of doing each. Maybe IPFS Control (admin config-write feature superset) and IPFS Node Explorer (read-only local-node config subset)?

In any case, if an IPFS HTTPS-WebDAV gateway is ever completed, then I may consider that closer to a general IPFS WebUI than this project per se. That gateway interface also has the advantage of existing POSIX translation and remote file system support in every OS, which could be considered non-browser forms of WebUI.