4 ms·
That still doesn't solve a problem of a user installing the browser for the first time, installing adblock, then going to a porn site in private mode and gettin
by Grue3 7y ago
That still doesn't solve a problem of a user installing the browser for the first time, installing adblock, then going to a porn site in private mode and getting a faceful of malware-ridden ads. Who thought this is a good idea?
- DCoder 7y agoIf you flip the setting, that doesn't solve a problem of a user installing the browser for the first time, installing an extension like Stylish †, going to a porn site in private mode and getting their private browsing history leaked to the extension operator together with their regular history. Who thought that is a good idea? :) † Stylish is a … special case [0]. But see also hypothes.is or any other extension that relies on a "user-created content store". [0] https://robertheaton.com/2018/07/02/stylish-browser-extension-steals-your-internet-history/ https://robertheaton.com/2018/07/02/stylish-browser-extensio...
- Scarbutt 7y agoThey are always following chrome's tail. But anyway, the reason probably is that some extensions are abusive of personal data and you don't want them sniffing stuff in private browsing (with out your persmission).
- callahad 7y agoIt's not perfect, but there are prominent prompts about this when you install an add-on for the first time and when you open a private window. Screenshots at https://imgur.com/a/d4ZnAHI https://imgur.com/a/d4ZnAHI
- recursive 7y agoNo one thought that was a good idea. The good idea is to prevent add-on authors from stealing private browsing history.
- jszymborski 7y agoI believe this is also an attempt to block fingerprinting.