Hacker News new | ask | show | jobs
by adlha 1840 days ago
Hey everyone, our team just built a tool to make your Github notebooks interactive and we would love for you to try it out. Just enter the GitHub URL of your (or any) public notebook and hit Render to instantly view the notebook. Your notebook will be rendered in an article-like layout and will get a table of contents. Anyone can fork it using the "Launch" button and play around with your code. The Deepnote viewer is also faster and more reliable than other .ipynb viewers we've tried. Would love for you to take it for a spin & hear your feedback!
3 comments

What's your security model for logged-in users, one of the reason we (the jupyter team) have nbviewer on a separate domain with no login is to have embedded JS and other potentially sensitive content to be rendered without risk. We've seen people trying many attack vectors against renderer like this one with for example injecting script tags in things like prompt numbers.
Thanks for the q (I work at Deepnote) - all outputs that can contain potentially malicious JS are sandboxed in iframes so they can only access their local context and can't be used e.g. for XSS attacks.
I am a huge fan of Deepnote!

Have you considered / is there already a way to “import” an .ipynb into a DeepNote project?

Would be easier for users than to copy and paste code one cell at a time.

Absolutely! All you have to do is Upload your .ipynb files (or full folders) into an empty Deepnote project and run the code. I'm sending docs with more info on how to import files here: https://docs.deepnote.com/importing-and-exporing/importing-d...
That seems great, but for the comparison between DN viewer and the other, is there any benchmark tests specifically or it just a general feeling of speed when someone is using them. Because for each Jupyter notebook viewer it will depend on the setup, machine and the load itself.
Hi there! Simon (Engineer at Deepnote) here. We didn't benchmark the load speed but for some reason, Github's ipynb viewer has always felt to me quite slow and unreliable.

All viewers are publicly accessible so I'd love it someone did an independent benchmark. I'd prefer to avoid doing one ourselves because of the obvious conflict of interest

I thought that it is more than this. I think you should support any claim about that by creating a reproducible open benchmark test so at least people can understand what criteria you selected.
I also find it myself much faster than GitHub viewer.
Why not make a benchmark which is also open and reproducible?