Cameron Yick

(Leaving this in draft because I need to figure out how to safely untangle this git conflict before attempting to propose another fix)

Based on https://github.com/vega/vega-lite/issues/8370, we may want to try manually bumping the package.json in `next` as to bring the published version string back up to date (it's currently 0.3 versions behind)

If we're willing to let the client fetch external resources for themselves on the first load, we can use the service-worker cache. I implemented one in my fork: https://github.com/hydrosquall/datasette-lite/pull/6

Specifically, these are the only functionalities currently supported, based on the [TNW article](http://thenextweb.com/dd/2015/02/12/linkedin-takes-aim-developers-plans-lock-apis/): From May 12, LinkedIn will limit its open APIs to just four uses: - allowing members to...

Running into same issue - wonder if it's related to Linkedin's gradual deprecation of their v1 API

I think the API integration is dead. https://techcrunch.com/2015/02/12/linkedin-battens-down-the-hatches-on-api-use-limiting-full-access-to-partners/

Since you're not using localhost, maybe leave the port number off? e.g. `https://linkedinpy-terenceliu.c9users.io` With that said, I think the library might be dead. Additionally, given the error message, are you...

So the python library does work, but for 4 basic functions. You can see that I provided in #103 the list of methods that are supported / not supported given...

I think this issue can be closed since https://github.com/intuit/auto/pull/2205 shipped - were you able to try out the new version @mrtnbroder ?

I misspoke - it turns out you can't use fetch with `loader.http` directly, you have to wrap it in a function that returns a string. Something to this effect works...