News for hackers. Stuff that matters.
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.

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 ;)
Re:For Static Sites, There’s No Excuse Not to Use a CDN by niutech on Friday June 08, 2018 @07:11PM (#17270480)
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.
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.