#Waterfox classic theme update#
#Waterfox classic theme portable#
#Waterfox classic theme code#
#Waterfox classic theme download#

The end result is you’re teetering on the edge of obsolescence, dying a slow death as you become a browser frozen in time in a world wide web that is constantly moving forward. Mozilla could disappear tomorrow and Pale Moon would still continue as normal. It is no longer accurate to say the same about Pale Moon and hasn’t been for many, many years now. Waterfox Classic is basically old Firefox. If anything Pale Moon is MORE secure than Firefox. It is simply mind-boggling how so many believe Pale Moon to be not as secure as Firefox despite the fact that the overwhelming majority of Firefox security flaws simply don’t affect Pale Moon to begin with.

#Waterfox classic theme code#

The larger the code base the harder it is to secure, or in other words, the more things that can go wrong, the more things will go wrong. Pale Moon has no such difficulties adapting relevant security issues, and if you peruse the release notes, you will notice that the majority of Firefox security issues are “not applicable” to Pale Moon. This is the problem with not being an actual hard fork of Firefox. Now You: Do you use Waterfox Classic or G4? It doesn't mention what the new options are, when I compared it to the previous release the only change that I could see is that Waterfox G4.0.2's Standard protection will block Cross-site cookies in Private Windows. The release notes for the new version states that there are some new preferences in about:preferences#privacy.

#Waterfox classic theme update#

The update introduces the Waterfox Classic theme, Australis. On a sidenote, Waterfox G4.0.2 has been released.

#Waterfox classic theme portable#

The portable version of Watefox Classic has not been updated since April this year, let's see if things change with the new project.

Now, the announcement does not mention the availability of an update, Waterfox Classic's previous update was released on October 13th. Hopefully we will see other contributors chipping in to the project to ease the burden. Kontos has done a commendable job in maintaining Waterfox for over 10 years, and it can't be easy to work on two projects at the same time. That is not a very reassuring message, although it is quite understandable and the transparency is appreciated.

Waterfox Classic will warn the user that the browser could be vulnerable to multiple security issues, and it is up to the user to decide whether to proceed to user it or not. These changes are expected to go live this week.

#Waterfox classic theme download#

The announcement also says that Waterfox Classic will have its own page on the official site, this is something which has bothered some users, as the lone mention of it, has been the link to the releases page, from which you can download the browser. A list of unpatched security issues will be made available on the browser's website. The developer says that Waterfox Classic's future will rely on contributions, by which he probably means what he previously mentioned, about porting security fixes from Firefox ESR. And since it is no longer tied with G4, issues won't be closed because of complications/incompatibilities with the modern version. Now that Waterfox Classic has its own Github repository, users will be able to track and report issues related specifically to it. But more importantly, this will improve the development process of the browser, because previously, issues related to both versions were tackled together. Firstly, users who relied on it will get new versions. This is a welcome move for multiple reasons. The developer cites that it has been difficult to keep the browser up to date with the main project, which is why the two variants have been diverged. Kontos has confirmed that Waterfox Classic will continue to be supported, but it will exist as a separate open-source project from Waterfox G4. Waterfox Classic development will continue No wonder users started worrying, but if you were among them, you can rest assured that it is still being worked on. He had mentioned that its future depended on the ease of porting security fixes from Firefox ESR. Alex Kontos, the developer of the popular Firefox fork, had previously hinted that the Waterfox Classic version was not a priority.