@EdwardTorvalds@mstdn.io
I guess then I don't understand how ipfs works... How does one make an ipfs-site (and doesn't it suffer from similar name problems as LBRY?). Also, won't this have performance problems for unpopular ipfs-sites? (Still requiring a dedicated server, but one with more resources to run the complex p2p software)
@kravietz
@everlastingrocks @EdwardTorvalds
BTW one of the largest practical deployments of IPFS today is LibGen!
@everlastingrocks @EdwardTorvalds
IPFS is a filesystem, so any website hosted on it is a static website - meaning static HTML+JavaScript rendered in the browsers and all data needs to be self-contained in the IPFS.
In terms of performance, it's self-scaling - the more users view a website, the more nodes cache it. Initial propagation may be slow, so if you want your website to always load fast for everyone, you just host more seeding nodes.