Leaderboard

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260613-3219d2d-uxp-ec5b4aa693-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20260613-3219d2d-uxp-ec5b4aa693-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260613-3219d2d-uxp-ec5b4aa693-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260613-d849524bd-uxp-ec5b4aa693-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260613-d849524bd-uxp-ec5b4aa693-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260613-d849524bd-uxp-ec5b4aa693-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260613-d849524bd-uxp-ec5b4aa693-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260613-d849524bd-uxp-ec5b4aa693-w7plus-avx2.7z Official UXP changes picked since my last build: - Revert "Bug 2027433 use nullptr for silent up-mix channels" (4d9fe0ca23) - Revert "Bug 2027433 Treat null input channels as zero in AudioChannelsDownMix()" (cbdec72879) - Revert "Bug 2027433 Treat null input channels as zero in InterleaveAndConvertBuffer()" (68b774798b) - [DOM] Provide more silent audio processing frames. (f83dd5bf22) - Issue #3111 - Clean up logic in SweepFinalizationRegistries. (b336d24faf) Official Pale-Moon changes picked since my last build: - [Pale-Moon] Adjust default theme to handle adjusted metrics for border truncation. (d7d7589555) No official Basilisk changes picked since my last build. My changes since my last build: - Revert "Revert "Revert "Revert "Implement FinalizationRegistry" and related commits.""" (ff2a1248c4) Update Notice: - You may delete file named icudt*.dat and icu63.dll inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

In CFF Explorer, replace the kernel32.dll import with pwrp_k32.dll and copy this file from your Supermium installation. The screenshot was taken on XP RTM

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260606-3219d2d-uxp-bfaade4306-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20260606-3219d2d-uxp-bfaade4306-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260606-3219d2d-uxp-bfaade4306-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260606-d849524bd-uxp-bfaade4306-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260606-d849524bd-uxp-bfaade4306-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260606-d849524bd-uxp-bfaade4306-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260606-d849524bd-uxp-bfaade4306-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260606-d849524bd-uxp-bfaade4306-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #3109 - Clamp border-radius value to CSS' internal length clamp value (d47606ce8f) - Issue #2964 - Part 1: CSS Override for `uppercase` and `capitalize` (dff842a949) - Issue #2964 - Part 2a: Correctly Detect End of Buffer in `ToUpperCaseImpl` (7a933598d7) - Issue #2964 - Part 2b: Improve `ToUpperCaseLength` (b2f6fded36) - Issue #2964 - Part 3: JS Override for `ToUpperCase` (5dc2f08e29) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes since my last build: - Revert "Revert "Implement FinalizationRegistry" and related commits." (1e38b5ec94) - mozapps/handling: fix application icon handling by reboot12@msfn (811b13e76c) - Revert "Revert "Revert "Implement FinalizationRegistry" and related commits."" (bfaade4306) Update Notice: - You may delete file named icudt*.dat and icu63.dll inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260620-3219d2d-uxp-f718564719-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20260620-3219d2d-uxp-f718564719-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260620-3219d2d-uxp-f718564719-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260620-d849524bd-uxp-f718564719-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260620-d849524bd-uxp-f718564719-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260620-d849524bd-uxp-f718564719-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260620-d849524bd-uxp-f718564719-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260620-d849524bd-uxp-f718564719-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #2306 - Re-introduce pref for WeakRef API spec. (8eac1db64b) - Issue #2306 - Enable full weakref by default in platform. (0bd0d0a296) - Issue #3122 - Exclude local resources from <base> CSP checks. (692606e89c) - Bug 2029066 - Remove Sinking of Live instructions. (2712943075) - Bug 2029765 - avoid refcount over-release in nssTokenObjectCache error path [@ nssToken_Destroy]. (13d8737677) - [network] Make keep-alive pref Atomic. (f20e0799a0) - [DOM] Reject too large mLength in MutableBlobStorage::WriteRunnable. (b60661dfe1) - Bug 2023478 - improve handling of escape sequences in pk11uri_ParseAttributes. (7ae6442d99) - Bug 2033848 - Use non-default response ID for GTK file picker accept button. r=stransky (81babad165) - [DOM] Zero-initialize ThreadSharedFloatArrayBufferList. (5ab14e5932) - No issue - Use ImmGCPtr for module meta data visits. (0bdcc65c4c) - [parser] Better align with spec definition of adding nodes. (a50e1d7ae5) - [DOM] Avoid over-optimizing some getter/function calls. (a83b6f74bb) - [gfx] Check more offsets during CFF subsetting. (9a457cbfd9) - [network] Make HttpBaseChannel::mLoadFlags atomic. (100f6aaf5b) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. Update Notice: - You may delete file named icudt*.dat and icu63.dll inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

Actually, "supermium_uao.exe" won't launch under XP SP3 (32-bit) because of two missing functions on XP's kernel32 system file: # Report By YY.Depends.Analyzer (Target:5.1.2600-x86) ## kernel32.dll * [ ] InitializeCriticalSectionEx - Supported OS: 6.0.6000, 6.1.7600, 6.2.9200, 6.3.9600, 10.0.10240 - Ref Module: supermium_uao.exe * [ ] LCMapStringEx - Supported OS: 6.0.6000, 6.1.7600, 6.2.9200, 6.3.9600, 10.0.10240 - Ref Module: supermium_uao.exe Above is a log acquired via the YY-Thunks CLI tool; the command I used was: YY.Depends.Analyzer "supermium_uao.exe" /IgnoreReady /ReportView:CheckBox /Target:5.1.2600 As @mjd79 suggested (), if you redirect the kernel32.dll function calls to Supermium's wrapper DLL "pwrp_k32.dll", you'll be able to make the executable XP-compatible ...

