Re:A guide to IPFS connectivity in web browsers
by can16358p on Thursday February 24, 2022 @09:59AM
(#30455456)
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.
Re:A guide to IPFS connectivity in web browsers
by rglullis on Thursday February 24, 2022 @10:57AM
(#30456165)
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.
Re:A guide to IPFS connectivity in web browsers
by simonw on Thursday February 24, 2022 @11:29AM
(#30456635)
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/
Re:A guide to IPFS connectivity in web browsers
by rglullis on Thursday February 24, 2022 @11:42AM
(#30456834)
- Firefox at 216M MAU: https://data.firefox.com/dashboard/user-activity
- Brave at 54M MAU: https://basicattentiontoken.org/growth/
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