Leaderboard

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

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.

False Google search is better than IPS, especially due to dorks. That’s completely irrelevant at the moment. MSFN articles or threads can’t be found on Google anyway. MSFN has been banished to the digital gulag as an alleged spammer.

What’s really going completely wrong at the moment is the lack of an official statement from the forum owner or administrator regarding this whole mess. You can’t just sit this out or ignore it.

All searches worked fine during that days, no "redirects". So it's closely related to @D.Draker's absence. MSFN lost its juice and spiciness without @D.Draker. People from my Uni came here in thousands just to read him! Don't get me wrong, I love @AstroSkipper, I also read @Dave-H, love their language and manners.... but without D.D. it just isn't what it used to be! To me, it looks like someone forced him out of the forum, thus killing off MSFN. My opinion, do what you want with it. BTW, a lot of people think this way, read the memeorandum at his account.

Any server or forum can be hacked. But the fact that Google has de-indexed a renowned technology forum and consigned it to the digital gulag is the ultimate admission of failure, the definitive proof that Google is no longer in control of its own mess and blindly trusts its algorithms and AI. Nevertheless, the operator of MSFN, @xper, also has a responsibility to carry out regular malware scans and install important security updates. In any case, Brave and Mojeek prove that, with the right filters, the problem can also be brought under control on the part of search engine operators. I have been a member of this forum since 2010, and even before that, as a non-member, I kept an eye on the MSFN forum. I have never before experienced or witnessed anything like what is happening now. It is a disgrace. The operator @xper, the administrator @Tripredacus and all members of MSFN must stand up to counter this undesirable development.

If I do a Google site search with msfn.org then I get a bunch of adulterated search results. That is, some (but not all) of the search results appear in the Thai language. Which is interesting because it suggests Google's own web crawler/scraper has been persuaded to read a different web page. However, if I follow one of the links I always arrive in the correct place. I am never redirected. This is using standard Serpent and quad9 dns (9.9.9.9). I did briefly try Google's dns (8.8.8.8) but it made no difference. So, the only place I see any evidence of the hack is within Google's search results. I haven't found a way to actually arrive on one of the Thai pages. I haven't even been able to find the domain – so, kind of a useless hack really. Ben.

When hover over them with cursor, the links look legit, but the results shown in that Alien language. Look at the bottom, please.

Google, Bing, and all search engines based on them do not show any real links to MSFN. They removed all relevant links from their index starting from 21.05.2026 with their latest Core Update. Only two major search engines show correct links to MSFN, one is Brave and the other Mojeek. I'm really curious to see what the owner or administrator @xper of MSFN will do about it.

Your view of things is extremely superficial and lacks the necessary depth. Your analysis is a perfect reflection of the prevailing trend in your circles. You’d be better off asking yourself where Google, Microsoft and the SEO industry are based. That would get us to the bottom of the matter much more quickly. And rubbish simply generates more rubbish. But why am I telling you this? You must know that far better than I do.

