Chromium - Privacy-Focused Builds

Thank you! Yeah, it is reported as "undetermined", I'm using these command lines too.

 

what would be the difference between google chrome and Chromium Sync? (if I use the sync feature)

 

https://chromium.woolyss.com/#features

 

Stable branch 56.0.2924.87 x64 builds are available now: No 32-bit builds yet.

Link: https://github.com/henrypp/chromium/releases/tag/v56.0.2924.87-r433059-win64
Link: https://chromium.woolyss.com/#windows-64-bit

EDIT: 32-bit builds are up now as well.

Link: https://github.com/henrypp/chromium/releases/tag/v56.0.2924.87-r433059-win32
Link: https://chromium.woolyss.com/#windows-32-bit

 

I recently downloaded chrlauncher and gave it a try. However I cannot seem to notice any differences between chromium variants "stable-codecs-sync" and "stable-codecs-nosync". I wonder if there really is any difference between these two.

For some reason I also seem to be getting pretty easily the "Aw, snap!" error message when trying to test the flash plugin (https://www.adobe.com/software/flash/about/). I have reinstalled chromium several times, but have not been able to figure out what ultimately makes the flash player to start crashing.This happens on all three computers I have tried it (Windows 7 & Windows 10)

I have downloaded and installed the PPAPI flash player separately from Adobe, so I have commented out the pepflashplayer line in chrlauncer.ini

I guess that chromium should also work when installed into \Program Files directory, this is where I have installed it (=binaries there; user data dir under %APPDATA%). But maybe I'm wrong.

With chrome I have not had this kind of problems...

Any advice is appreciated.

 

If i look at the comments on the chromium-website, it seems you have to use the sync-build if you want Flash to work:

 

chrlauncher (http://www.henrypp.org/product/chrlauncher) version 2.3, released today, adds support for downloading/installing, auto-updating and/or portable builds of ungoogled-chromium (https://github.com/Eloston/ungoogled-chromium) both 32-bit and 64-bit builds.

Keep in mind that these ungoogled-chromium builds are not compiled by Nik, Woolyss, or Henry++. Simply, Henry++ tool chrlauncher utilizes API from Woolyss' site to download ungoogled-chromium builds as described here (https://github.com/henrypp/chrlauncher/issues/33#issuecomment-279736691):

You can see release notes for chrlauncher here: https://github.com/henrypp/chrlauncher/blob/master/CHANGELOG.md

 

Thank you! Updated here.

 

All Chromium/Chrome binaries (all included executables and DLL's) after revision 451116 are compiled with Control Flow Guard.
See: https://bugs.chromium.org/p/chromium/issues/detail?id=584575#c15

Previously CFG was only compiled with chrome.exe and chrome_elf.dll if I remember correctly.

 

New release of Chromium available
Current stable version: 57.0.2987.98 (10 Mar 2017)
Download x64
Download x86

chrome://plugins was removed:

 

@mood Excellent, thank you for the heads up! This build is running smooth so far here from RAMDisk.

There still seems to be an issue with the No WebRTC version and Flash Player crashing unfortunately. But for now I am just using the Sync build because I do still need the occasional C2R Flash content but I simply just do not log into the Google Sync functionality.

 

Flash is increasingly deprecated and majority of Flash sites will now run in HTML 5. No more slowdowns and freezes and browser uptime is markedly improved.

 

New and fresh dev builds are also available: 59.0.3038.0

 

57.0.2987.110 Stable update is available now.
64-bit: https://chromium.woolyss.com/#windows-64-bit
32-bit: https://chromium.woolyss.com/#windows-32-bit

 

is there any way to get flash to work with the no-sync version?

 

When I last used it I got it running Flash by setting option in Content settings to Allow sites to run flash:

 

Stable branch release 57.0.2987.133 (444943) is available now:

64-bit: https://chromium.woolyss.com/#windows-64-bit
32-bit: https://chromium.woolyss.com/#windows-32-bit

 

Why You Shouldn’t Use (Most) Alternative Browsers Based on Google Chrome (by howtogeek)

 

Reasons described in that article are IMO not valid for woolyss releases.

 

Is the Google Safe-Browsing disabled in Chromium Woolyss?

 

disabled because of ...?

dont know about chrome, but any other has the option to opt-out - where is the problem?
did you not test yourself? why not?

 

If I understand it correctly, the "No sync • No WebRTC • No Widevine" builds at Woolyss' site do not have the included Google API to allow for Google Safe Browsing to be enabled. However, the "Sync • WebRTC • Widevine" builds do include all of the relevant Google API functionality.

 

Not by default, but you can disable it - the same way as in Chrome.

 

There is still an option in that build, but IDK if it works

 

Regarding the Windows Registry, I just tried out chrlauncher (v2.3) by itself (installing Chromium on its own) and also using it with existing archive versions from woolyss, and in every case with different build types, it creates persistent registry keys and updates them (on Windows 7 64-bit). I thought it would be fully portable like the AluisioASG version.

Chrlauncher creates the following keys:

HKEY_CURRENT_USER\Software\Chromium
HKEY_CURRENT_USER\Software\Google