Add-ons • Re: Working on a Greasemonkey fork for Pale Moon

Quick question: Is there someone here that would hate my extension not being 100% faithful to how Greasemonkey should look and act like (Think of the current upstream version of Greasemonkey on Firefox), or do you guys just care about the extension being compatible and effective, no matter how different it'll look like in comparison to the old fork of Greasemonkey (I call Janek's fork old now, since I maintain a modern fork of Greasemonkey)?

Been having some ideas of porting in some features from other userscripts managers, like the import/export feature that behaves like how it behaves on Tampermonkey, possibly do something about the userscript editor of greasemonkey, since a lot of people are expressing their dislike of it.

I have also noticed that the old fork of the extension does not have the import/export mechanism and does not show all userscripts' homepages, unlike Violentmonkey that has 7 levels of fallbacks that would display the homepages of all userscripts - I'm adding both of these 2 features in my fork and it'll be present on the next version of 3.6.0, but I feel like it's not going to help much, since the next version is going to have a different UUID, which means nobody is really going to utilize these 2 features, when it's needed the most.

Should I release a transitional version, where it makes it easier for people to utilize these 2 features under the same UUID, before migrating to 3.6.0 under a different UUID, but they'll be able to bring back all the userscripts that they have been using?