Hi, I am writing a blog about decentralization and it can currently be accessed old skool via an nginx server, or through the ipfs gateway I run on that server.
IPNS optimization work is currently in progress. You could always give out the IPFS hash and add a “load latest” button somewhere that goes to the IPNS hash (which points to a HTML redirect page which in turn redirects to the IPFS hash).
You could use JavaScript to make this transparent to the end user.
@pors thanks for testing this stuff. The core maintainers of go-ipfs are really busy right now but will be coming up for air very soon and the info you’re gathering will be useful. We want to do lots of optimizations over the coming months. The issues you’re surfacing will help us target those efforts. First on the list is to make IPNS a lot faster – a couple people are already working on that one.
If you figure out ways to reliably reproduce the slow response times, I’d say go ahead and submit a bug report on https://github.com/ipfs/go-ipfs with instructions on how to recreate the issues. That will make it easier for the committers to keep track of it, and to let you know when it’s been addressed.
Just want to chime in and say we too are experiencing greatly varied load times when hosting on our own gateway (thought that would do the trick!) so any attention devs can pay attention to this issue are greatly appreciated. We really want to stay hosted on IPFS!!