Improving IPFS

[liamzebedee]

• Simpler tooling for deploying .eth dapps.
• Feedback on upload/download for content.
  • Users can see what % a torrent is, but there’s no equivalent for IPFS.
  • num leechers/seeders
• Add observability for content dissemination on Cloudflare etc - right now it’s impossible to know.
• IPNS sucks - it’s worse than DNSLink for production dapps. Automatic republishing is not built-in, IPNS records are centralized (wtf) unlike the IPFS DHT.
• IPFS node is opaque - I’ve run my node for 1 day and it’s used 10GB of download. What’s it doing? I cannot tell.
• Understanding/configuration of maximum size limits for content on the user-side.

Potential features:

• Private IPFS networks that are gated by token-access would be very useful. e.g. imagine a network of websites that permit access based on some condition.
• Very useful would be an in-browser ipfs API, similar to Metamask, that allows dapps to use "P2P storage" (as opposed to cloud storage).

[liamzebedee]

Some improvements made from switching to lowpower profile.

Some relevant info on how IPFS isn't going to scale as a protocol here - https://news.ycombinator.com/item?id=32738093