All Activity

The OpenSSL from here says: OpenSSL 3.6.1 27 Jan 2026 (Library: OpenSSL 3.6.1 27 Jan 2026) built on: Wed Jan 28 15:01:03 2026 UTC platform: VC-WIN32 options: bn(64,32) compiler: cl /Z7 /Fdossl_static.pdb /Gs0 /GF /Gy /MD /W3 /wd4090 /nologo /O2 -DL_ENDIAN -DOPENSSL_PIC -D"OPENSSL_BUILDING_OPENSSL" -D"OPENSSL_SYS_WIN32" -D"WIN32_LEAN_AND_MEAN" -D"UNICODE" -D"_UNICODE" -D"_CRT_SECURE_NO_DEPRECATE" -D"_WINSOCK_DEPRECATED_NO_WARNINGS" -D"NDEBUG" -D_USE_32BIT_TIME_T -D_WINSOCK_DEPRECATED_NO_WARNINGS -D_WIN32_WINNT=0x0501 OPENSSLDIR: "C:\Program Files (x86)\Common Files\SSL" ENGINESDIR: "C:\Program Files (x86)\OpenSSL\lib\engines-3" MODULESDIR: "C:\Program Files (x86)\OpenSSL\lib\ossl-modules" Seeding source: os-specific CPUINFO: OPENSSL_ia32cap=0x46da222b478bfdff:0x0000000000002509:0x0000000010000400:0x0000000000000000:0x0000000000000000

They are actually and always have been. I don't update the upstream script anymore, but all that I locally changed was "openssl-3.3.1" to "openssl-3.6.1". https://github.com/Reino17/ffmpeg-windows-build-helpers/blob/master/ffmpeg_local_builds/cross_compile_ffmpeg.sh#L78-L104 C:\>openssl.exe version -a OpenSSL 3.6.1 27 Jan 2026 (Library: OpenSSL 3.6.1 27 Jan 2026) built on: Sat Jan 31 22:56:33 2026 UTC platform: mingw options: bn(64,32) compiler: /cygdrive/e/ffmpeg-windows-build-helpers-master/ffmpeg_local_builds/sandbox/cross_compilers/mingw-w64-i686/bin/i686-w64-mingw32-gcc -m32 -O2 -march=pentium3 -mtune=athlon-xp -mfpmath=sse -msse -DL_ENDIAN -DOPENSSL_PIC -DUNICODE -D_UNICODE -DWIN32_LEAN_AND_MEAN -D_MT -DOPENSSL_BUILDING_OPENSSL -DZLIB -DNDEBUG -D_WIN32_WINNT=0x501 OPENSSLDIR: "/cygdrive/e/ffmpeg-windows-build-helpers-master/ffmpeg_local_builds/sandbox/cross_compilers/mingw-w64-i686/i686-w64-mingw32/ssl" ENGINESDIR: "/cygdrive/e/ffmpeg-windows-build-helpers-master/ffmpeg_local_builds/sandbox/cross_compilers/mingw-w64-i686/i686-w64-mingw32/lib/engines-3" MODULESDIR: "/cygdrive/e/ffmpeg-windows-build-helpers-master/ffmpeg_local_builds/sandbox/cross_compilers/mingw-w64-i686/i686-w64-mingw32/lib/ossl-modules" Seeding source: os-specific CPUINFO: OPENSSL_ia32cap=0xfed8320b078bffff:0x00405fc6f1bf97a9:0x0000003000000110:0x0000000000000000:0x0000000000000000 The last time I've updated the "MingGW-w64 Build Script" was 18 Sep 2022.

Current New Moon. Current 55 basilisk also show page without errors, after some seconds i see popup with message "We'd like to send you notifications." - maybe you use external adblocker with agressive profile?

Which version are you using? I'm on 55 basilisk and the error is there even with a new profile.

I'm not seeing what you describe. Are you allowing any sort of "prerendering" or "AI-powered protection" or "safe browsing protection"? ALL are disabled on my config.

You can't visit https://rutracker.org/ or https://www.ozon.ru/ or https://www.vseinstrumenti.ru/ or https://vkvideo.ru/ ?? Don't see errors after two minutes.

Add this one to the list: https://weather.com/weather/today/l/c4025fdf0177c872b7fc2e0d09e7c523995ef49e21145e2d2438fe08649ca9e8 After about 3 seconds it breaks with this error: Application error: a client-side exception has occurred while loading weather.com (see the browser console for more information).

There might be a "JavaScript hook" that sneakily overwrites the link after it is clicked. Initially the true link is displayed on the status bar in New Moon. In New Moon the link anchor has the parameters: href (true link), data-ved, data-sb (google's redirect) In Supermium the parameters are: href (true link), data-ved, ping (google's redirect) It seems that Chromium is able to do something with "ping" that older browsers are not, perhaps connect to Google in parallel with the target. I didn't even know you could write such custom values into HTML.

