Comment on How We Made IPFS Content Publishing 10x FasterparentComments−boramalper2moI think the biggest sin of IPFS is not working natively in web browsers—instead, requiring the use of either HTTP gateways or native apps running outside the browser.−dannyobrien2moActually, this works now! https://inbrowser.link/ https://github.com/ipfs/service-worker-gateway -- getting p2p working in browsers is still surprisingly hard: even the official routes like webrtc have lots of hard edge cases.−Borg32moComment there made me chuckle..: serving only small static HTML+JS files (<10MiB)sigh So entire IPFS + IPFS Gateway needs to be so huge? 10MB? My dot.exe (DVFS repo manager) is 150kB..
Comments
I think the biggest sin of IPFS is not working natively in web browsers—instead, requiring the use of either HTTP gateways or native apps running outside the browser.
Actually, this works now! https://inbrowser.link/ https://github.com/ipfs/service-worker-gateway -- getting p2p working in browsers is still surprisingly hard: even the official routes like webrtc have lots of hard edge cases.
Comment there made me chuckle..: serving only small static HTML+JS files (<10MiB)
sigh So entire IPFS + IPFS Gateway needs to be so huge? 10MB? My dot.exe (DVFS repo manager) is 150kB..