Jump to content

Recommended Posts

Posted

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

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

Repo changes:
- import from UXP: Issue #2686 - Don't rely on return value of ExecutionContext::Compile when the context may forbid running scripts (0590764f) (36eaeed46)
- import from UXP: Issue #2688 - Don't apply auto min-sizing when flex max-sizing. (0849deea) (1f720079b)
- import from `custom` branch of UXP: Update eTLD list (PSL) (064d8757) (762691794)


Posted

@roytam1 I have a Visual C++ 2013 update 4 build of your New Moon 27.10.0 20241220 build, taken from the palemoon27-master branch in your repository. Previously, you had merged Arctic-Fox commits into your palemoon27 repository, and "squashed" them so that all the Arctic-Fox commits you merged will appear as 1 commit. If I have the source code to palemoon27-master, and the Arctic-Fox-master git information (presently at version 45.2 from January 6th 2025), what git command do you recommend I use in order to merge commits from Arctic-Fox (I only know git cherry-pick)? Also, I asked you if you could create a VC2015 branch in your palemoon27 repository, and see if you could merge the latest Arctic-Fox commits to that branch. I finally decided to try a VC2015 build of New Moon 27.10.0 20241220, and it failed 8 minutes in with errors in the type_traits file built into Visual C++ 2015, but when I tried a VC2013 build, it compiled cleanly taking 76 minutes. That means creating a "VC2015" branch for the purpose of evading Visual C++ 2013 compatibility is not necessary in my opinion, but a "tracking" branch that is not meant to be compiled but merged to may be helpful to determine if merging commits from Arctic-Fox will still work (I'm scared of git). 

Posted
On 1/29/2025 at 9:56 AM, basilisk-dev said:

Pale Moon was always intended to be a browser that was utilized newer CPU optimizations to increase performance.

I have a great deal of appreciation and respect for what Moonchild, MCP, and you have accomplished with PM, Basilisk, and the UXP platform, but, "always?"

I think the word "originally" would be more accurate. I first downloaded and used PM back in the early 2000's when I was still using Windows 98. At that time, PM was basically just a clone of Firefox, but compiled for better performance; much appreciated on that old 733 MHz Pentium machine.

But PM and Basilisk (and @roytam1's versions of those) have gotten quite a bit away from just being Firefox compiled with better optimizations. Today, folks (including me) turn to them for many good reasons, but I daresay no one uses them nowadays because they want a higher-performance FF clone!

On 1/29/2025 at 9:56 AM, basilisk-dev said:

Your claim that it was done with the explicit intention of [not] running on older CPUs is false, although that is an unfortunate side effect of enabling the AVX instruction set.... There is absolutely a noticeable performance improvement when comparing the AVX builds to the pre-AVX builds.

The words in bold are doing a lot of work there. In fact, I believe that not running on older CPUs was a strong implicit motivation, as opposed to an explicitly stated reason, for the change.

I chose the word "noticeable" poorly when I said "... not to give PM a noticeable performance improvement on newer 64-bit processors that do support AVX instructions." Perhaps I should have said "significant," as the meaning I wanted to convey was "enough performance improvement to turn the use of PM on Javascript-laden sites from a painfully slow experience into a reasonably responsive one."

Posted
On 1/26/2025 at 4:16 PM, modnar said:

Is there any option AVIF format would be added to Serpent - apparently it's there to lower the size of images (better compression).

I wonder if this could be done with a plug-in? I realize that NPAPI plug-ins are considered passe and aren't supported by more modern browsers, but UXP still supports them; if it would work it would be a perfect way to add support for new image compression formats without having to add bloat to the browser itself.

On 1/26/2025 at 8:33 PM, Leokids123 said:

AVIF isn't supported on Pale Moon cause they claim it falls technically short on all important areas.....

They may be right; I don't know. But that's a question for Web sites to consider, not for browser developers like MCP!

The question for MCP should be, are there enough Web sites using AVIF that lack of support is a barrier to using PM? If not, don't spend time on it; there are other areas that need more attention. But if there are, then MCP needs to support it, even if it's crappy; or PM will lose even more users.

MCP is not Google! (Thank goodness!) They can't kill something they don't like by refusing to support it; they can only hurt themselves.

Posted
9 hours ago, Nicholas McAnespy said:

@roytam1 I have a Visual C++ 2013 update 4 build of your New Moon 27.10.0 20241220 build, taken from the palemoon27-master branch in your repository. Previously, you had merged Arctic-Fox commits into your palemoon27 repository, and "squashed" them so that all the Arctic-Fox commits you merged will appear as 1 commit. If I have the source code to palemoon27-master, and the Arctic-Fox-master git information (presently at version 45.2 from January 6th 2025), what git command do you recommend I use in order to merge commits from Arctic-Fox (I only know git cherry-pick)? Also, I asked you if you could create a VC2015 branch in your palemoon27 repository, and see if you could merge the latest Arctic-Fox commits to that branch. I finally decided to try a VC2015 build of New Moon 27.10.0 20241220, and it failed 8 minutes in with errors in the type_traits file built into Visual C++ 2015, but when I tried a VC2013 build, it compiled cleanly taking 76 minutes. That means creating a "VC2015" branch for the purpose of evading Visual C++ 2013 compatibility is not necessary in my opinion, but a "tracking" branch that is not meant to be compiled but merged to may be helpful to determine if merging commits from Arctic-Fox will still work (I'm scared of git). 

better try compiling directly from rmottola's AF dev branch first, you may just fork it and create a new branch for your changes.

I do have a winbuild branch of AF to merge upstream's dev branch changes.

and my changes in my repo comes from upstream's dev branch changes and my winbuild branch changes squashed with `git diff oldrev..newrev` and apply it in my NM27 master branch(also needs fixing since my master branch doesn't very winbuild branch alike).

but these nightmares are long-gone for me as it doesn't fit my needs now.

Posted

Basilisk52 win64

It was quiet for a few months and recently https://www.elektroda.pl
started to randomly report a connection problem again.
One goes to the site and at first everything works,
only after one clicks on more links,
more messages on the forum page, it can report a connection error:

Secure Connection Failed
The connection to www.elektroda.pl was interrupted while the page was loading.

After refreshing the page, the page loads until the next error in a few minutes, where the next link and again need to refresh to get the page to load after the error.

Posted (edited)

ATTENTION. Cloudflare security check stopped working in New Moon and Serpent in January. I checked in Chrome - there it's working.

Example: https://www.y2mate.com/youtube/oZaDX7cgJEo

Press download green button and see how Cloudflare check looping endlessly. Roytam1, please, can you fix it?

Serpent even crashed during that check.

Edit: Ok. i noticed that New Moon crashes too, so i searched "Cloudflare" on Pale Moon forum and this is what i find:

Pale Moon people are well aware of that issues and situation so far not resolved

Cloudflare Verification Loop issues

Cloudflare has decided to crash Pale Moon

It's hard to believe in such levels of incompetence, probably Google and Cloudflare trying to destroy alternative browsers. At this point it safely to say that no company did not made more damage to internet as Google. They really go from "don't be evil" to "just be evil as f***".

This monopolies can be defeated only by Superstates like USA and EU. But considering what happening last month in USA i must say it look disappointing.

Edited by Rod Steel
Posted
10 hours ago, Rod Steel said:

ATTENTION. Cloudflare security check stopped working in New Moon and Serpent in January. I checked in Chrome - there it's working.

Example: https://www.y2mate.com/youtube/oZaDX7cgJEo

Press download green button and see how Cloudflare check looping endlessly. Roytam1, please, can you fix it?

Serpent even crashed during that check.

Edit: Ok. i noticed that New Moon crashes too, so i searched "Cloudflare" on Pale Moon forum and this is what i find:

Pale Moon people are well aware of that issues and situation so far not resolved

Cloudflare Verification Loop issues

Cloudflare has decided to crash Pale Moon

It's hard to believe in such levels of incompetence, probably Google and Cloudflare trying to destroy alternative browsers. At this point it safely to say that no company did not made more damage to internet as Google. They really go from "don't be evil" to "just be evil as f***".

This monopolies can be defeated only by Superstates like USA and EU. But considering what happening last month in USA i must say it look disappointing.

the crash is fixed in both sides, but the challenge is not fixed yet.

Posted
I just came to confirm/report the Cloudflare captcha issue that I started to have since yesterday.

I sent them feedback (as it worths something...)

Thanks whenever you can fix it.

Or Palemoon guys can do something. It is a shame that is happening to the latest "Pale" too :S

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...