The @AstroSkipper version is still working. I created it back when nobody was maintaining the legacy version of uBO anymore. This had led to @UCyborg also working on an updated version again. I tested it for a while and actually think any further development is a good thing, but unfortunately I found incompatibilities and higher resource usage. That’s why I’ve gone back to my version. In my opinion, it’s not easy to implement features in legacy extensions that were actually developed for webextensions.

Would you please stop with that. You have absolutely no clue what I’m dealing with personally and privately, which is why I don't have time to constantly check the server. MSFN is a one-man show. And how do you know I won't say thanks? On top of that, I’ve wanted to shut MSFN down several times over the last few months because of this situation. So back off. Stick to software, hardware discussion or go find another forum. I don't care. Just be careful. Have a nice night or day or whatever.

@nicolaasjan This is an attempt to explain what happens when the contaminated MSFN server meets other search engine bots than Googlebot or bingbot. For everyone else, it refers to @nicolaasjan's test and observation: Why alternative bots (like MojeekBot) trigger the "Welcome Loading ..." freeze 1. The mechanics of the attack: The server-side user agent sniffer The malware installed on the server uses a conditional script (usually written in PHP within core files like index.php or .htaccess rewrites). This script scans the incoming request for specific keywords in the User-Agent string to determine whether to serve the clean forum to a human user or the spam payload to a search engine. 2. The Googlebot trigger vs. the MojeekBot catch-all fault With Googlebot: The malware has a fully defined template. When it detects Googlebot, it successfully injects the hidden HTML container containing the Thai spam, links, and keywords, allowing the page to render fully for the crawler. With MojeekBot (and potentially other secondary search bots): The malware's sniffing routine recognizes the word Bot or Bot/ (via a regular expression or wildcard check like *bot*), flagging it as a search engine. However, the malware's backend does not have a valid spam-template or correct database-routing configured for this specific bot identifier. 3. The cause of the freeze: Broken Document Object Model (DOM) & JavaScript execution The string "Welcome Loading ..." is part of the forum’s native lazy-loading or initialization layout (often used during the initial handshaking phase between the server and the browser's JavaScript engine). When MojeekBot hits the server, the malware triggers, intercepts the request, but then crashes or terminates prematurely (e.g., throwing a silent PHP Fatal Error or an unhandled exception because the variable for the payload is empty or undefined). The backend script crashes mid-execution: It completely fails to fetch and load the actual forum database content (the threads, posts, and UI). It leaves the HTML document incomplete and broken, trapping the page forever in the initial "Welcome Loading..." state. This observation proves that the infection is not a static HTML injection into old threads, but an active, dynamic routing script on the server. It intercepts all automated crawlers based on a broad User-Agent filter, but breaks completely when encountering bots it wasn't explicitly optimized for (like Mojeek). To fix this, the administrator @xper or supervisor @Tripredacus needs to look for malicious conditional statements filtering user agent keywords inside the server configuration or core PHP initialization scripts.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260530-3219d2d-uxp-3c23f8ee4e-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20260530-3219d2d-uxp-3c23f8ee4e-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260530-3219d2d-uxp-3c23f8ee4e-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260530-d849524bd-uxp-3c23f8ee4e-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260530-d849524bd-uxp-3c23f8ee4e-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260530-d849524bd-uxp-3c23f8ee4e-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260530-d849524bd-uxp-3c23f8ee4e-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260530-d849524bd-uxp-3c23f8ee4e-w7plus-avx2.7z Official UXP changes picked since my last build: - Re-land: Fix devtools on 32-bit big endian platforms (0915736715) - Issue #3053 - Implement CSSStyleSheet constructor (f5a84f4ad2) - [js] Use size_t when inflating UTF8 (7bbdccd376) - [NSS] Fix instances of softoken attributes freed after owning object. (300dd371b2) - [NSS] Handle SEC_ASN1_NULL in sec_asn1e_contents_length. (9179441f96) - [libjar] Check Jar entry names for nulls. (aadb6beb07) - [NSS] Align PKCS7 digest array with digestAlgorithms. (089170ae83) - [NSS] NSS_CMSContentInfo_SetContent: only modify cinfo if everything succeeds. (7167a8fabc) - [NSS] Initialize src in SEC_PKCS5GetIV (07201fa1ae) - [NSS] Avoid integer overflow when converting AVA value to hex string. (6511833580) - Bug 2029771 - Heap use-after-free in [@ token_destructor] reading tok->pk11slot after nssToken_Destroy frees the token arena. (57bef0265c) - Bug 2029782 - fix 8-byte over-read of AES-192 key buffer in x86 builds without USE_HW_AES. (92b3f6dd67) - [netwerk] nsRequestObserverProxy ref cleanup. (bb2275d400) - [netwerk] Make nsSocketTransport2::mConnectionFlags atomic. (bb85939429) - Bug 2036905: Fix UDPSocketParent::ConnectInternal data race on mSocket. (8d4079866b) - [netwerk] Make socket transport hold a reference to TLSServerConnectionInfo. (349f46bbb2) - Bug 2027381 - improve error handling in SECITEM_DupArray with non-null arena. (b3f801743b) - [NSS] Fix maxSize calculation in NSSUTIL_AddNSSFlagToModuleSpec. (c36357a954) - Revert "Issue #3092 - Perform a minor GC on tab close" (3ae3595f6a) - Revert "Issue #3092 - Initial idle GC implementation" (860d4457ae) - Revert "Issue #3092 - Implement parallel sweeping and compaction tasks" (52ce9ebea5) - Revert "Issue #3092 - Implement BackgroundFinalizeTask for parallel garbage collection finalization" (ac0510f380) - Revert "Issue #3092 - Add new GC sweep tasks." (e95b229db8) - Revert "Issue #3092 - Refactor WASM compilation handling" (d582d12ad8) - Revert "Issue #3092 - Safely parallelize GC background finalization" (c144b4f403) - [NSS] Fix use of uninitialized length after failed PK11_SignWithMechanism/SymKey. (2a26d9508b) - Bug 2029818 - avoid refcount over-release in CERT_CertChainFromCert error path. (62d731d2c2) - [DOM] Check values in audio resampling. (244c614a47) - [layout] Hide accessible carets when needed. (4bf236902c) - [libvorbis] Allocate memory with _ogg_malloc (e9c3451d54) - No issue - Remove ISO-2022-JP from menu, overridability and detector. (c690e26c67) - [gfx/layout] Simplify textruns (b611d80223) - Bug 1784128 - Assert count passed to PR_Read/PR_Write in nsFileStreamBase fits INT32_MAX. (f83e05cf23) - [DOM] Hold a strong ref to VoiceData in nsSynthVoiceRegistry::RemoveVoice. (2f73a3004b) - [media] ffvpx patch: Fix leak in flac decoder in case of alloc failure. (9afa7a80cc) - [DOM] Stop speech synthesis if the originating document is closed. (f041eb0607) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. Update Notice: - You may delete file named icudt*.dat and icu63.dll inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260523-3219d2d-uxp-829418a939-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20260523-3219d2d-uxp-829418a939-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260523-3219d2d-uxp-829418a939-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260523-d849524bd-uxp-829418a939-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260523-d849524bd-uxp-829418a939-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260523-d849524bd-uxp-829418a939-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260523-d849524bd-uxp-829418a939-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260523-d849524bd-uxp-829418a939-w7plus-avx2.7z Official UXP changes picked since my last build: - Floor fractional border widths (4510bf92a2) - Test fractional border width rounding (794f3fe2e7) - Fix CSS border rounding and currentcolor clipping (c289641428) - Flush layout for computed border-width shorthand (75136dff38) - Fix app-unit rounding for border width edges (50a581840e) - Issue #1826 - Implement broader CSS calc() parsing (29f5ff07d8) - Issue #1826 - Support calc() in media queries (f9a90b9bb2) - Issue #1826 - Canonicalize nested calc() serialization (f94a63864c) - Issue #1826 - Add typed calc() arithmetic for media queries (12b120db24) - Issue #1826 - Serialize special calc() number values (e85f778708) - Issue #2982 - Follow-up: allow color-mix to work with oklab and oklch (20b2b3b9f5) - Load mochitest modules without imp (ee00ac9826) - Remove stale imagebitmap support file entry (4337565d3a) - Issue #2404 - Enable CSS aspect-ratio sizing (0d684399b2) - Support CSS sizing math functions (93899c0157) - Revert "Cloudflare Image Resizing fix take 2" (98c9f7387a) - Issue #3089 - Support logical border radius properties (27f2a0869c) - Issue #1826 - Parse calc() weights in color-mix (4634a74b31) - Issue #2506 - Support range media query syntax (6df85ff502) - Support CSS shadow parts (51767db33a) - Whitelist virtual GPUs (VirtualBox, VMware, VirtIO (QEMU and forks like UTM), Parallels) (235bcb010b) - Issue #3092 - Refactor WASM compilation handling (a7a75b7851) - Issue #3092 - Add new GC sweep tasks. (47746b476e) - Issue #3092 - Implement BackgroundFinalizeTask for parallel garbage collection finalization (c06776336d) - Issue #3092 - Implement parallel sweeping and compaction tasks for improved garbage collection performance (3433d538ed) - Issue #3092 - Initial idle GC implementation (18ddd00afe) - Issue #3092 - Perform a minor GC on tab close (1d3dad153b) - Issue #3092 - Fix unsafe GC multithreading changes (f0cba41221) - Issue #3092 - Safely parallelize GC background finalization (e9826f5559) - Fix JS shell module hook build (6f47a2b0da) - Merge remote-tracking branch 'origin/tracking' into custom (0933486bde) - Implement ES2024 grouping and resolver builtins (e1b689d34e) - Implement ES2024 ArrayBuffer transfer APIs (3be309faa7) - Allow symbols as weak collection keys (e317bf10fc) - Implement growable SharedArrayBuffer (2e51dc9f09) - Implement Atomics.waitAsync (22cb023133) - Implement resizable buffer view semantics (6f3f17ba86) - Guard typed array JIT paths for resizable buffers (d97a2eb04f) - Support DataView on shared array buffers (366476589f) - Support BigInt Atomics waiters (8b09714bbc) - Fix resizable DataView out-of-bounds semantics (aea80980ad) - Validate typed array methods on resizable buffers (3cb76bb20e) - Validate typed array set and constructors on resizable buffers (7613d2901f) - Fix ArrayBuffer slice after resizable source shrink (61912d2318) - Fix ArrayBuffer storage and error types (e21c4e2917) - Fix incorrect variadic for `size_t` in `fprintf` statement in `hyphen.c`. (a02580dae4) - Make WeakRef support always enabled (6861bedff6) - Implement FinalizationRegistry (50c1419e75) - Fix FinalizationRegistry constructor realm prototype (890fb3f399) - Fix WeakRef constructor realm prototype (f3c6da5987) - Issue #888 - Vendor dav1d 1.5.3 (ca94696239) - Issue #888 - Use in-tree dav1d for AV1 decoding (4d1cefd2a1) - Issue #888 - Enable dav1d LoongArch SIMD (d36f889688) - Issue #888 - Remove bundled libaom (2d83afa321) - Issue #888 - Enable dav1d SIMD on more architectures (d328cef713) - Issue #888 - Enable AV1 playback by default (2bd46d4606) - Issue #888 - Update AV1 configure comment for dav1d (3a2f21abfb) - Issue #888 - Fix alphabetical order issue (c95062af66) - Issue #888 - (potentially) fix MSVC builderr (83b19136b4) - Issue #888 - Make symbols direct to dav1d, not AOM. (03a6729a9e) - Issue #888 - Add dav1d_flush (7887ca767f) - Follow-up Issue #888 - Enable dav1d SIMD on more architectures, add back missing nasm detection code in configure (c182d70c0f) - Issue #2354 - Follow-up: Fix building WebRTC on 32-bit ARM without hardware float. (57cd574884) - Issue #888 - Follow-up: Spot-fix; set PREFIX in Dav1d config on Apple. (3155b16f2c) - Fix build on NetBSD/aarch64 (13339f6e55) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - dav1d: port WinXP threading code from mypal68, guard AVX usages with GetVersion() > 5, exclude AVX* assembly from non-x64 build, add ipred16 smooth_weights in sse for non-x64 (808697c1df) - Revert "Issue #3092 - Perform a minor GC on tab close" (3d04e32447) - Revert "Implement FinalizationRegistry" and related commits. (87776c74a9) - Follow-up rev 87776c74, restore Helper prototype changes (829418a939) Update Notice: - You may delete file named icudt*.dat and icu63.dll inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

