Leaderboard

... I'm always puzzled by that type of a query ; both links you posted are currently live/valid, so, with respect, why can't you test yourself? Why do others have to test them for you? In any case, both extensions (not plugins, BTW) belong to a "hybrid" type of an extension, in reality a WebExtension format inside a JetPack extension format; you can see for yourself, if you open the XPIs with 7-zip; as such, they may install under NM28, but they WON'T function as expected (e.g., there's no way to even access their toolbar buttons) ... I haven't tested with latest St52/St55, but they would install there and SHOULD work as expected ; from past recollection, Browsec only offers 4 free/anonymous nodes; unsure what the current state of Windscribe would be; many years ago already, they had disabled the "anonymous" free tier option (initially 2GB, then just 1GB of monthly traffic was allocated to a fresh extension install), now all versions of their extension require you to register an account with them; a valid/verified e-mail address will grant you 10GB of monthly traffic, on a limited subset of their nodes; but v0.1.61, being an ancient one, might've been blocked from connecting to their servers ... PS: Please, don't confuse the official upstream apps with the roytam1 forks; use the terms New Moon 28 and Serpent 52 (55) for the latter; FYI, official Basilisk does not support WebExtensions...

@reboot12 I found out with Ubuntu, what is going on. The Gemini chipset with 4105 uses another Firmware, vs 46. My driver uses vs 77. So, fun goes on, I just build new driver with Firmware 46 Dietmar

Do we really want this? No. VPN in browsers is a slimmed-down and not really sensible solution. A system-wide VPN is the real deal. I personally avoid those VPN extensions. And Windscribe is unfortunately crap. But TBH, there are dedicated threads here in the Windows XP forum with all necessary information about VPN. Keep in mind that all such browser extensions are old and no longer maintained for legacy browsers! Although updated very regularly, New Moon 28 and Serpent 52 are still very old browsers that are not really or not at all taken into account in the development of extensions. And in terms of VPN not at all. In any case, I would not install an extension in my perfectly adjusted and completely error-free browser that is obviously no longer compatible. Either you fix the extension yourself or it goes to the data graveyard.

autohide taskbar functionality fixed in 3.9.23. thanks!

LOL, understood! Anyway, I've been using Supermium for ages now, and I've always been very happy with it. I'm not going to rush to use another browser just to gain a few more Chromium versions. The Supermium developer has mentioned in the past about using the equivalent of ESR versions of Chromium. How relevant that is, I don't know, as ESR versions are a Mozilla thing of course, but that may explain why he doesn't keep on updating with new Chromium versions as soon as they're released. He seems to update after about another 10 Chromium versions.

Notice: next build will bring you libdav1d instead of libaom for AV1 decoding, not fully tested but looks like working from my limited testings.

Yes, also on 8.0

Sandbox working

I already know what is messing up Chromium 127+ It is the kernel32.dll and kernelbase.dll version checking. I rewrote it to return a false value for them indicating Win 10, and here is the result: The latest versions also use IsWindowArranged from user32, which is absent in 8.1 - possible to be replaced by, for example, IsWindowVisible. Now it remains for me to write my own version of UpdateProcThreadAttribute.

That is, the breaking of the engine or V8 by author continues. The question is for what reason? The author doesn't have to do anything with it to maintain legacy OS compatibility.

https://github.com/win32ss/supermium/issues/1367 I don't have a github account, so if someone could pass on. Win32ss needs a bcryptprimitives function, specifically ProcessPrng. Supermium doesn't have VMP anyway, so the author can change the import to his own implementation of bcryptprimitives in the patcher anyway. GetProcessMitigationPolicy and SetThreadInformation are also needed, but from what I've seen the author of Supermium certainly knows. Oh, right, I forgot. On Supermium 132, including R3 widevine does not work at all, even on Windows 10, and even more so with the repaired widevine under 7, or with original widevine with VXkex. The world does not end with Netflix, there are many sites that use DRM, for which unnecessary for the author to buy VMP license for Supermium. Works in 126 R7:

Unfortunately, versions 2830.0 and 2380.100 have recently stopped working. For now, my temporary workaround for 4.10.2891.0 on Win 7 is to use pwrp_k32 from Supermium instead of kernel32, an p_cryptp instead of bcryptprimitives. There are actually a few functions missing, so perhaps I will write my wrapper and make it available to the public. That's basically what Mozilla does. https://hg-edge.mozilla.org/releases/mozilla-esr115/log?rev=widevine You can find bcryptprimitives in the widevinecdm.dll file by searching 62 00 63 00 72 00 79 00 70 00 74 00 70 00 72 00 69 00 6D 00 69 00 74 00 69 00 76 00 65 00 73 in hex editor (two occurrences), replace, for example, 62 at the beginning with 78, and name the p_cryptp.dll file xcryptprimitives.dll.

Indeed, the sandbox is fixed. #supermium-tab-options works fairly decently, although v109 mode has minimal bugs (at least on 7 SP1 with Aero).

No, any pure Chromium lacks API keys and OAuth2, I remind you that I only applied e3kskoy7wqk patches to the completely original Chromium. I have not tried this flag, I will check it under Win7, on which, of course, my rebuilts work.

Unfortunately, Chrome Sync still does not work after adding Google API keys, you still need OAuth2 keys. As a not being a Chromium developer, you can only use the default keys, which can be added with the --oauth2-client-id and --oauth2-client-secret flags. There is a simple solution for this, so that you won't have to add flag it to shortcuts or in the registry (in case you set it as default browser) void ChromeMainDelegate::PreSandboxStartup() { base::CommandLine& command_line = *base::CommandLine::ForCurrentProcess(); std::string process_type = command_line.GetSwitchValueASCII(switches::kProcessType); if (!command_line->HasSwitch("oauth2-client-id")) { command_line->AppendSwitchASCII("oauth2-client-id", "77185425430.apps.googleusercontent.com"); } if (!command_line->HasSwitch("oauth2-client-secret")) { command_line->AppendSwitchASCII("oauth2-client-secret", "OTJgUOQcT7lO7GsGZq2G4IlT"); } With this code, replace the PreSandboxStartup() function in the chrome_main_delegate.cc file. Edit: in testing/variations/fieldtrial_testing_config.json there are flags about TabStripComboButton and disabling MV2 support. They override the default values declared in the corresponding files, hence you need to remove them from this json.

The patcher included by e3kskoy7wqk, along with the diff files for each compilation (a total of 5 apply_patches.bat files), require a bit more correction than the author claims. At “REPO_PATH=E:\win7dep\chromium\src” change the path to yours, of course, but besides that, you also need to replace “!REPO_PATH!” with “%REPO_PATH%” in two places. In addition, it is required to add clang_use_chrome_plugins = false to args.gn.