My Browser Builds (Part 5)

[Goodwin]

On 6/29/2025 at 4:25 PM, roytam1 said:

AI crawlers don't respect robots.txt.

This is a preparatory stage for the introduction of personal identifiers on the network. Do you remember the Microsoft passport that they wanted to introduce back in 2003? They are psychologically preparing the herd (as they perceive people) to avoid mass discontent. I don't believe in kind-hearted individuals who want to make the internet free for nothing. These individuals are either bought off and remain silent, or they divert the masses towards imaginary threats (such as UFOs), concealing real threats in the noise.
For example, such a nuisance suddenly appeared on the last remaining Invidious sites a couple of months ago, and serpent can't pass this test, and I don't want to enable workers or scripts. Previously, these sites could be used without scripts. After introducing such a nuisance, there's no point in maintaining privacy. Alternatively, the owners of the last Invidious sites may have decided to earn extra money by collecting unique browser fingerprints using these protection measures against the dreaded pseudo-AI, which are highly interested in Invidious sites.

[Mathwiz]

17 hours ago, Ben Markson said:

I have a lot more run-ins with Cloudflare than I do Anubis. Both of them can get stuck in an infinite validation loop. Cloudflare can get insanely aggressive, it will quite happily lock your browser into an irretrievable Loop of Death (who would write code like that?). At least Anubis can easily be stopped.

I think the thing I object to the most is that they focus on the way a browser looks rather than what it is actually doing. In civil society this is characterised as profiling rather than being intelligence led.

All that will happen is that the bots will better disguise themselves and their behaviour will go unchecked.

If you take the Anubis explanation (posted above by @VistaLover ) at its word, it seems to make sense. The idea is to make the user agent (browser or bot) do something rather hard, but not too hard; the idea being if you're just an ordinary user, the extra work is just a short delay in getting to the Web page; but if you're a bot crawling millions of pages, that extra work isn't worth the effort so you'll just abort the script after a few milliseconds and move on.

But, then - why insist on "modern" Javascript and why force users to disable their privacy guards? I'm still somewhat skeptical that Anubis was telling us the whole story above.

[Leokids123]

13 hours ago, Mathwiz said:

If you take the Anubis explanation (posted above by @VistaLover ) at its word, it seems to make sense. The idea is to make the user agent (browser or bot) do something rather hard, but not too hard; the idea being if you're just an ordinary user, the extra work is just a short delay in getting to the Web page; but if you're a bot crawling millions of pages, that extra work isn't worth the effort so you'll just abort the script after a few milliseconds and move on.

But, then - why insist on "modern" Javascript and why force users to disable their privacy guards? I'm still somewhat skeptical that Anubis was telling us the whole story above.

I'm assuming "modern" Javascript is ES6+ Those versions of Javascript are fairly recent and supports modern features.

[Mathwiz]

Yes; the page could've been clearer on exactly how "modern" your browser's Javascript needed to be.

At any rate, UXP does seem up to the task, albeit inefficiently. There are many reasons that might have caused me to get the "denied" page, but it wasn't worth the effort to track it down. I was just wondering what kind of nonsense we WWW users have to deal with now, and why. My curiosity is "mostly" satisfied now.

[roytam1]

New build of Serpent/UXP for XP!

Test binary:
Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20250705-3219d2d-uxp-9175504ffc-xpmod.7z
Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20250705-3219d2d-uxp-9175504ffc-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-20250705-3219d2d-uxp-9175504ffc-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-20250705-d849524bd-uxp-9175504ffc-xpmod.7z
Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250705-d849524bd-uxp-9175504ffc-xpmod-ia32.7z
Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250705-d849524bd-uxp-9175504ffc-xpmod-sse.7z
Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250705-d849524bd-uxp-9175504ffc-xpmod.7z
Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250705-d849524bd-uxp-9175504ffc-w7plus-avx2.7z