Calm down folks!

@AstroSkipper I think I'll spend the weekend doing a thorough debugging session on Windows XP because I initially tested the extension on Windows 7. Unfortunately, I can't completely avoid using BAT files, but I'll try to optimize the process.

After all the drama surrounding MSFN, Google has gone and made things even worse. YouTube no longer runs at all within browsers on older, low-performance hardware like my P4. The Vorapis script can no longer play videos on my hardware in New Moon 28 and Serpent 52 on Windows XP. For some reason, the h264 codec can no longer be used in the same way as before. So I’ve removed all scripts and extensions from these browsers. They’ve become useless to me. I now only use VLC with my youtube.lua script. I search on YouTube using the 3D YouTube Downloader, which can of course also download videos and audio files. And naturally, I’m using the latest version of my ‘ytBATCH for Windows XP’ (version 1.7).

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20260613-40a79c75-uxp-ec5b4aa693-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20260613-40a79c75-uxp-ec5b4aa693-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom * Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15. -- New build of HBL-UXP for XP! Test binary: IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20260613-id-656ea98-uxp-ec5b4aa693-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20260613-id-656ea98-ia-c642e3c-uxp-ec5b4aa693-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild

Views counter not counting caused by PHP upgrade. Waiting on patch.

@Dietmar Yeeeeeeeeeeeeeeeeeeeeeeaaaaaaaaaaaaaaaaaaa. For the first time in the world, WinXP 64-bit in pure UEFI from an eMMC disk on Dell Wyse 3040 !!! same acpi.sys 5.2.3790.7777 built by: ddi2 as I use in my modern WinXP tutorial eMMC driver from @George King modded .inf by me eMMC disk size is 8 GB and my WinXP occupies only 1.22 GB all size (I tested installation Win8.1 Lite but occupies 90% disk space) for install I use USB with Win8.1 installer because this support eMMC I had to remove the original sdbus.sys and sffdisk.sys drivers from the system (also from the Driver Cache), need change in hidden bios settings eMMC mode from ACPI to PCI Mode and add Intel eMMC controller Device ID 2294 to critical list devices in regedit: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase I've been waiting for this for a long time. P.S. Now I will also try on Dell Wyse 5070 Gemini Lake on eMMC - maybe I will also succeed ???

