search

fonsp / Pluto.jl

🎈 Simple reactive notebooks for Julia
https://plutojl.org/
MIT License
4.91k stars 284 forks source link

Privacy Badger extension can break pluto #645

Open ericlesaquiles opened 3 years ago

ericlesaquiles commented 3 years ago

I'm using Julia v1.5.2 and running things on Pluto have been going just fine until earlier today I updated it to version 0.12.7, and since then it's been unable to open a notebook (old, new, from web, from samples..), besides using a a-bit-too-great amount of cpu and memory at times. Pluto does run, it just doesn't open notebooks - but keeps loading forever. I wonder whether it's just me though

fonsp commented 3 years ago

Can you try an incognito window?

ericlesaquiles commented 3 years ago

oh then it worked :o thanks

fonsp commented 3 years ago

In that case the problem is with one of your browser extensions. 😢

Try whitelisting Pluto's address, and report the error to the extension developers

ericlesaquiles commented 3 years ago

Actually, the issue disappeared after I opened on incognito. I'm not sure what happened.. maybe that triggered a whitelisting. Anyway, I don't use many extensions, and none seem to be having problems with Pluto as of now

fonsp commented 3 years ago

Do you have any adblocking/cookie/privacy/vpn extensions?

ericlesaquiles commented 3 years ago

Only Privacy Badger and Facebook Container. Also, maybe I should've said I'm on firefox.

ndgnuh commented 3 years ago

For me, it was the User Agent Switcher. Excluding localhost from it should help.

fonsp commented 3 years ago

Okay, Privacy Badger is known to block Pluto's source code provider (jsdelivr CDN) after a while. It would be really helpful if you could report this error to privacy badger:

image

This lets the EFF developers know about the situation, and might help them update their algorithm.

fonsp commented 3 years ago

@novoselrok Can we detect that the scripts did not load and show a helpful warning? Just like we do for old browsers. Feel free to add this to our list! Alternatively we could solve #241 to avoid this issue entirely.

ericlesaquiles commented 3 years ago

That's a strange thing for the badger to do... it started after the update, and stopped after a seemingly uninteresting action. Well I suppose it happens, I'll be report the error.

fonsp commented 3 years ago

Ooh maybe the problem started because we load firestore from jsdelivr instead of the google CDN