Official UXP changes picked since my last build:
- Issue #2765 - Follow-up: Make scrollbar width checks use the originating non-NAC style context on Linux and Mac (af84337437)
- Issue #2765 - Follow-up: Fix UAF when returning the non-NAC style context from a frameless node (6e358f1039)
- Issue #2765 - Follow-up: Avoid declaring RefPtr in the return statement (e4630ce481)
- Unprefix -moz-read-write / -moz-read-only (4cc014cb6b)

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

[roytam1]

New build of BOC/UXP for XP!

Test binary:
MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20250705-7bda12e7-uxp-9175504ffc-xpmod.7z
BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20250705-7bda12e7-uxp-9175504ffc-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-20250705-id-656ea98-uxp-9175504ffc-xpmod.7z
IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20250705-id-656ea98-ia-c642e3c-uxp-9175504ffc-xpmod.7z

source repo (excluding UXP):
https://github.com/roytam1/icedove-uxp/tree/winbuild
https://github.com/roytam1/iceape-uxp/tree/winbuild

[roytam1]

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-20250705-e30943041-xpmod.7z
Win64 https://o.rthost.win/basilisk/basilisk55-win64-git-20250705-e30943041-xpmod.7z

repo: https://github.com/roytam1/basilisk55

Repo changes:
- import from UXP: Issue #2765 - Follow-up: Make scrollbar width checks use the originating non-NAC style context on Linux and Mac (af843374) (60255fc16)
- import from UXP: Issue #2765 - Follow-up: Fix UAF when returning the non-NAC style context from a frameless node (6e358f10) (8580d4e5d)
- ported from UXP: Unprefix -moz-read-write / -moz-read-only (4cc014cb) (e30943041)

[Leokids123]

25 minutes ago, roytam1 said:

New build of Serpent/UXP for XP!

Test binary:
Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20250705-3219d2d-uxp-9175504ffc-xpmod.7z
Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20250705-3219d2d-uxp-9175504ffc-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-20250705-3219d2d-uxp-9175504ffc-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-20250705-d849524bd-uxp-9175504ffc-xpmod.7z
Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250705-d849524bd-uxp-9175504ffc-xpmod-ia32.7z
Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250705-d849524bd-uxp-9175504ffc-xpmod-sse.7z
Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250705-d849524bd-uxp-9175504ffc-xpmod.7z
Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250705-d849524bd-uxp-9175504ffc-w7plus-avx2.7z

Official UXP changes picked since my last build:
- Issue #2765 - Follow-up: Make scrollbar width checks use the originating non-NAC style context on Linux and Mac (af84337437)
- Issue #2765 - Follow-up: Fix UAF when returning the non-NAC style context from a frameless node (6e358f1039)
- Issue #2765 - Follow-up: Avoid declaring RefPtr in the return statement (e4630ce481)
- Unprefix -moz-read-write / -moz-read-only (4cc014cb6b)

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

First UXP build of july and yet...

 

Why are you still picking changes,if you can't even access their UXP repo?

[roytam1]

1 minute ago, Leokids123 said:

First UXP build of july and yet...

 

Why are you still picking changes,if you can't even access their UXP repo?

there is a mirror in github, but it has low update count.

[VistaLover]

Out of curiosity, I got myself a HK IP address and then tried to load:

https://repo.palemoon.org/MoonchildProductions/UXP

This is what I got: 

It would be far-fetched to think (would it? ) that MC specifically blocked access to his Gitea instance in Hong Kong, where roytam1 resides, as a means of thwarting further development of the UXP "XP forks", that he so much despises...

In any case, @roytam1 are you behind the GFW in HK? Can you not use a geo-spoofing application (VPN, VPS, DNS, Shadowsocks, etc. ) to acquire, e.g., a European IP address and properly access RPO? 

Worst case scenario, one of "us" here  could send you a tarball of the proper UXP repo, though currently this stands at ca, 252 MB: