- #Firefox 57 addons pale moon software
- #Firefox 57 addons pale moon code
- #Firefox 57 addons pale moon free
The dialogue was sabotaged from the beginning by ibara, not the Pale Moon devs.
Ibara was stupidly and unnecessarily combative right out of the gate (an asshole), to which the lead dev (mattatobin) and IP owner (wolfbeast) responded in kind. That is perfectly reasonable and required by trademark law, to which the contributor (ibara) responds: I will do no such thing until I speak with the person who owns the rights to the intellectual property, which appears to be not you. You must comply with the directive or you must disable official branding for your builds. I will definitely be avoiding pale moon after reading that link.įirst, the link opens with the following line: We do not allow system libs to be used with official branding because it deviates from official configuration. Just be prepared to acknowledge that the information you're responding to is very likely way out of date. That's fine, I respond to old links on occasion, too.
#Firefox 57 addons pale moon code
Copyright is not a factor here, as the code is under the permissive Mozilla licence (which is vastly superior to the viral GPL), but the brand is required to be protected in order for the trademark owner to keep the branding. A company can selectively enforce a copyright, but they can't selectively enforce a trademark. Trademarks are required to be protected by the trademark owner, whereas copyrights are not. Debian had to change the name of it's own altered Firefox (IceWeasel) for the same reason - do you hate Mozilla for that?ĮDIT: To reiterate, I'm talking about Trademark Law. But you can't change it and still call it Pale Moon, not without official permission.
#Firefox 57 addons pale moon free
Pale Moon is open and the code is free to anybody who wants to use it and call it something else.
If you think that link provides a reason to avoid Pale Moon, then you're anti-opensource.
#Firefox 57 addons pale moon software
If Pale Moon doesn't defend it's branding, then anyone can release any software and call it Pale Moon. But OpenBSD is actually changing the code, making the software something else, but still calling it Pale Moon as if it was official. If OpenBSD shipped with an official build of Pale Moon, there would be no issue. Because Mozilla needs to protect it's branding. IceWeasel is Firefox, literally, with the branding removed. That's why Debian ships with IceWeasel instead of Firefox. If you don't defend your branding, you lose protection for that branding. The take-down in that link is not draconian, it's required by trademark law. Ignoring the announcement and clinging to the abandoned plugins nonetheless was simply short-sighted.Ĭomplaining here in the Linux Mint forum, because now the final EOL day for the unmaintained Firefox plugins had come with the release of Pale Moon 29.2.0, will not change anything.īy the way, I do have Pale Moon 29.2.0, and there is nothing which I have lost when upgrading from 29.1.1 to 29.2.0.I don't want to use pale moon anymore after reading that. The Pale Moon developers kept on announcing that unmaintained Firefox plugins would no longer be permitted in Pale Moon for quite some time. Is it really so hard to understand that the Pale Moon developers are not really keen on having to deal with abandonware, which has been abandonware for years now? Whenever this abandonware causes trouble with Pale Moon, users will complain about Pale Moon, instead of realizing that clinging to abandonware is asking for trouble. In fact all these indispensable and irreplaceable add-ons have not been maintained for years now, basically since Mozilla banned them from their own browser. This is why users caused a fuss, when Firefox took away all these indispensable and irreplaceable add-ons. Nothing is indispensable or irreplaceable. T42 wrote: ⤴ Fri 6:48 amI'm using Pale Moon solely due to its compatibility with several indispensable and irreplaceable old FireFox add-ons
0 kommentar(er)
