Vivaldi Browser

Hi folks. As you know, Vivaldi is a partially open source browser based on Chromium. They say that the closed source part is about the ui and peculiar features in the browser. I am aware of their privacy policy, the unique identifiers etc. But I would like to learn about if the closed sourced part is important, or not.

I mean if you can see the core functions in the open source code and cannot inspect the code about UI and other stuff, is it a problem or not. Or, is it possible to distinguish the code about ui and other parts which is relevant to our privacy?

I don’t have first hand knowledge of this browser, but the above ^ is exactly the type of stuff that seems like it would benefit most from being open source (from a security and bugspotting/bugfixing point of view)

I am not talking about privacy and security here, but I think the “partially open source” stuff is a meme. Ofc it’s going to be partially open source, because chromium itself is open source. Are we also going to say that edge/chrome is “partially open source” ?

1 Like

That is why I asked the question since I don’t have any coding knowledge. Is there any kind of mechanism that can be used to verify that closed source part of Vivaldi is not making any additional connection or collecting personal data if those components/parts are only intended for UI and feature improvements?

You could probably just wireshark it

2 Likes