Vivaldi: Built using Chromium, but different from Chrome
-
- Raspberry Pi runs Linux and all its standard toolset is at your dusposal. GTK, Qt, whatever,
- Desktop UI looks comical and is wholly inappropriate on mobile devices. Et vice versa.
-
Very good those explanations
-
@anrdaemon I didn't say a mobile version would be the same as desktop, but it means that functions made for desktop can easily be adapted for mobile.
And I would class "web based" as "whatever" in your list of interfaces. The point is that any platform where the Chromium engine runs can already have the UI - without even needing to look at QT etc.
-
Still waiting for Vivaldi Sync feature
-
@pesala: No-one may be common outside of North America, but I'd challenge anyone to find no-one North America. Rather, no one is the preferred version.
-
@amutavdzija Yes, I know it is commonly used. I said that it was incorrect in my opinion for the reasons stated.
-
The only thing I dislike with Vivaldi is Google and Google Chrome. Ideal would be to ignore all Google, which I feel is the worst thing on the net due to its privacy intrusion.
-
@linfan Vivaldi has to have an engine. Chromium (not Chrome) was the most practical one to adopt. Vivaldi does not have any of the Chrome privacy intrusions enabled. Google does not get any of your data unless you sign in to their sevices - and that is the case with all browsers.
-
@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?