Contestant on Googlyify.
hello im doge. wow nod.js
Yes, the diffing part of it is probably only useful in certain use-cases. Rare updates have the benefit of being able to just cache heavily and then version bump assets on a deploy. In that case, this library would be helpful instead to give you the automatic inlining of assets on a mobile-served page.
The proxy thing is finicky right now and is intended to be more of a conversation piece than anything. If you have 3rd party cookies blocked you're going to have problems, I think. Also make sure you try it at http://dinosrc.it/proxy-demo without the
www - think that might make a difference, but I can't remember why right now :p - we might have not set it up entirely right, that push happened pretty close to the deadline!
Never mind, I'm full of it - the domain shouldn't matter. I bet it's the 3rd party cookies setting on your browser. Browsers treat
localStorage in that same category of 3rd-party persisted data, so you won't be able to automatically write to the proxy'd domain's storage in most circumstances w/ that protection turned on. Theoretically there are times when it won't be blocked, such as if you've visited the proxy'd domain before in the same browsing session (I think that's how Safari and latest FF do it) - but in my experience it's hard to rely on.
Sorry for stopping the fun so early! Getting the gameplay working took too much time from building it further. Thank for the feedback! :)