51–60 of 156 posts
If you replace the word "IPFS" with "BitTorrent," this article is still true. Similarly, if you replace "IPFS" with "BitTorrent" in most of the comments here, the comments are still true. If you understand how BitTorrent works -- including its strengths and limitations -- you'll understand how IPFS works.
Minor nit: BitTorrent does not allow one to maintain a persistent URI to changing/updated data, as IPNS does.
If you replace the word "IPFS" with "BitTorrent," this article is still true. Similarly, if you replace "IPFS" with "BitTorrent" in most of the comments here, the comments are still true. If you understand how BitTorrent works -- including its strengths and limitations -- you'll understand how IPFS works.
Minor nit: BitTorrent does not allow one to maintain a persistent URI to changing/updated data, as IPNS does.
We run a blog on top of IPFS, and we use ENS (Ethereum Name Service) to keep it always updates. Basically you can access it if you use Opera browser or some browser extension. If not there are some gateways, like this: blog.almonit.eth.link
like Zeronet with Namecoin, only less original
If you care about people consuming your content, you won't use IPFS.
Earlier quoted context omitted.
To add to this there are* serious issues with naming. I wrote an app that ran on IPFS last year and throughout testing there was a persistent problem with needing to issue the testers with a new hash/link for each new version because IPNS, IPFS' decentralized naming solution, effectively doesn't work. It's supposed to give each node a unique name which can be repeatedly mapped to different hashes but publishing a new…
I consider IPNS fundamentally broken and have stopped using it. ENS is better in almost every way and is extremely reliable so it's not that big of deal.
Earlier quoted context omitted.
To add to this there are* serious issues with naming. I wrote an app that ran on IPFS last year and throughout testing there was a persistent problem with needing to issue the testers with a new hash/link for each new version because IPNS, IPFS' decentralized naming solution, effectively doesn't work. It's supposed to give each node a unique name which can be repeatedly mapped to different hashes but publishing a new…
I consider IPNS fundamentally broken and have stopped using it. ENS is better in almost every way and is extremely reliable so it's not that big of deal.
Earlier quoted context omitted.
Well, one can use IPFS through Tor, and use gateways that are Tor onion services.
We do this for OpenBazaar which is built on top of ipfs and it works great. We built a Tor transport for libp2p, which is what drives ipfs's p2p networking so any libp2p app, including ipfs, can work over Tor. https://github.com/OpenBazaar/go-onion-transport
It was y'all that actually got IPFS working via Tor.
Out of curiosity, isn’t the DNS gateway like Cloudflare ( https://blog.cloudflare.com/distributed-web-gateway/ ) a single point of failure? Is there a solution to this without having to resort to a completely different desktop app?
Last I checked a lot of the consensus were that the Dat project was more mature than IPFS and that it had some advantages over IPFS (such as not using as much resources to run). How is it now? Is it more mature? Even though I actually even sub to their newsletter I haven't really been keeping up to date if they have made any major releases. Not to be a downer on IPFS at all, btw. I'm very glad that both it and Dat ex…
Has Cloudflare made any commitments regarding the longterm availability of their IPFS gateway?