Leaderboard

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 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.

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.

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.

most suspected code that may cause this is GC related one. https://repo.palemoon.org/MoonchildProductions/UXP/pulls/3093

UC.JS Programming Given the feedback – or rather the lack of it – I assume that either nobody in New Moon or Serpent is using UC.JS/UC.XUL scripts, or that there is a massive lack of interest in this topic , or simply the usual passivity. What is so special about UC.JS/UC.XUL scripts in these two browsers? If you search for such scripts online, you’ll find that most were created for newer versions of Firefox, i.e. Firefox 57+ or even Firefox 68+. And the situation is just as dire when it comes to compatible script loaders. If you’re now thinking, ‘But there is an extension called userChromeJS in the form of an XPI file’, then you’re right. But the latest version, 2.0, dates from 2010 and is far too old to load all modern scripts, meaning the functionality of this loader in New Moon or Serpent is rather limited. It was adequate back then, but no longer in this day and age. Most users install a varying number of extensions to add missing features. There are still a few current and well-maintained ones, but most are ancient, no longer developed versions. They generate numerous error messages, no longer function fully, consume resources and, in the worst case, cause incompatibilities. I’ve left all that behind me. The loader I use, which has been additionally patched by me, is much more up to date. It is implemented in exactly the same way as in Mypal 78. So no longer in the form of an extension. UC.JS/UC.XUL scripts consume significantly fewer resources and can provide precisely the functionality required without installing any extra bloatware. And their access via the browser is virtually unlimited. What are the specific challenges involved in creating UC.JS/UC.XUL scripts in New Moon or Serpent? Although Serpent 52 is also based on the very old Firefox version 52, it is nevertheless considerably more modern than New Moon 28. This browser already features the excellent CustomizableUI interface. At the time, Moonchild Productions decided not to integrate the CustomizableUI interface, introduced in Firefox 29+, into Pale Moon. Consequently, all widgets and toolbar buttons from UC.JS scripts in New Moon 28 must be created differently, i.e. in a completely basic, ‘old-school’ manner. This is a major problem. Such buttons are injected into the DOM very late by the script loader and are then regarded as foreign by the browser. They are not really managed by it. Therefore, the developer of UC.JS scripts must also take care of this. In Serpent 52, this is much easier, as CustomizableUI is fully present, albeit not up to date. Furthermore, of course, some things always need to be adapted specifically for each browser. Scripts that work in Mypal 68/74/78 usually do not run in Serpent 52 or, quite possibly, in New Moon 28. And the scripts in Serpent 52 do not run straight away in New Moon 28 either, for a variety of reasons. I’ve now overcome every obstacle. Since early 2025, I’ve single-handedly written countless scripts for Mypal 68/74/78, and ported them first to Serpent 52 and then even to New Moon 28. My script loader, all my scripts and even the extensions I use no longer produce a single error in the browser console. To achieve this, I had to fix a few extensions that haven’t been maintained for a long time, such as Violentmonkey, Navigation Bar Enhancer and Toolbar Buttons. I have now expanded my one man team to include an AI that I have trained specifically for this purpose. All this means that you can use UC.JS and even UC.XUL scripts in New Moon or Serpent just as you would in, for example, Mypal 78. So, that was my first report on this topic. Enjoy reading!

This is what I get when I search for the whole domain. The site is now completely shadowbanned!

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20260523-40a79c75-uxp-829418a939-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20260523-40a79c75-uxp-829418a939-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-20260523-id-656ea98-uxp-829418a939-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20260523-id-656ea98-ia-c642e3c-uxp-829418a939-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild

Oh man, you can’t seriously be saying that in your right mind, can you? Google Search has been a complete disaster for ages. And I’m sick of hearing that rubbish about ‘for your own safety or for your protection’. It’s the daftest excuse ever and one of the reasons why everything’s going down the drain.

I agree TODAY. But this is actually NEW news. A week ago when I posted that, you **COULD** do a Google search for "MSFN Windows XP" and you **DID** get MSFN results. That is no longer true. As you have noted in another thread. But again, this is NEW news that was not true a week ago. A week ago, I did a search for "MSFN Start Is Back" and the Google results listed MSFN as the #1 result for that query. That is not true "today".

You are completely wrong. MSFN members won't search threads of their forum via Google, of course. But that’s only logical and isn’t the issue at all. The point is that non-members will no longer be able to find content posted on MSFN. MSFN will no longer reach people who are looking for answers via Google. No new visitors, less traffic, and a descent into obscurity for all Google slaves, who, tragically, use nothing else because intellectual laziness has become the norm everywhere.

And now it’s crystal clear where this is heading if other search engines rely solely on Google. Startpage, Ecosia and many, many others no longer recognise MSFN either. It’s a complete disaster. Monopolies are the death of everything. My compliments to Mojeek and Brave. They are now my main search engines in New Moon, Serpent and Mypal.

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.

Thanks for the link! I have never observed this crap before. Google and Microsoft are unfortunately dominating the market. They are togetther monopolists destroying the idea of free infornation. So, the users have to understand that and say bye, bye to them. I personally start to use Mojeek and Brave Search. I've had absolutely had enough of this rubbish. .That aside, the quality of Google’s search results declined steadily. Even the exact phrase was no longer taken into account. The results increasingly consisted of irrelevant rubbish that had absolutely nothing to do with the search query.

Conclusio: At the moment, MSFN is no longer listed on Google. Their index has been destroyed. Bye, bye Google!

And here the same search string in Mojeek: Looks a little different, doesn't it?

I can confirm that, and more than that. However, I can't confirm that. They are easy to handle and can be directly modified at any time. I additionally use a UC.JS/UC.XUL script manager to get full control of them and to activate or deactivate them if desired. You always see the starting order when it is of the utmost importance. At the moment, I am running 20 UC.JS/UC.XUL scripts in New Moon 28 as well in Serpent 52 without any errors. Most of them are ports from scripts I originally created for Mypal 68/74/78 and indeed self-created from scratch. You can use these scripts to retrofit almost anything with pinpoint accuracy. Retrofitting all of this with extensions is far more labour-intensive and would consume an much larger amount of resources. In any case, my browsers are in perfect condition, so to speak.