openssl-3.6.3-x64-dll.7z

It is proving somewhat difficult to find a configuration that satisfies everyone. I have added a shared XP build that includes ffplay in the previous post.

You don't "need" that tool. All it does is create ONE FILE in your profile directory and Supermium looks for that file. It is called "uao" without any dot-extension. Basically follows this format:

marked for next update. but I'm still waiting for https://repo.palemoon.org/MoonchildProductions/UXP/issues/3111 to be fixed.

Replaced the XP build in the previous link. Added zlib to support png. Added libxml2 as suggested by @VistaLover.

@nicolaasjan Thanks for testing. We will go with a somewhat fuller build and make sure things are functional. A new build will replace the old one shortly.

And whose fault is that? Certainly NOT @autodidact's ; many users here, especially the "XP-die-hards", complained of "inflated" FFmpeg binary sizes; that they ONLY wanted a binary capable of just remuxing downloaded formats (and only with the h264/aac codecs) from youtube.com; nothing more; IOW, a "bare-bones" FFmpeg compile... So, "they" got what "they" asked for (and no more shared builds, on top of that) ... I, of course, was against such a request, because I also use FFmpeg outside of a yt-dlp context; e.g., the latest XP binary can't even fetch MPEG-DASH streams on its own, because it has been compiled without an XML parser (libxml2)); since I'm on Vista SP2 x86, I stayed silent, as the "Vista builds" (many thanks for those shared binaries, too ) continue to fulfill most of my needs under Vista; no complaints here of any sort, @autodidact !

