Webui Features

[mappum]

This issue is for planning and tracking Webui development. Feature suggestions and feedback belongs here.

Initial feature planning

Raw brainstorm output

Main sections

• Connections
  • List of active peer connections
  • Show bandwidth usage
  • Expand entries to show more info about peers
    • Public keys
    • Addresses + geolocation
    • Protocol + agent version
    • Link to bitswap ledger, wantlist
  • Google Earth visualization of connections, traffic
• Bitswap
  • Show our wantlist
  • Show peers' wantlists/ledgers
  • Strategy info
  • go-ipfs: Requires some additional commands (ipfs bitswap [ wantlist | ledger | strategy ])
• DHT
  • Show routing table
  • Hashspace visualization (can show location of PeerIDs+object hashes in a ring)
  • go-ipfs: requires a ipfs dht table command, and realtime events for the visualization
• Files (UnixFS)
  • Show all local files/directories
    • go-ipfs: requires a command to list all locally stored files/dirs
  • Resolve hashes for downloading/viewing
  • Show pinned files/directories
• Objects
  • Show object links
  • Show object data
  • Link to data as UnixFS file/directory
• Names
  • Show/edit IPNS entries
  • go-ipfs: Requires a command to list all of our names
• Config
  • View/edit config values
• Logs
  • Show daemon logs
  • go-ipfs: requires a command to download (and maybe stream) logs

Other details

• Show when new updates are available, button to download/install them
• Browser mode that keeps a frame with a IPFS address bar (navigates to /ipfs/hash/foo/bar paths)
  • Shows smart info about resolving/errors (e.g. /ipfs/hash/foo might be valid, but not /ipfs/hash/foo/bar)
• Make tables sortable and filterable

[jbenet]

sweet! also list:

• modifications needed in go-ipfs
• expected time

[mappum]

I listed the go-ipfs modifications, but I'm not too sure on time estimates yet. I'll have a few data points for estimation after doing the first few tasks.

[btc]

For the UnixFS feature, you may want to have a look at the http.FileSystem and http.File interfaces.

I mention this because conforming to these interfaces would make it possible to offer IPFS as a drop-in static file server.

http.ListenAndServe(":8080", http.FileServer(ipfs.Node()))

[whyrusleeping]

CAUTION, OFF TOPIC

speaking of http serving files, i read this earlier, pretty damn awesome: http://avtok.com/2014/11/05/interface-upgrades.html

[jbenet]

Please see #576