4 ms·
Is there any concern that limiting JavaScript's functionality could cause unexpected behavior? E.g., your credit card is charged upon checkout but next part of
by elwell 5y ago
Is there any concern that limiting JavaScript's functionality could cause unexpected behavior? E.g., your credit card is charged upon checkout but next part of payment flow isn't triggered and your order isn't actually placed. Or, some DDOS protector thinks you are the same agent as everyone else using a similarly restricted config.
- eurasiantiger 5y agoBetter yet, having this extension installed is just another data point more and will count against your future social score because paranoia is not healthy.
- inpdx 5y agoWeird definition of paranoia.
- kdmytro 5y agoIt's only paranoia if you are not being watched. Watching you is the main business of many companies. Therefore, installing this extension is evidence of having basic understanding of modern advertising, rather than evidence of paranoia, in my opinion.
- woodruffw 5y ago> Is there any concern that limiting JavaScript's functionality could cause unexpected behavior? E.g., your credit card is charged upon checkout but next part of payment flow isn't triggered and your order isn't actually placed. I thing this was a common concern with the first few generations of content blockers, one that's mostly proved to be a non-issue. It's not my space, but if I had to take two guesses: 1. Most analytics code is sufficiently flaky and unreliable to keep it far away from the critical concrete value path of someone actually paying with a card. 2. Most developers are probably running content blockers.