Are you using (or plan to use) JS-IPFS in browser ? Your input would really help to shape the plan for changes that we hope will improve your and your users experience.
Right now every browser tab starts a new IPFS node & that has following shortcomings:
- Increased resource usage (CPU, Memory, Network Connections) is multiplied by number of tabs that negatively impact power usage (how much battery lasts).
- IPFS content from one tab is fetched over the internet by another tab (when they are no different origins).
Addressing those, however requires certain trade-offs like:
- Changing how JS-IPFS is bundled (as we need workers)
- Limiting configured options (sharing node implies sharing configuration)