The embeds we create will be requested from us each time. This is desirable: users can update their Observable notebooks to update their Jupyter embeds, even without rerunning the Jupyter notebook. (If users are worried about the cells breaking because of later modifications to the Observable notebook, they can request a specific version of the embed.)
Unless it isn't. We could allow users to download everything we'd need for an embed (data URIs etc.) into the Jupyter notebook. Their notebook code would still be fetched on every execution of the Python embed function, but the code would be not fetched for every viewer of the document. Jupyter notebooks are sometimes viewed by viewers without execution privledges; sometimes they are transformed into static documents by nbconvert and those static documents hosted somewhere else. If it were important that embedded Observable cells not make requests to api.observablehq.com on every load, we could make that happen.
I don't think this would be useful. Maybe it would hit some sweet spot for corporate users in some situations.
The embeds we create will be requested from us each time. This is desirable: users can update their Observable notebooks to update their Jupyter embeds, even without rerunning the Jupyter notebook. (If users are worried about the cells breaking because of later modifications to the Observable notebook, they can request a specific version of the embed.)
Unless it isn't. We could allow users to download everything we'd need for an embed (data URIs etc.) into the Jupyter notebook. Their notebook code would still be fetched on every execution of the Python embed function, but the code would be not fetched for every viewer of the document. Jupyter notebooks are sometimes viewed by viewers without execution privledges; sometimes they are transformed into static documents by nbconvert and those static documents hosted somewhere else. If it were important that embedded Observable cells not make requests to api.observablehq.com on every load, we could make that happen.
I don't think this would be useful. Maybe it would hit some sweet spot for corporate users in some situations.