Pale Moon forum

Moonchild wrote: ↑

2021-02-09, 23:32

Which, by the way, will also NOT have their beloved unported and unmaintained extension.

Other browsers have up-to-date extensions, developed by developers, and do not need to use MTT counterparts.

Moonchild wrote: ↑

2021-02-09, 23:32

meaning they were using MTT while they should not.

Many people used MTT because they could not find a working XUL extension.

palem wrote: ↑

2021-02-09, 23:57

Other browsers have up-to-date extensions, developed by developers, and do not need to use MTT counterparts.

So you're telling me that someone currently using MTT to run an old and obsolete "legacy" Firefox extension will find that same extension in other current browsers?

palem wrote: ↑

2021-02-09, 23:21

So they will have to look for another browser.

Just use Basilisk and quit complaining if what you want is a browser eternally frozen in time with minimal UI changes. Basilisk visually is Firefox 52 minus web extensions support running on UXP and purposefully does not change anything other than the internal core that is shared with other UXP applications .

Except while Basilisk's UI doesn't change often mainly because work specifically on the UI is not a high priorty by any means but it is not invulnerable either. It does change if the platform changes require it to and other platform changes that affect extensions are still happening.

So Basilisk is in the exact same situation as Pale Moon except that it still uses its Firefox GUID and advancement of its unique UI and featureset just aren't broadly important enough to bother with unless it needs fixed/changed for changes elsewhere.

Let me lay out what is coming next for Pale Moon et all:

We WILL remove the six year old temporary hack known as the "Dual-GUID System" that bypasses the install check and allows extensions with a Firefox targetApplication to install.

We WILL introduce a new Add-on JSON-based Install Manifest to be the new format going forward for all applications. This will have a similar but not identical data structure to the current RDF-based Install Manifest in order to eliminate long standing issues and quirks of the format. This will be fully documented on DPMO when it lands for testing on trunk/unstable.

We WILL disable the RDF-based Install Manifest processing globally on the platform except for Basilisk and Interlink.

This ALL will not happen at once but will be staggered out across the release cycles only the exact timing is in question. But we will end the year with this long accomplished. So everyone best get out of their little (fire)foxhole and pay attention.

To support this there will be a new fully from scratch new version of the Phoebus Add-ons Site Software written to address and eliminate many issues from its past development which will add whole new fearures and granular controls for developers and their Add-ons including new types and pseudo-types.

The new software will NOT accept submission of new or updated add-ons using the RDF-based Install Manifest. But will continue to serve all it has at that time. I am also considering a one-time automatic conversion of latest versions of all Extensions and Themes to the new JSON-based Install Manifest. We shall see on that.

These ARE the plans for going forward and if we survive them we will ALL be in a better situation. It would be a great shame if after all this work and years of service that we should fail because of lack of vision by the userbase and current/incoming developers. A great shame, indeed.

So you see, Moon Fester Tool will be of little use going forward.

New Tobin Paradigm wrote: ↑

2021-02-10, 05:03

So you see, Moon Fester Tool will be of little use going forward.

Until he comes up with 'convert your FF extension to JSON based manifest so you can keep using them indefinitely' extension

I don't think that will be allowed to fly. But I kinda hope he does. It will be the final nail.

Is anyone else aware that this extension will permanently and materially alter extensions on the fly? Opens them up and rewrites parts of them and saves them?

Additionally, JustOff, This is your public notification: I have removed your little message about the extension being on level 1 blocklist status. Level 1 is only a warning and the only effect on installation is that it is that it needs to be manually enabled. Users do NOT need to change their Security Level Enforcement in Preferences at all to use the extension. Asking them to is irresponsible as hell because lower than level 1 is literally NO SECURITY. So you are asking users to disable the blocklist for the sake of your Firefox Extension hacking and rewriting tool.

Asking users to disable security features for your extension ESPECIALLY when it isn't even needed will NOT be tolerated. I hope you hurry up and get your SHIT off our Add-ons Site as soon as maintenance is complete.