3 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

> 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/