Please add an "outdated" tag to Decentraleyes

[Andrew Herbert]

The Decentraleyes add-on is out-of-date to its Firefox counterpart, and as such, has critical problems that will not be solved:

https://git.synz.io/Synzvato/decentraleyes/issues/190

https://git.synz.io/Synzvato/decentraleyes/issues/211

Tracking protection add-ons are the ones that most need to be up-to-date, therefore it's imperative to add an "outdated" tag in order not to let users have a false sense of security. The last update date isn't enough, since users don't expect specific add-ons for Pale Moon by official developers to be outdated, as opposed to ones from the Classic Add-Ons Archive or even ones ported by unofficial developers.

[Lootyhoof]

Perhaps you should check with the developer before assuming it is outdated because it hasn't been updated in an arbitrary amount of time. Version numbers mean nothing in this scenario given the different codebases (XUL vs WebExtension).

[moonbat]

Perhaps you should check with the developer before assuming it is outdated because it hasn't been updated in an arbitrary amount of time.

The 2 issues he linked to both ask the developer this question and both were closed without any further reply - and are over 2 years old.

[adesh]

both were closed without any further reply

There is a reply:

> Will there be any further updates [...] for Pale Moon [...] If not, is it safe to [...] use 1.3.10?

Yes. It is absolutely safe to continue to use version 1.3.10, and the Pale Moon compatible codebase will receive maintenance updates, as well as library bundle additions, for as long as absolutely possible.

https://git.synz.io/Synzvato/decentrale ... #note_3380

[New Tobin Paradigm]

During the latter years of Firefox extensions at least half the extension updates for all actively maintained extensions were version bumps and compatibility fixes. Since we don't tend to obsessively refactor and bust stuff constantly the bulk of Pale Moon extension updates are for bug fixes and new features with compatibility updates being rare.

So if we haven't specifically changed something that would bust an extension and that extension is rather feature complete then newer versions aren't being produced by developers unless they need to be. It depends more on their development plan and need than us driving them through constant version bumps and bustages.

This is how it was in the days before Mozilla lost their god damned minds and of course the purges.