NoScript tends to break more things on the page than is desired, in my experience, I used to use it but eventually I got rid of it because of the hassle of “is this the one I should add an exception for to make it work? No. How about this one?” repeat until you figure it out,and then repeat the whole process for every website you ever use
Using AdNauseam’s built-in uBlock, I can use its element picker if something is particularly stubborn
Don’t get me wrong, I like NoScript as a concept and think it should exist for the subset of users who want that functionality, but it’s not for me.
and then repeat the whole process for every website you ever use
The thing is that you soon reach a point in which most of your frequently visited sites are already properly permissioned. After that, only newly visited domains need any special attention, and that’s assuming you’re there to do anything other than read some text or view an image.
![Goodbye [System32 Comics]](https://lemmy.world/pictrs/image/e8d929a6-dccd-43fe-80ab-8a85b0769b86.jpeg){kind=link}
anytime blocking elements is the correct choice noscript is better
NoScript tends to break more things on the page than is desired, in my experience, I used to use it but eventually I got rid of it because of the hassle of “is this the one I should add an exception for to make it work? No. How about this one?” repeat until you figure it out, and then repeat the whole process for every website you ever use
Using AdNauseam’s built-in uBlock, I can use its element picker if something is particularly stubborn
Don’t get me wrong, I like NoScript as a concept and think it should exist for the subset of users who want that functionality, but it’s not for me.
The thing is that you soon reach a point in which most of your frequently visited sites are already properly permissioned. After that, only newly visited domains need any special attention, and that’s assuming you’re there to do anything other than read some text or view an image.