Vivaldi: Built using Chromium, but different from Chrome
-
@ayespy maybe, but at the same time when I use Vivaldi some strange things happen, occasional glitches I'd say, sometimes opening a new tab I get Google's main page, considering I have switched off everything Google it shouldn't happen, my suspect is that if you use chromium you can't really switch off Google.
-
Nice that you state this clearly, as I think it's a good market niche: With Vivaldi you get the same Chromium engine and page compatibility as with Google Chrome, also have a professionally maintained browser, but with much better (European?) privacy standards!
Firefox as fully open source browser can compete with this only as long as you do not install a dozen of addons to get the features Vivaldi has built in. Dozens of addons mean you need to trust dozens of developers around the globe in their skills in keeping their addons secure and you need to trust them in not changing their business models unnoticed (like evernote temporarily did..).
So it is a good idea to be clear about the privacy and if it complies to European privacy rights, the sections of openly published source code and the business model with (privacy respecting) search engine contracts.
Keep up the good work! -
@talgarik said in Vivaldi: Built using Chromium, but different from Chrome:
my suspect is that if you use chromium you can't really switch off Google.
I'm sure you suspect that. However, it's not accurate. One thing that might hook into Google when you don't want it, is the occasional extension. Further, not every aspect of the original Chromium interface has been erased for Vivaldi. That's a work in progress. But as far as sending data to Google, Vivaldi simply does not do that. Extensions may.
-
Vivaldi is becoming a really great browser. Only one thing is still keeping me from switching (at work). Will Emulation view work with detached console window in a coming version? This is essential to me.
-
@healing_cross
Hi, Stable is at Chrome 67 security level, Opera too.
If really needed Vivaldi patch the Stable 1.5 at the level of Chrome 68.
There are two new anti-malvertising features in Chrome 68, we have to wait and see.
Chrome 68 is a few days old so they need some time to get to it.CHeers, mib
-
@mib2berlin said in Vivaldi: Built using Chromium, but different from Chrome:
Hi, Stable is at Chrome 67
Nah. The Stable engine uses Chr65
-
@lamarca said in Vivaldi: Built using Chromium, but different from Chrome:
Nah. The Stable engine uses Chr65
Nah - Security is Chr67!
There was a minor update: https://vivaldi.com/blog/minor-update-to-vivaldi-1-15-2/ -
@lamarca
Hi, I meant it use security patches of Chromium 67.https://vivaldi.com/blog/minor-update-to-vivaldi-1-15-2/
Cheers, mib
-
@tbgbe Not that I don't trust you, let me start the Stable.
-
@healing_cross said in Vivaldi: Built using Chromium, but different from Chrome:
It's just the information I had and the reason for my question. The respective URL shows me the same Engine 65 for 1.15
Correct.
The engine is Chr65 - however, (applicable !? ) security updates from Chr67 were "backported" into Vivaldi Stable using an update.@lamarca Only security update(s) - the engine is still Chr65 so Chr67 will not show in the Stable version.
-
@tbgbe I snatched a screenshot, just in case. Probably the 1.16 will switch to Chr67.
That engine gave me a hard time on mouse, proprietary media.
-
@mib2berlin said in Vivaldi: Built using Chromium, but different from Chrome:
Hi, I meant it use security patches of Chromium 67.
Thanks for taking your time to provide the link. Just out of curiosity, do you use backport?
-
@tbgbe said in Vivaldi: Built using Chromium, but different from Chrome:
The engine is Chr65 - however, (applicable !? ) security updates from Chr67 were "backported" into Vivaldi Stable using an update.
Same question, how often you backport any piece of softaware?
-
Backport is a repository for testing. All the packages have a high number version of the stable version. It's a procedure where you get a small "piece" of the software to use in the stable soft.
-
@healing_cross To "backport" a security fix means to include a fix that was issued in a later version, as part of an earlier version. As the fixes are in the Chromium code, you can rely on them to the same degeree that you could rely on the same fixes in Chrome.
It is not for Vivaldi (or anyone) to proclaim whether you can "rely" on all or any particular security patch. You use free software that you download from the web at your own risk. You decide whether to trust it or not based upon reputation and your prior experience, if any with the software. No one can guarantee how secure a particular piece of software is.
-
@healing_cross said in Vivaldi: Built using Chromium, but different from Chrome:
Can I rely on all the security patches that were built into recent versions of Chrome ........
Absolutely, yes.
You posted while I composing the backport question. -
@healing_cross When you update to any "new" version, any backports that were included in an earlier number of that same stream will also be included in the updated version. Nothing is determined by the manner in which you update. What is in the software is what is in it.
-
@lamarca said in Vivaldi: Built using Chromium, but different from Chrome:
Same question, how often you backport any piece of softaware?
Haven't done it for years now.
But Vivaldi devs have done it to a few Stable versions when a new Chromium was released.
At least, they have according to the blogs -
@tbgbe Skipping from 65 to 67, they had no other way. Backporting Kernel is funny when there's time. I am on 4.9.110-1
-
@healing_cross If Vivaldi had a 200-strong development team like Opera does, it would be in much closer sync with the Chromium release schedule. Instead, it has about a tenth that - so there are fewer people to do the work of keeping up.
That said, Vivaldi and Opera are designed differently (in order for Vivaldi to have the flexibility to add the features that it does), and that difference often means that Chromium changes create regressions in Vivaldi that Opera does not suffer from.
When Chromium changes do not severely break Vivaldi, then even the very small team is able to keep up with the Chromium release schedule on about a 1-week delay. About the same as Opera.