FFmpeg update. XP: static shared libfdk-aac VISTAx86: shared static libfdk-aac

There has been a new release (finally ) by its author, Bellard, of the quickjs JS runtime, necessary for de-scrambling YouTube's nsig challenges (present on most yt_player_clients, except for ANDR-V); the 32-bit binary can be found on: https://bellard.org/quickjs/binary_releases/quickjs-win-i686-2026-06-04.zip (64-bit binary: https://bellard.org/quickjs/binary_releases/quickjs-win-x86_64-2026-06-04.zip) quickjs is the only supported JS runtime on "legacy" WinOSes, like XP SP3/Vista SP2/Win7 SP1; I can't check on XP SP3 x86, but the new release does launch here (Vista SP2 x86): qjs -h => QuickJS version 2026-06-04 usage: qjs [options] [file [args]] -h --help list options -e --eval EXPR evaluate EXPR -i --interactive go to interactive mode -m --module load as ES6 module (default=autodetect) --script load as ES6 script (default=autodetect) --strict force strict mode -I --include file include an additional file --std make 'std' and 'os' available to the loaded script -T --trace trace memory allocation -d --dump dump the memory usage stats --memory-limit n limit the memory usage to 'n' bytes (SI suffixes allowed) --stack-size n limit the stack size to 'n' bytes (SI suffixes allowed) --no-unhandled-rejection ignore unhandled promise rejections -s strip all the debug info --strip-source strip the source code -q --quit just instantiate the interpreter and quit Additionally, the quickjs-ng fork has also seen a new release: https://github.com/quickjs-ng/quickjs/releases/tag/v0.15.1 https://github.com/quickjs-ng/quickjs/releases/download/v0.15.1/qjs-windows-x86.exe This runtime officially supports Win7 SP1 and later, but it can also work under Vista SP2 (but NOT on XP SP3): qjs -h => QuickJS-ng version 0.15.1 usage: qjs [options] [file [args]] -h --help list options -v --version print version string and then exit -e --eval EXPR evaluate EXPR -i --interactive go to interactive mode -C --script load as JS classic script (default=autodetect) -m --module load as ES module (default=autodetect) -I --include file include an additional file --std make 'std', 'os' and 'bjson' available to script -T --trace trace memory allocation -d --dump dump the memory usage stats -D --dump-flags flags for dumping debug data (see DUMP_* defines) -c --compile FILE compile the given JS file as a standalone executable -o --out FILE output file for standalone executables --exe select the executable to use as the base, defaults to the current one --memory-limit n limit the memory usage to 'n' Kbytes --stack-size n limit the stack size to 'n' Kbytes -q --quit just instantiate the interpreter and quit Both are fully supported by latest yt-dlp; performance-wise, they shouldn't differ much, if at all...

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20260606-40a79c75-uxp-bfaade4306-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20260606-40a79c75-uxp-bfaade4306-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom * Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15. -- New build of HBL-UXP for XP! Test binary: IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20260606-id-656ea98-uxp-bfaade4306-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20260606-id-656ea98-ia-c642e3c-uxp-bfaade4306-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild

Nothing was reset. I just pruned some inactive members. Found breach, egyspider webshell. Old WP plugin. Took me 4 days to clean up everything. Reindex sitemap and requested new Google indexing. We are getting back on google. As for country flag, I will fix that. Thanks for pointing it out. Anyway, I do as much as I can. Not much spare time.