With current defaults memory consumption by the basilisk.exe will go to even north of 1600K (which never went before) and CPU constantly at 25% (one whole core occupied) and browser completely unresponsive. I have observed that setting javascript.options.gc_on_memory_pressure to true ameliorates the memory problem (memory consumption stays at around 1000K), but no the CPU-one (I tried different settings, but haven't found one that worked). P.S.: This memory saving setting (javascript.options.gc_on_memory_pressure) is "true" by default in newer firefox versions (or so I have read).

The issue at hand goes far beyond MSFN. In my article I have shared some in-depth insider knowledge and outlined the reasons behind Google’s total decline. And Google is dragging most search engines down with it. From now on, we can remove the term ‘to google’ and, in my native language existing for 30 years, 'googeln' from our vocabulary, unless you’re into adverts and misinformation. MSFN is just one of many to suffer the consequences. If it were just a question of spam, there would be hardly any websites left to visit. It's all about money and power. That's something you should know well from your boss.

Microsoft's Bing is just as bad as Google, and DuckDuckGo is dependent on Google because it uses its data and therefore no longer usable. You don’t seem to have fully grasped the implications. Google, Bing, Startpage, Ecosia, DuckDuckGo, etc. have thus become useless. This is also about search engines under New Moon 28 and Serpent 52. If that isn’t important, then I don’t know what is important at all. As far as I’m concerned, all these search engines are dead and are now just history. You're worried about your CPU spikes when using the most recent version of New Moon 28. But just think about what browsers were created for! The main function of browsers is to access websites, which must first be found by search engines if you don’t know their address. That’s what I do most of the time with @roytam1’s browsers, such as New Moon or Serpent. And I do it on a real installation of Windows XP.

Once again. There is no SuperStop for New Moon 28. You have to create a script with same functionality or combine different, already existing methods via extensions, custom buttons, scripts or CSS stylesheets to get a similar effect. One of them is ToggleGifAnimations. I made a little research.In fact, there is an earlier legacy version of SuperStop by the same author which therefore can be installed in New Moon 28. But it’s rather poor. It only uses the browser’s built-in BrowserStop() function, which merely stops the current tab from loading. This version, SuperStop 0.1, can be found in the Classic Add-ons Archive (caa). But, as I said, it can only do a fraction of what the later webextension, SuperStop 0.6, does, which stops active WebSocket connections, JS timers, XMLHttpRequests, and any animated images and videos.

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.

Ok. Memory Fox 1.0 is a webextension and not a legacy one. That explains a lot. Therefore, it won't work in New Moon 28. I had a look inside the XPI file, and the popup.js is a script for discarding tabs. No more, no less. In case you are running Serpent 52 in single-process mode, it can't really help. Real tab discarding is only possible if running the browser in multi-process mode.

Have a look at my "results":

I didn't refer to AI search results. Have a look at the standard search results. Try, for example, 'MSFN Windows XP'! Google officially began rolling out the May 2026 Core Update yesterday (21 May 2026). And that’s exactly where the problem lies! Maybe, in Europe or Germany first! The search results are simply crap.

Did anyone try to search MSFN threads via Google Search since yesterday? Doesn't matter whether you do it in New Moon or Serpent or any other browsers. You’ll be really surprised. Just type in ‘MSFN’ as your search term! From now on, I won't use anymore Google Search in my browsers as the main search engine. I've had enough of Googling for now.

@exogenesis Did you really read my last articles carefully? I don't think so. Here is my comment about the legacy custom buttons and what I am doing at the moment: Please note the underlined sentences! And BTW, here is no package of custom buttons or whatever it is you're on about. Since the beginning of 2025, I am a UC.JS script programmer. I develop scripts for use in Mypal 78, Serpent 52 and New Moon 28. And to say it again clearly, custom buttons and its extension is history for me. SuperStop is not a custom button but a webextension. You can get it here: https://addons.mozilla.org/en-US/firefox/addon/superstop/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=search If you're still interested in the old custom buttons and you want to stop all GIF animations, then have a look at my article:

they also checked-in lots of other things, bug parallelized GC and FinalizationRegistry may cause browser strugglish and/or crashy. EDIT: decided to back-out FinalizationRegistry here, GC-on-close-tab was backed out as well.

Your obsession sounds like a mental health issue. Seek help.

They have been hacked before, they will be hacked again. Granted, first article I found is from a year ago, with Google ADMITTING that their DNS was hijacked. All it takes is a temporary hijack and YOUR CONFIG'S DNS CACHE to keep the "redirect" active forever (or until that cache is flushed) on YOUR CONFIG. https://umatechnology.org/googles-public-dns-servers-hijacked-traffic-redirected-for-more-than-22-minutes/

That was nearly a year ago. I'm now using Supermium 138, which spoofs itself as 142, by design, but is definitely actually 138. It's certainly no older than that, and I never accepted the claim that the Supermium developer was deliberately falsifying the Chromium version it was using. I have never had any redirection issues with MSFN.

Please stop being "combative". It feels like you are trying to "start a fight". Why? The "impatience" I can live with. If this is "combative" in nature, the moderators can keep track of how often that is the case.