Brave has IPFS support build-in and with every other browser you can still access it by using a public gateway, without installing anything. Even if you want th

Brave has IPFS support build-in and with every other browser you can still access it by using a public gateway, without installing anything. Even if you want the "full experience", it's quite easy as the go-ipfs daemon comes a single precompiled binary without any weird dependencies or a need to configure anything. Also IPFS has a FUSE daemon included (--mount option), so it shows up as /ipfs and /ipns on Linux. The bigger issue is that there is no way to browse IPFS. So even when you have IPFS up and running, there isn't anything obvious to do with it. ipfs-search.com is about as good as it gets, but that's mostly broken links and due to the lack of a way to navigate to the parent directory, you are often left with individual files as search result, not actual webpages. Also the FUSE daemon is barely usable. Due to the way IPFS works at the moment, it can't show you a directory until it has downloaded the blocks for all the files in that directory, as that's the only way to get the file type. This makes it painfully slow to use and basically impossible for larger directories, e.g. having a Linux distribution mirrored on IPFS could be cool, but was completely unusable last time I tried. There is a lot of potential in IPFS, but to really shine it needs a lot more work put into it. Once it can mirror Github and I can `cd /ipfs/...` into a git repository, it could be really useful (IPLD should allow that eventually), but so far it barely works well enough to replace an FTP server. Another elephant in the room is copyright. IPFS only cares about hashes, it doesn't track who owns or uploaded the content. It's like running a torrent for every bit of Internet you browse. I can't see that working out in the long run in today's legal landscape.