Introducing Cloudflare’s IPFS Gateway

Re:Introducing Cloudflare’s IPFS Gateway by magnetic on Monday September 17, 2018 @04:18PM (#18009643)

Is there a way (even not free) to ensure that my data in IPFS is always available (at least as available as with "traditional hosting services)?

That's a bit of a requirement when building a serious service/website.

[ Parent | on HN ]

Re:Introducing Cloudflare’s IPFS Gateway by wiml on Tuesday September 18, 2018 @12:44AM (#18012526)

As I understand it, the way is: run an IPFS node (perhaps on a cheap VPS); use `ipfs pin ` to force the node to retain the file even if it isn't being requested.

Presumably someone could sell "pinning as a service" for fairly cheap: a popular file will be widely cached, so the service will rarely need to provide it; and an unpopular file will be rarely requested.

[ Parent | on HN ]

Re:Introducing Cloudflare’s IPFS Gateway by magnetic on Saturday September 22, 2018 @01:20PM (#18046868)

Isn't pinning as a service essentially a CDN?

Is there a reason to believe that such service would be cheaper than a "traditional" CDN?

[ Parent | on HN ]

Re:Introducing Cloudflare’s IPFS Gateway by qbaqbaqba on Tuesday September 18, 2018 @08:42AM (#18014748)

https://www.eternum.io

[ Parent | on HN ]

Re:Introducing Cloudflare’s IPFS Gateway by 0x8BADF00D on Monday September 17, 2018 @08:10PM (#18011253)

CAP theorem.

[ Parent | on HN ]

Re:Introducing Cloudflare’s IPFS Gateway by ric2b on Friday September 21, 2018 @07:14PM (#18043375)

What we're talking about only requires the A and the P.

[ Parent | on HN ]

Re:Introducing Cloudflare’s IPFS Gateway by magnetic on Monday September 17, 2018 @10:10PM (#18011860)

Perhaps you can elaborate?

[ Parent | on HN ]