Pale Moon forum

Basilisk 2023.01.26 has been released!

This release uses the same UXP platform version as Pale Moon 32.0.

See the release notes for more information.

See the downloads page to download the update.

Autoupdates will not work from Moonchild Productions releases to Basilisk Development Team releases due to changes in the compression algorithm used for the autoupdate files. You will need to manually perform an update from a Moonchild Productions version of Basilisk to our version. After this one-time manual update autoupdates will work again. Please review the first run page after performing this update for instructions on how to transfer your data from the older Basilisk versions to the current version.

Much thanks, works just fine. Appreciate the update.

N

Would be better if you make a generic release announcement thread and update it each time there's a new version (and lock it until the next release) instead of separate posts, similar to how we get announcements for new Linux builds of PM.

Sorry for cross posting in the old version thread. I would like to know if it's possible to add some cosmetic tweaks:
- a checkbox to enable/disable WebRTC
- a checkbox to enable/disable WASM
- port the Photonic theme to Basilisk.

moonbat wrote: ↑

2023-01-29, 01:45

(and lock it until the next release)

Please no. This is obnoxious. I can't count how many times I've wanted to discuss release notes or specifics of a release only to have to create my own thread on the topic when it should be discussed in the actual announcement thread*. I'm not talking about reporting bugs or anything, just a simple congratulations and thank you. Or requesting clarification about release notes. etc.

There is MUCH too much locking of threads going on in this forum. It is a scourge.
This is mainly a complain about Pale Moon threads, but it doesn't need to spread to Basilisk threads now, too.

*If we insist on locking these release announcement threads, at least make a companion discussion thread and link it in the release post for every one going forward.

My installed version now matches the Help|About dialogue and the release notes link. However, when Basilisk told me there was a new version available, it said Version 0 was available for download. Just a heads up.

Wastelander wrote: ↑

2023-01-29, 11:26

Sorry for cross posting in the old version thread. I would like to know if it's possible to add some cosmetic tweaks:
- a checkbox to enable/disable WebRTC
- a checkbox to enable/disable WASM
- port the Photonic theme to Basilisk.

The checkboxes for WebRTC and WASM are possibilities. I think this may be a good idea. Please open an issue on the Basilisk repo and I will look into it.

As for the Photonic theme, you should get in contact with the author of that theme to add support. There used to be a lot more themes available for Basilisk, but when Basilisk was originally discontinued many themes (and add-ons) dropped support for Basilisk. Even though I've restarted Basilisk development many of these authors have still refused to reinstate Basilisk support.

Figueroa wrote: ↑

2023-01-29, 19:07

However, when Basilisk told me there was a new version available, it said Version 0 was available for download. Just a heads up.

I saw that too on my Windows machine. That doesn't occur on the Linux builds. I'll have to take a look at the XML being returned by the autoupdate server.

moonbat wrote: ↑

2023-01-29, 01:45

Would be better if you make a generic release announcement thread and update it each time there's a new version (and lock it until the next release) instead of separate posts, similar to how we get announcements for new Linux builds of PM.

I have no intention of doing this at this time, but thank you for the suggestion.

In my opinion, not locking the release announcement thread for the current release is not beneficial whatsoever. I do however lock the old release announcement thread when a new release happens so that discussion of the new release can happen in the new thread. If someone needs to discuss something not release-specific (for example a feature request) then that is a situation where it makes sense for the user to create their own thread.

If it gets to the point that there is a lot of spam and irrelevant discussion in the release threads then I will consider doing this, but at the moment I do not feel the method of locking threads that you are suggesting is the best approach.