I investigated this myself and the reason appears to be that @Reino's DLLs haven't been "stripped" post successful compilation : https://en.wikipedia.org/wiki/Strip_(Unix) In an MSYS2 environment, $ strip libssl-3.dll will reduce the filesize from 1.22 MiB to just 890 KiB, while $ strip libcrypto-3.dll will reduce the filesize from 5.20 MiB to just 3.88 MiB Finally, as a general observation, different compilers will produce binaries with different filesizes, even when the source code is always the same; and, of course, using different compilation flags between two different compiler invocations will also produce binaries with (slightly?) different filesizes, even when the compiler and source remain unchanged... The DLLs obtained from slproweb were compiled using a "CL" compiler (MSVC C/C++), as you can see by running: openssl version -a => OpenSSL 3.6.1 27 Jan 2026 (Library: OpenSSL 3.6.1 27 Jan 2026) built on: Wed Jan 28 15:01:03 2026 UTC platform: VC-WIN32 options: bn(64,32) compiler: cl /Z7 /Fdossl_static.pdb /Gs0 /GF /Gy /MD /W3 /wd4090 /nologo /O2 -DL_ENDIAN -DOPENSSL_PIC -D"OPENSSL_BUILDING_OPENSSL" -D"OPENSSL_SYS_WIN32" -D"WIN32_LEAN_AND_MEAN" -D"UNICODE" -D"_UNICODE" -D"_CRT_SECURE_NO_DEPRECATE" -D"_WINSOCK_DEPRECATED_NO_WARNINGS" -D"NDEBUG" -D_USE_32BIT_TIME_T -D_WINSOCK_DEPRECATED_NO_WARNINGS -D_WIN32_WINNT=0x0501 OPENSSLDIR: "C:\Program Files (x86)\Common Files\SSL" ENGINESDIR: "C:\Program Files (x86)\OpenSSL\lib\engines-3" MODULESDIR: "C:\Program Files (x86)\OpenSSL\lib\ossl-modules" Seeding source: os-specific CPUINFO: OPENSSL_ia32cap=0x0000e39defebffff:0x0000000000000000:0x0000000000000000:0x0000000000000000:0x0000000000000000 These two are also linked to vcruntime140.dll (external MSVC dependency, thus this further reduces the DLLs's filesize). My educated guess is that Reino's DLLs were compiled with some flavour of MinGW/MSYS2 (as can be deduced from the linked GH issue ), and that compiler is known to produce larger binaries than MS's Visual Studio (but I could be wrong somewhere, without knowing all the finer details ) ...

Showing screencap's of the "about" dialog is about as useful to the discussion as showing a picture of my dog! At any rate, I cannot even do any Google searches now, all I get is the D#MN F'IN CLOUDFLARE CAPTCHA B#LL F'IN SH#T (in most-recent New Moon, didn't even bother in anything else). If the previous post is correct about spoofing UA (I am unable to verify), then the next step should be to go the other route, spoof New Moon's UA on Google and check results. Because this is SERVER-SIDE. Chrome/Chromium/Supermium/r3dfox is being sent DIFFERENT HTML CODE then New Moon. They are all simply rendering what the server is sending them. And New Moon is being "singled out". (I did not check other Roytam browsers, only New Moon.)

I don't need them now, but others might prefer them. What I'm wondering is, why are your dll's larger in file size than the ones from here? libcrypto-3.dll: 5.19MB vs 4.38MB libssl-3.dll: 1.21MB vs 1.01MB More features?

I don't need them now, but others might prefer them. What I'm wondering is, why are your dll's larger in file size than the ones from here? libcrypto-3.dll: 5.19MB vs 4.38MB libssl-3.dll: 1.21MB vs 1.01MB More features?

its a gamble you dont know the variables one varible to jump out would be corruption in similiar things there are bet´s - while the bet´s are being told/know whatsoever (or told to the managers team) the "team" was then told just to play defence - so you cant see the differens then the suppose to be the better team lost but that would be 1 condition to leave this there is also many things coming together, you defined a team based sport so a 1 good sportsman in that sport wouldnt win the match dayly form not included injuries missing people for that match sometimes players fit better to a different style then others doping plays also a rule, for soccer a good drug is cocaine (as it increases brain activity and power to the body) (you therefore have to define what would be good for this sport also, you dont need a bodybuilder - they would be to heavy) in the soccer example you have 11 people influencing the match luck is also part of this - if we dont call it luck then we call it momentum - there was such things where good teams have lost to bad teams so you wont have a clear answer

vkvideo.ru sure is a heavy site, eats 1.3GB of RAM and videos (or rather pictures of them) are really stretched (magnified)... (Serpent 52.9, latest)

Just tried spoofing the UA, the same.

And no such tracking in the official Ungoogled Chromium either.

ie, it's not Mozilla versus Google thing. I didn't try, but something tells me that Google will serve the *tracking links* versions to Chrome, Chromium, Supermium, and r3dfox *IF* you set the user agent to match that of New Moon. Have not tried... Will try this afternoon if nobody else can first...

On my end - vanilla Chrome, vanilla Chromium, vanilla Supermium, and vanilla r3dfox all show the true link withouthout tracking. New Moon (vanilla, most recent) was the only browser that has the tracking links.

Our supervisor says Cloudflare isn't fake. Read a lot of posts where MSFN members do solve Cloudflare ans other verification captchas. I immediately close such websites.

No such thing in CatsXP, also Chromium.

Do we need to assume bots use the default browser flags positions?

Edge appears to be the same, so I guess it's a Chromium thing?

thats a simple function kernel extenders have it already somewhere however it would be better to use dependency walker to see if there are more

Then why do you need mine? While I was at it (compiling OpenSSL) I've had a look at this, but I couldn't compile quickjs. The culprit is undoubtedly "Add cross-platform Atomics support". I think it will be extremely difficult to restore WinXP compatibility. Attempting this at all, I think a patch similar to how I (with the help of Gianluigi "sherpya" Tiesi) restored WinXP compatibility to libaom back in the day is needed. We could ask him to have a look?

I just noticed that when I copy a link from Google search using Supermium, I actually get the target link. But if I copy with an old browser, such as New Moon, I get the redicted link managed by Google. Why is it that Supermium has access to the true obfuscated link?