For Static Sites, There’s No Excuse Not to Use a CDN

Re:For Static Sites, There’s No Excuse Not to Use a CDN by ireflect on Friday June 08, 2018 @11:23AM (#17266334)

CDNs make a lot of sense for improving load times and for the overall efficiency of network utilization, but I worry that the current ones (Cloudflare et al.) contribute too much to the recentralization of the Internet.

What we need is for gateway.ipfs.io to use geo-dns such that it can serve this purpose, and IPFS gateways can be run all over the world by regional ISPs, universities, and even individuals.

[ Parent | on HN ]

Re:For Static Sites, There’s No Excuse Not to Use a CDN by prophesi on Friday June 08, 2018 @11:34AM (#17266449)

Yeah, +1 to this. I'd use a CDN if it wasn't all owned by one company. I run a static site on IPFS, and just have two nodes located in NYC & San Francisco that my local gateway is always connected to.

It does a pretty good job for USA visitors (which is where the majority of my traffic comes from). But it'd be ideal for IPFS to use geo-dns, along with FileCoin implemented so that I can pay for nodes in other countries to have my content pinned.

Also, my site uses Service Workers to cache all of the content + TurboLinks, which drastically speeds up every subsequent page transition. I'm not sure if that's doable if you're using an external CDN like Cloudflare for all of your resources.

[ Parent | on HN ]

Re:For Static Sites, There’s No Excuse Not to Use a CDN by aspett on Friday June 08, 2018 @12:54PM (#17267328)

Do you have a blog on setting this up per chance? I'm interested in reading more about IPFS (haven't looked at it since I first heard about months and months ago). Their website seems a bit light on the details bar a link to a whitepaper I haven't dared to look at yet ;)

[ Parent | on HN ]

Re:For Static Sites, There’s No Excuse Not to Use a CDN by niutech on Friday June 08, 2018 @07:11PM (#17270480)

Here is one: https://medium.com/@merunasgrincalaitis/how-to-host-your-ipf...

[ Parent | on HN ]

Re:For Static Sites, There’s No Excuse Not to Use a CDN by StavrosK on Friday June 08, 2018 @11:46AM (#17266561)

Has the team done much since they raised $250 million? I've only seen one or two releases since, and the commit graph looks very slow. It's been a while since I checked, though, I might be out of the loop.

[ Parent | on HN ]

Re:For Static Sites, There’s No Excuse Not to Use a CDN by prophesi on Friday June 08, 2018 @11:51AM (#17266622)

There's been a lot of activity with the JS implementation of IPFS, but I'd agree that the core IPFS development has been lackluster lately.

[ Parent | on HN ]

Re:For Static Sites, There’s No Excuse Not to Use a CDN by gnode on Friday June 08, 2018 @12:45PM (#17267230)

A fundamental issue with CDNs is that you have to trust them. Even for public content, who accesses what is valuable private information. I can imagine IPFS making this worse, when anyone who wants to observe what is accessed by whom need only mirror it.

[ Parent | on HN ]

Re:For Static Sites, There’s No Excuse Not to Use a CDN by stephenr on Friday June 08, 2018 @01:16PM (#17267585)

If the SV/Startup set ever move past this ridiculous "outsource all the things" idea, now is as good a time as any to enable realistic self-owned CDN's using a lot of low-resource nodes across a variety of providers around the globe/your service area.

[ Parent | on HN ]

Re:For Static Sites, There’s No Excuse Not to Use a CDN by dwalkr on Friday June 08, 2018 @11:29AM (#17266391)

I definitely agree. The point I wanted to make here is that setting up replication for a static site is trivial due to their static/stateless nature (you can just use a CDN.) These same qualities make distributing a static site over IPFS easy to do too.

[ Parent | on HN ]

Re:For Static Sites, There’s No Excuse Not to Use a CDN by jgrahamc on Friday June 08, 2018 @12:18PM (#17266909)

Or have a CDN (e.g Cloudflare) support IPFS and get the best of both worlds.

[ Parent | on HN ]