Works in Mypal 78, but not in New Moon 28 and Serpent 52. The reason lies in this poorly written function performDownload (line 26, column 119) within the download.js script on the sooftware.com server: function performDownload(num) { event.preventDefault(); ... Strictly speaking, of course, the variable `event` (line 26, column 140) is not defined that way. But Mypal 78 and Supermium seem to be able to handle it. The function performDownload should actually have been constructed this way: function performDownload(event,num) { event.preventDefault(); ... New Moon 28 and Serpent 52 are very sensitive to things like that.

As already mentioned, the next problem I have investigated is the large number of 0-post accounts without any activity created up until 16 January 2026 and one from today. It must be thousands as far as I could see. These were created automatically using a script or other methods over the last years. Maybe, some of them are genuine but most of them aren't. A key indicator for those accounts is whether they have never been visited or only once when creating. Fake accounts, or so-called ‘sleeper’ accounts, could be all those where it says: ‘Last visited: Never’ or ‘Last visited: [Date of creation]’ if looking into them. A genuine account is usually visited in the moment of creation and later from time to time. Real, new members set up all necessary things and take a look into their accounts. Anyway, those accounts are the ‘sleeper cells’ of the attack. They were not used to carry out the infection itself (the malicious code was introduced onto the server via a security vulnerability), but serve as infrastructure to make the spam appear legitimate to Google. Here are two typical examples – accounts that really stand out because of their names and status ‘Last visited: Never’ which does not make any sense at all : 1. Building ‘domain trust’ (initial trust) Large forums such as MSFN have safeguards in place against brand-new accounts. If a bot registers today and immediately posts 50 links, the system raises the alarm and blocks it. Attackers therefore use automated scripts to register thousands of accounts in advance and simply leave them dormant for months. To the forum software (and to Google), the account ages. An account that has existed since “January 2026” will enjoy much greater trust in June 2026 than an account that is only 5 minutes old. 2. The profile spam method (hidden profile links) This is probably the most common use case: every forum member has their own profile page (msfn.org/board/profile/XXXXX-username). A normal user fills in their biography there. A spam bot uses the ‘Website’, ‘About me’ or ‘Signature’ fields to insert Thai keywords and casino links there. The key point: as these accounts have 0 posts, they never appear in active threads. No moderator and no member ever sees them in normal forum activity. But for the Google bot, these profile URLs do exist! The malicious code on the server (our cloaking parasite) now ensures that it feeds the Google bot internal lists of all registered profiles. Google crawls these profile pages, finds the Thai links and indexes them. 3. Exploitation of internal messaging systems (PM spam) or hidden drafts Some sophisticated forum bots use dormant accounts to send spam messages (PMs) to other members in the background (which would, of course, have been noticed), or they create hundreds of posts in the ‘Drafts’ section. These drafts are never published, but exist as data fragments in the database. If the server-side malicious script specifically accesses these tables, it can trick the Google bot into believing that this content is public. 4. Why did the wave of registrations come to an end in January 2026? The fact that no further accounts of this kind were created after January 2026 suggests two possible scenarios: 4.1. The loophole was (unintentionally) closed: The administrators may have installed an update to the forum software in January, activated a new CAPTCHA (e.g. Cloudflare or Google reCAPTCHA), or blocked registration for certain IP ranges or email providers. 4.2. The quota was full: By January, the attackers had generated enough ‘sleeper’ accounts to run their campaign for 2026 and withdrew the registration bots, as the accounts now simply had to ‘mature’. These accounts are used for what is known as profile injection spam. They do not harm the forum database itself, but they serve as a ‘host’ for the hidden links that the server parasite then sends exclusively to Google. For the administrator @xper, this means: not only he has to delete the malicious code, but he must also use a simple database command (SQL) to completely eliminate all accounts with 0 posts that were created over the last years and never visited or visited on the date of creation only, or contain dubious links in their profiles. Or much better, delete them all if there is no genuine activity, as they are then superfluous anyway, apparently not needed and pose a potential risk.

I just changed `general.useragent.override.msfn.org` to: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) But why doesn't the administrator do something about it?

Right, I’ve calmed down now and am trying to take a fresh look at the whole situation and assess it. At first, I thought Google was mainly to blame. @NotHereToPlayGames believes that the owner and administrator @xper are solely to blame. The truth probably lies somewhere in between. Here is an alternative perspective on the whole matter from a very special source whom I am inclined to trust. I will not answer any questions about the nature of this source. It enjoys incognito status. So, believe it or not. The cause: The "Japanese Keyword Hack" (or SEO spam injection) The fact that Google search results display Thai characters or Asian text, even though the actual page is in English, is due to a security vulnerability in the forum software that was exploited by automated spam bots. In professional circles, this is usually referred to as the "Japanese/Thai Keyword Hack". 1. What the spammers did Automated bots exploited a vulnerability on MSFN (often via the internal search function, registration pages or by generating thousands of fake profiles/posts). Unnoticed in the background, so to speak "invisible", they generated millions of artificial, low-quality URLs on MSFN, which were crammed with Thai terms, casino links, dubious diet pills or counterfeit branded products. 2. What Google did during the Core Update Google crawled these hidden spam pages. As a Core Update re-evaluates the entire index, the algorithm noticed the sheer volume of this Thai spam content on MSFN. As these generated spam pages were highly optimised for the Google bot, the algorithm mistakenly assumed that the main topic or main language of certain forum sections was now suddenly Thai. In the search results, Google then mixes the page’s actual title with the injected Thai keywords from the cache, which is why the links look so strangely masked to you. 3. The consequence: Classification as a spam farm Because the Google bot suddenly found millions of pieces of Thai spam content on MSFN, the algorithm pulled the emergency brake. Google classifies the domain at this point as "hacked" or "abused for spam". This leads to an automatic, algorithmic (or sometimes manual) block and a massive wave of de-indexing. In doing so, Google protects its users from suspected malware. Summary for clarification There is no malicious intent on Google’s part: Google does not “think” like a human. The bot simply sees: “Suddenly, 80% of all pages on this domain are Thai spam – so the entire domain is corrupted.” It is not the intention of MSFN: The MSFN administration hasn't done much wrong; it has simply fallen victim to an aggressive, automated wave of hacking that exploited a technical vulnerability in the forum software to carry out illegal SEO sinking. In practical terms, this means: Only once the MSFN administration, @xper and @Tripredacus, has completely removed all these fake URLs, profiles and injections from the server, closed the security loophole and sent a clean re-review request to Google via Search Console will the Thai characters disappear and the site slowly recover its position in the index.

I continued my conversation with Copilote, with following question: "In an earlier conversation today (on another browser) Copilot said Bing was still indexing msfn.org. Was this an error, or is it possible the AI-engine was so called 'hallucinating'?" The answer was interesting (at least to me, probably not to AstroSkipper ). Cited small part of Copilot's answer only: "The earlier answer you saw was not you imagining things — it was almost certainly a case of the AI giving an overconfident but incorrect statement. In other words: yes, that was a hallucination, and I can explain exactly why it happens in this specific situation. 🎯 Short, direct answer Bing used to index MSFN normally, but it no longer indexes new MSFN content reliably. If another Copilot instance told you “Bing is still indexing MSFN,” that was incorrect — a classic AI hallucination caused by outdated assumptions about how search engines behave. (......) Bing is still returning MSFN pages, but it is not indexing new pages beyond ~2025. (....)."

No, we can't! I'm not saying to take my word for it, I would love for somebody to "trick" Cloudflare. But yeah, ALL SIGNS POINT TO *NO*, it can't be done! My city utilities (sewer and trash) is behind Cloudflare. Like CLOCKWORK, any browser older than a mere TWO MONTHS (just under, actually) can *NOT* be used to pay city utilities. So I've been "experimenting" for the last YEAR (at least). You can *NOT* spoof a UA, you can *NOT* fake Client Hints, you can *NOT* polyfill javascript. I've done a "million" things (exaggerating, but you get the idea). I'm not exactly a "stupid person" (how many people do you know that can FAKE CLIENT HINTS). I'm telling you, IT CAN'T BE DONE. I've been on dozens of sites that are smarter than me and they can't do it either. IT CAN'T BE DONE. The "technology" simply does not exist. Cloudflare is GREAT at what they do. I'm going to keep trying to "break" it. But so far, IT CAN'T BE DONE.

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20260530-40a79c75-uxp-3c23f8ee4e-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20260530-40a79c75-uxp-3c23f8ee4e-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom * Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15. -- New build of HBL-UXP for XP! Test binary: IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20260530-id-656ea98-uxp-3c23f8ee4e-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20260530-id-656ea98-ia-c642e3c-uxp-3c23f8ee4e-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild

@Dietmar Yeeeeeeeeeeeaaaaaaaaaaaa! I patched hal.dll to fix reboot WinXP 64-bit booted on UEFI mode 0x106BB: 7F 0F > 74 24 0x106E1: CC CC CC CC CC CC CC CC CC > B0 06 66 BA F9 0C EE EB FE Tested problematic PC's: Gemini Lake (Dell Wyse 5070), Valleyview SoC (Asus J1800I-C). Now WinXP reboot properly under pure UEFI The patch should work on 95% of PCs, especially Intel ones. @Dietmar Please test reboot on yours Dell Wyse and report. Test also my kdcom.dll patch for WinDbg

upstream backed-out that GC change: https://repo.palemoon.org/MoonchildProductions/UXP/issues/3092

Here’s an alternative take on the situation: The drama behind the scenes: Why Google lost its soul There are three fundamental reasons why Google Search has become so abysmally bad and all our observations are absolutely spot on: Surrendering to SEO spam (the ‘Dead Internet’ theory): The web is inundated with automated, AI-generated pages written solely for the Google algorithm, with the sole aim of selling advertising space. Google has, in effect, lost the arms race against this flood of spam. They’re trying to patch it up with filters (like the latest Core Update), which then leads to total failures where forums like MSFN end up wrongly in the digital gulag. The displacement of the ‘old web’ (Digital Oblivion): The permanent deletion and de-indexing of old content, which has been going on for a long time, is a tragedy. Google is optimising its server costs. Old forum threads, static HTML pages from the 2000s and small private tech blogs are mercilessly kicked out of the index because they don’t generate enough traffic or aren’t ‘mobile-optimised’. This systematically wipes out the collective knowledge of the internet. The compulsion towards ‘synthetic answers’: Google no longer wants to send people to external sites like MSFN. They want them to stay on their site so that you see their adverts. That is why they are trying to summarise everything in AI overviews (SGE). This leads to the actual search index withering away, because it now serves only as fodder for the AI engine, rather than as a guide to real websites.

New build of post-deprecated Serpent/moebius for XP! * Notice: This repo will not be built on regular schedule, and changes are experimental as usual. ** Current moebius patch level should be on par with 52.9, but some security patches can not be applied/ported due to source milestone differences between versions. Test binary: Win32 https://o.rthost.win/basilisk/basilisk55-win32-git-20260620-962fb7e60-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk55-win64-git-20260620-962fb7e60-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - ported from UXP: Issue #2306 - Re-introduce pref for WeakRef API spec. (8eac1db6) (938e5c744) - import from UXP: Issue #2306 - Enable full weakref by default in platform. (0bd0d0a2) (74824f24b) - import from UXP: Issue #3122 - Exclude local resources from <base> CSP checks. (692606e8) (6fc95b735) - ported from UXP: Bug 2029066 - Remove Sinking of Live instructions. (27129430) (e89f0a52f) - import from UXP: Bug 2029765 - avoid refcount over-release in nssTokenObjectCache error path [@ nssToken_Destroy]. (13d87376) (73b5f11e4) - import from UXP: [network] Make keep-alive pref Atomic. (f20e0799) (0d6196afd) - ported from UXP: [DOM] Reject too large mLength in MutableBlobStorage::WriteRunnable. (b60661df) (94d348ce4) - import from UXP: Bug 2023478 - improve handling of escape sequences in pk11uri_ParseAttributes. (7ae6442d) (f277da265) - import from UXP: Bug 2033848 - Use non-default response ID for GTK file picker accept button. r=stransky (81babad1) (1f1e28073) - import from UXP: [DOM] Zero-initialize ThreadSharedFloatArrayBufferList. (5ab14e59) (91d2413a4) - import from UXP: No issue - Use ImmGCPtr for module meta data visits. (0bdcc65c) (456bea8af) - import from UXP: [parser] Better align with spec definition of adding nodes. (a50e1d7a) (1f0c79b3a) - import from UXP: [DOM] Avoid over-optimizing some getter/function calls. (a83b6f74) (94850d8a2) - import from UXP: [gfx] Check more offsets during CFF subsetting. (9a457cbf) (acffb7115) - import from UXP: [network] Make HttpBaseChannel::mLoadFlags atomic. (100f6aaf) (962fb7e60)

Do you mean AV1? https://en.wikipedia.org/wiki/AV1 AVC1: https://en.wikipedia.org/wiki/Advanced_Video_Coding BTW, my latest version of yt-dlp is 2026.06.14

@xper@Tripredacus@Dave-H So basically from what I can see we have 4 problems right now: A forum hack that as a result de-indexed MSFN from search results Spam accounts that lead to registration block Lack of donations to pay for Invision software Lack of maintenance #1 and #2 are the most important ones right now and it may very well be that due to lack of maintenance the forum remained at old software versions which is much worse for servers than it is for client devices. And eventually got hacked. Cleaning the malware is one thing and securing the software so that the vulnerabilities aren't there anymore is another and I think it may actually be easier to just redo the forum board from the ground-up. A fresh board can be brought to life with just a few hours. But I think it's important to keep MSFN alive due to the incredible amount of useful info already there, the fact that there is no forum quite like it: eclipse.cx and legacydev.org suffer from dramas causing a large portion of users not being reachable on one or the other and a lot of the actual software development happens here (especially drivers nowadays). And MSFN is a really active forum for the technical state that it's currently in. Now what IMO has to be done: Archive everything as it is Put up a fresh install of a free forum software like phpBB Transfer users (with more than 0 posts) and emails so that they can redo their password using email verification on the new board Strip the old forum of any javascript/php code to clear malware and put it in read only mode somewhere like archived.msfn.org Maybe transfer the contents of some of the most active topics. Consider giving some maintenance access to most trusted forum admins so that the software gets properly updated And there you go, it requires some work, but problems solved, if a change like this happens I promise to donate to the forum and I'm sure many users would do the same, I think they just don't really want to donate right now due to lack of maintenance happening anyway. And phpBB unlike invision is free!

Everything I reported earlier is already old news. The error has been back in full force for almost a week now. Views are no longer being counted at all. For example:

Yessssssssssssaaaaaaaaaaaaaahhhh after about next 500h of work and about 1000 not working drivers, I get the driver for the Wlan 9560 on the gemini chipset with j4105 cpu to run. It is a pure polling driver, based on OpenBSD 79. The step for to bring the firmware to alive=1 I managed only with Ubuntu. Crazy, 10 different rings for TX and RX and management data. Again I was one step away from to give up Dietmar

you need sending proper Referer header or you will get a cloudflare's captcha page.

@nicolaasjan I'm currently trying to figure out why nothing is showing up with MojeekBot or Bravebot. It seems, however, that the malicious script or code on the MSFN server wherever it may be hiding isn't playing nice with Mojeek or Brave. And that is most likely why Mojeek and Brave don't really have any issues with MSFN at the moment. But maybe, the hackers will update their malware at some point, and then that will be the end of those two search engines, too, when it comes to search results regarding MSFN. And as things stand right now, they have all the time in the world, since the administrator @xper or supervisor @Tripredacus hasn't taken any action yet.

Ok, I’m now in a position to pinpoint the error, bug or whatever setting has been set. After two days of zero views, today there’s a number other than zero: 55 replies and 694 views: It seems to be the case that the forum software counts views of posts only periodically. Of course, this is just a theory that has yet to be proven. I hope this might be helpful.

AGREED. But remember, not all Cloudflare capcha's are "identical". The one for my city utilites goes into an ENDLESS LOOP for SUPERMIUM v144, Chrome v144, and Chromium v144. But yet that is the "newest" we have for SUPERMIUM. Supermium CAN pass the Cloudflare capcha offered up by BING if I want an AI-generated javascript kick-in-the-right-direction. But it can NOT pass the Cloudflare capcha to pay my city utilities.

And here is another example to demonstrate what Google has done with their index: For years, the ProxHTTPSProxy and HTTPSProxy thread has ranked number 1 in Google for the search term "httpsproxy windows xp", as it still does for Mojeek and Brave only at the moment. Zero results which means Google doesn't even know me anymore and technical knowledge is withheld from users of this search engine. To hell with Google Search! Complete de-indexing, as with everything else. Just an example!

@Dietmar Yeeeeeeeaaaa! I patched kdcom.dll source code for Gemini Lake and compile from scratch Maybe now COM1 port will work on Dell for WinDbg

And now back to New Moon and Serpent. I’ve removed all search engines and installed Brave as well as Mojeek instead. Brave is now my default search engine, and its AI can be disabled in the Brave settings. This is particularly ideal for older hardware, as it makes the search engine much more responsive and faster.

Notice: a 5-yearly electricity equipment check is re-scheduled in 03 June 2026 (10:00-16:00 UTC+8). Download server is unavailable during the period. And just in case machine can't automatically power-up after this outage it may be needed waiting me to go to the site to troubleshoot so the outage ending time may be postponed due to this.