Devs: Can Vivaldi compile on ungoogled-chromium?

FutureProof

Hey Vivaldi Devs... I think one thing that would make Vivaldi more attractive to some is using these ungoogled-chromium sources: https://ungoogled-software.github.io/

Is that possible?
Thanks!

FutureProof

@yngve - been a minute since your below post, so I figure maybe you could give an update?
https://forum.vivaldi.net/topic/22330/google-spyware-is-still-not-removed/34

Catweazle

Google withdraws most of their APIs on March 15th,(Sync, Store, Security and others) meaning that Chromium will be ungoogled by default and will be the end of most Chromium Browsers without own services.

FutureProof

I think you can still find a lot of difference between the ungoogled-chromium project & chromium code base - even after March 15th... Is my point.

Catweazle

@FutureProof , yes, mainly that in ungoogled Chromiums security updates come much later.

Hadden89

@FutureProof They'll continue to ungoogle chromium (recently they made opt-out several google services) but using the vanilla chromium is safer not to break feature users may need (DRM, webrtc, cast,....) and to keep the codebase more updated and secure. Is not excluded they could consider some "hotfix" from ungoogled chromium forks if applicable to current versions.

Eggcorn

@Catweazle said in Devs: Can Vivaldi compile on ungoogled-chromium?:

Google withdraws most of their APIs on March 15th,(Sync, Store, Security and others) meaning that Chromium will be ungoogled by default and will be the end of most Chromium Browsers without own services.

What does that mean for Vivaldi?

derDay

@Eggcorn
perhaps more vivaldi user, if they used a chromium browser, which had no own services and used the googles one

Eggcorn

@derDay It might be a marketing opportunity for Vivaldi. But I'm thinking more along the lines of: Is Vivaldi going to need it's own extension store now?

derDay

@Eggcorn
probably not, see the discussion in another thread about this problem

Catweazle

@Eggcorn , t would be desirable, but it is not so much an impediment, since there are alternatives to the Chrome Store and you can also install the extensions manually without the Store.
Anyway, the lack of Google APIs is going to be a lesser impact for Vivaldi than in many other browsers.

Catweazle

@Weebsouls , for all these there are alternatives, either that can be implemented in Vivaldi or through extensions or external applications. What is going to cause headaches will of course be several things to other Chromiums, who have only put their logo in Chromium, without modifications with all the inclusions of Google services, sync included.

FutureProof

My original question was: "currently, can Vivaldi be compiled using ungoogled-chromium?"

Also I don't think the conclusions in this thread so far are entirely true. This is from the ungoogled-chromium maintainer (which can be found in their matrix & gitter.im chats):

"please refer to https://github.com/Eloston/ungoogled-chromium/discussions/1351
tl;dr It is incorrect to say Chromium will be completely ungoogled.

Longer answer: From my understanding, using Chromium without API keys today should be the same as the change they're making in March. Short term, this probably won't change anything for us. Looking optimistically long-term, we reduce/remove patches in ungoogled-chromium. I am betting there is still ungoogling we will need to do. I don't want to speculate the specifics because I don't believe it will help us take any preemptive action."

smelly

I found Vivaldi as the most-recommended pro-privacy browser, aside from Brave which I absolutely do not trust and is redundant with ScriptSafe and FPMON installed.

Therefore features like DRM are very unwanted, as they can be used to identify pretty much anyone (even Tor users have this problem on Windows.) I'm going to try Ungoogled-Chromium for the same reasons I tried Vivaldi and certainly hope that it does compile. I really love some of these UI features.