4 ms·

This is nice but for more mass adoption we'll need something seamless that will just be included as a script in a web page and "just work" by connecting to a pr

This is nice but for more mass adoption we'll need something seamless that will just be included as a script in a web page and "just work" by connecting to a provider while still customizable for people who want to use their own node. It can even "polyfill" any IPFS paths automatically (which should just be simply as replacing any ipfs:// URIs with ipfs.io gateway paths). For anyone trying to host pinned files behind a NAT/CGNAT would it be possible to hole punch to serve paths directly? If possible everything can me set up to work just out of the box with minimal/no setup in browser which should be the aim. In other words, we need something of an IPFS version of what MetaMask/ethers.js did to Ethereum based blockchains.

dangerface 5y ago
The current state of the browser its just not possible to do p2p properly, WebRTC is the best bet and you need to trust stun servers to punch NAT you need to trust a signal server to connect to other peers its not real p2p so why not just trust a gateway and use that. Brave browser has ipfs support built in and I think there are plugins for chrome and firefox without the code localy to do p2p properly it doesn't really make much sense faking it with WebRTC when the end result is the same as using a gateway directly.
- can16358p 5y ago
  Trying local node, verifying it works, otherwise falling back to an external node might be the best way to go. But still we need Firefox/Chrome/Safari adoption.
artdigital 5y ago
> This is nice but for more mass adoption we'll need something seamless that will just be included as a script in a web page and "just work" by connecting to a provider while still customizable for people who want to use their own node. It can even "polyfill" any IPFS paths automatically (which should just be simply as replacing any ipfs:// URIs with ipfs.io gateway paths). That’s what Brave does built in, and other browsers with the ipfs companion extension When you hit a ipfs URL it’s resolving it either through a gateway or through your own node
- can16358p 5y ago
  That's great but the problem is still Brave's market adoption. We'd really need some support from Firefox/Chrome/Safari trio to really start adoption. Most likely Firefox, then (albeit unlikely) Chrome and Safari. Brave's adoption is just too low, even though I (and probably a significant people here ar HN) personally think it's doing the best.
  - rglullis 5y ago
    Look at the trends. Brave has barely 3 years since it became usable enough to be a daily driver, and it has already 20-25% of Firefox market share. Firefox is constantly shrinking its user base, Brave is growing 40% YoY.
    - simonw 5y ago
      Where are you finding those numbers? Most global browser share numbers I could find bundled Brave into the "Other" category - this was the only one I found that broke it out separately: https://kinsta.com/browser-market-share/ https://kinsta.com/browser-market-share/
      - rglullis 5y ago
        - Firefox at 216M MAU: https://data.firefox.com/dashboard/user-activity https://data.firefox.com/dashboard/user-activity - Brave at 54M MAU: https://basicattentiontoken.org/growth/ https://basicattentiontoken.org/growth/
contrahax 5y ago
Currently working on Android + iOS apps that handle the ipfs:// protocol natively and allow users to upload files as well. I think you're right on target RE: more protocol adoption and hopefully something as simple as making the links work natively and letting people upload with a simple interface will help out. The IPFS extension exists for Chrome/Firefox/Opera for similar functionality. Out of my hands but getting more browsers than Brave to add support seems like the next place to start pushing IMO.

dangerface 5y ago

The current state of the browser its just not possible to do p2p properly, WebRTC is the best bet and you need to trust stun servers to punch NAT you need to trust a signal server to connect to other peers its not real p2p so why not just trust a gateway and use that. Brave browser has ipfs support built in and I think there are plugins for chrome and firefox without the code localy to do p2p properly it doesn't really make much sense faking it with WebRTC when the end result is the same as using a gateway directly.

can16358p 5y ago
Trying local node, verifying it works, otherwise falling back to an external node might be the best way to go. But still we need Firefox/Chrome/Safari adoption.

artdigital 5y ago

> This is nice but for more mass adoption we'll need something seamless that will just be included as a script in a web page and "just work" by connecting to a provider while still customizable for people who want to use their own node. It can even "polyfill" any IPFS paths automatically (which should just be simply as replacing any ipfs:// URIs with ipfs.io gateway paths). That’s what Brave does built in, and other browsers with the ipfs companion extension When you hit a ipfs URL it’s resolving it either through a gateway or through your own node

can16358p 5y ago
That's great but the problem is still Brave's market adoption. We'd really need some support from Firefox/Chrome/Safari trio to really start adoption. Most likely Firefox, then (albeit unlikely) Chrome and Safari. Brave's adoption is just too low, even though I (and probably a significant people here ar HN) personally think it's doing the best.
- rglullis 5y ago
  Look at the trends. Brave has barely 3 years since it became usable enough to be a daily driver, and it has already 20-25% of Firefox market share. Firefox is constantly shrinking its user base, Brave is growing 40% YoY.
  - simonw 5y ago
    Where are you finding those numbers? Most global browser share numbers I could find bundled Brave into the "Other" category - this was the only one I found that broke it out separately: https://kinsta.com/browser-market-share/ https://kinsta.com/browser-market-share/
    - rglullis 5y ago
      - Firefox at 216M MAU: https://data.firefox.com/dashboard/user-activity https://data.firefox.com/dashboard/user-activity - Brave at 54M MAU: https://basicattentiontoken.org/growth/ https://basicattentiontoken.org/growth/

contrahax 5y ago

Currently working on Android + iOS apps that handle the ipfs:// protocol natively and allow users to upload files as well. I think you're right on target RE: more protocol adoption and hopefully something as simple as making the links work natively and letting people upload with a simple interface will help out. The IPFS extension exists for Chrome/Firefox/Opera for similar functionality. Out of my hands but getting more browsers than Brave to add support seems like the next place to start pushing IMO.