@vivaldi\_browser maybe tell people you don't do this sort of thing: [https://infosec.exchange/@WPalant/111027907021400159](https://infosec.exchange/@WPalant/1110
@vivaldi\_browser maybe tell people you don't do this sort of thing: [https://infosec.exchange/@WPalant/111027907021400159](https://infosec.exchange/@WPalant/1110
@vivaldi_browser maybe tell people you don't do this sort of thing: https://infosec.exchange/@WPalant/111027907021400159
Latest Vivaldi release doesn't have Enhanced Safe Browsing.
@epp @vivaldi_browser @Vivaldi
Thanks for letting me know
Apart the information is wrong, the Google attempt with WEI DRM has nothing to do with the browser engine, it's a web API wich give the webs the ability to block any browser, be it Chromium, Gecko or WebKit, if it does not include a Google token that "certifies security". That is, it doesn't matter if you use Firefox, Safari or any other, if it doesn't have this token, Game over. Such nonsense on the part of Google cannot be allowed. It is legitimate that web pages are given a tool to protect themselves, but it cannot depend on a commercial company to decide which browser deserves this token and which does not, this should by far depend on an independent technological institution. Let's see if this has been made clear once and for all.
Which part of toot is wrong?
That Vivaldi hasn't enhanced safe browsing, you can select it in the settings, if you want and you can see in the screenshot. Firefox has it established, it is called Firefox Safe Browsing, same with Safari, but all these are the safe browsing API from Google, also in Vivaldi, in which you have the posibility to desactivate it, because it isn't really needed, it has filters in the inbuild ad/trackerblocker which do the same (include Filterlists from ABP, uBO, DDG and you can add others, if you want), without this Google API. I think it's good enhanced, and without the obligation of having to use this Google thing.
