Restart manager

[GeoMaL]

Hi all,

My name is George.

This thread is dedicated to "Restart manager" extension for Pale Moon.

If you are interested, you can find it in Pale Moon's add-ons site, here:
https://addons.palemoon.org/addon/restart-manager/

Here, you can discuss everything related to this extension, such as reporting bugs
or glitches, express ideas, make suggestions.

Happy restarting..!

[GeoMaL]

I have a new version almost ready to be released, currently under final testing.

Because of some new features i have implemented, it needs updates to its included locales.
I would not like to publish it with a mixture of English and whatever other language.
There are only a few strings to be translated.

If you find it a bit useful and wish to contribute in its localization, you are more than
welcome to take action!

This is the place on CrowdIn i created for this purpose:
[https://crowdin.com/project/restart-manager

[Nightbird]

Restart manager 2.04 is not compatible with the last unstable 29.0.0a1 (2019-12-18) and has been automatically disabled.

https://github.com/MoonchildProductions ... its/master

[New Tobin Paradigm]

strictCompatibility is strict.

[Nightbird]

Thanks for the tip.
I modified the max version.

[GeoMaL]

I will publish a new version in a few days, because currently i'm working
on some changes.
"strictCompatibility" should be mandatory applied by default in all extensions
especially of this kind.
This is because in case of a real incompatibility, they may cause severe issues
to the browser, even permanent personal data loss.

[New Tobin Paradigm]

I can't agree more but if we disable compatibileByDefault there will be a literal riot of people accusing us of "breaking their Pale Moon" and how "Pale Moon is ruined" and how "it is happening all over again" because "we are just like Mozilla".

You have already seen people go nuts because themes are always strictCompatibility and the current count of extensions using strictCompatibility such as yours and that is JUST a small taste of what would happen.

I shit you not it would be even worse with dozens of threads, ragequits, and attacks. Then others will stay on 28.x for months to years. Not to mention the "Old and Insecure" crowed will seize on it and make another big push against us.

So as long as we accept Firefox extensions for installation we will have to keep compatibleByDefault on all extensions that do not specify strictCompatibility.

I predict, because it has happened before, there will be one anyway because with the 29 version number comes a new issue in that some Firefox extensions are going to malfunction. Specifically those that have but aren't exclusively compatible with Australis that conditionally check appVersion for which codepath to branch off into.

Remember Firefox 29 was Australis and because they are unmodified unforked Firefox extensions expecting things based on the version number.. They are gonna bust in spectacular ways because Pale Moon is not Firefox and never will be again.

So looking forward to that.

[moonbat]

Many extensions are orphaned as opposed to abandoned - their developer contact info is out of date, or (as happened with LiveClick), sending an email didn't elicit a response. So sans permission we can only locally hack them to work but can't distribute the forked version.

[Moonchild]

Many extensions are orphaned as opposed to abandoned - their developer contact info is out of date, or (as happened with LiveClick), sending an email didn't elicit a response.

That is abandoned, moonbat. Abandoned as in the developer packed up and left without a word.

Orphaned extensions would be better, that is extensions where the developer has made a statement they are no longer going to develop it and are basically handing it over to the OSS community for someone else to pick up. Orphaned extensions have clarity about their state.

[moonbat]

Ah, so I interchanged the terms. Such a shame though
If you recall I made a post asking about forking Liveclick after fixing the bug where it wouldn't open the preferences window. I have the fixed version running locally, but the developer never responded to the mail I sent at the provided address - so does this mean the extension is in some kind of legal limbo - i.e. one can share the patch fix but not the modified extension itself due to licensing issues/lack of explicit permission from an AWOL developer?

[Lootyhoof]

does this mean the extension is in some kind of legal limbo - i.e. one can share the patch fix but not the modified extension itself due to licensing issues/lack of explicit permission from an AWOL developer?

Off-topic:
According to CAA and the Internet Archive, LiveClick was released under MPL 1.1, so you're free to fork it provided you rebrand it and otherwise abide by that license. It's probably recommended to upgrade the license to MPL 2.0 if you do though; any MPL 1.1 project can be upgraded to 2.0 without issue.

[New Tobin Paradigm]

Not everything mpl 1.1 can be upgraded to 2.0. There are a few restrictions on that actually but even as 1.1 it can be properly forked.

[back2themoon]

Restart manager has been updated for Pale Moon 31 compatibility (version 2.09).