News for hackers. Stuff that matters.
Re:Introducing Cloudflare’s IPFS Gateway by dgreensp on Monday September 17, 2018 @02:20PM (#18008491)
Is IPFS really a store, let alone a store with any particular performance or availability properties? If I want to be sure a file is available, don’t I have to host it or pay someone to host it? And if I want to make sure it is geo distributed, I have to geo distribute it or pay a service to? What is the big change?
Re:Introducing Cloudflare’s IPFS Gateway by wongarsu on Monday September 17, 2018 @02:27PM (#18008562)
Wit IPFS you could rent a few cheap storage servers at different providers around the world and have them all pin your content. That should be resilient against most classes of failures (unlike a cloud provider where bad code pushed to production by the cloud hoster can cause failures in all availability regions).

It's not exactly the first protocol enabling that, but IPFS also has the benefit of distributing bandwidth if your clients all access the files via IPFS (since they will serve them from their cache).

Re:Introducing Cloudflare’s IPFS Gateway by dgreensp on Tuesday September 18, 2018 @04:25PM (#18018804)
I see, so geo distribution could be as simple as making the file available in multiple locations, with IPFS doing the rest.
Re:Introducing Cloudflare’s IPFS Gateway by progval on Monday September 17, 2018 @02:32PM (#18008617)
IPFS is not a store, it's a protocol. You still have to pay someone to host it.