riiis wrote:The one and only definition of "curation" I could find in my many English dictionaries was "cure", i.e. healing. If Phoebus were indeed "a living add-ons site", it might be in need of "curation". However, rest assured Phoebus is not alive, never was alive, and never will be alive.
The Pale Moon Add-ons Site and Project Phoebus are very much a living Add-ons Repository and Project in and of them selves. I don't know how this doesn't make sense to you. It isn't a static archive it changes, grows, adapts, gets better over time. In essence, alive.
Code: Select all
curate verb Select, organize, and look after the items in (a collection or exhibition)
riiis wrote:What does "AUS" mean? Is it an abbreviation for "Australis" or obfuscation? And, how are thousands of old Firefox add-ons, no longer being developed or listed at AMO-- how will these thousands of old Firefox add-ons be in need of update. And by whom will these thousands of old Firefox add-ons be updated?
As mentioned above though slightly incorrect AUS in this context stands for Add-on Update Service. That is what happens either automatically or manually to get updates to add-ons via the Add-on Manager. In a historical context it stands for Automatic Update Service because way back in the long long time ago, Mozilla had "Mozilla Update" which provided the Automatic Update Service for both Applications and Add-ons. This was split not too long after the initial beta phase. "Mozilla Update" (umo) became the Mozilla/Firefox Add-ons Site (amo) and application updating was separated out and went in different directions. Much the same way that XPInstall was eventually reduced to JUST dealing with add-ons. So AUS as in Application Update Service is different from AUS as in Add-on Update Service but they both qualify as Automatic Update Services.
As an interesting sidenote while Add-on Update Service retains it's Mozilla RDF manifest format, Application Update Service switched to bare XML.
NOW, Phoebus while will donate some of it's code for the purposes of driving MY Phoenix Extension Archive that archive has nothing to do with Project Phoebus it's self or any of the living Add-ons Sites. If you thought that the Pale Moon Add-ons Site or future Basilisk Add-ons Site would be flooded with AMO Extensions as part of the Archive then you are very mistaken. Though, I guess I can understand the confusion since I am doing both.
NewTobinParadign wrote:Remember, Pale Moon does NOT support Firefox Extensions and hasn't since v25 despite allowing them to install and gradual lifting of the restrictions on Firefox targeted extensions.
This statement is absurd to the 10th power. The Pale Moon add-ons site is filled with Firefox add-ons, just Firefox add-ons NOT compatible with the latest versions of Firefox. And why build an archive for users, an archive of thousands of old Firefox extensions, if Pale Moon does NOT support these Firefox extensions.
The Pale Moon Add-ons Site is currently filled with extensions that target Pale Moon and have had Pale Moon compatibility added even IF just a targetApplication block. Not all of them support Firefox and while many are derived from extensions that once supported Firefox they may not work for Basilisk or eq stock Firefox. Because the Add-ons Site started as just being for Pale Moon and nothing else.
As stated above, the Phoenix Extension Archive has nothing to do with Project Phoebus (except the software will be based on a stripped down version of the code) it is a separate project that has no connection to the Pale Moon Add-ons Site, Moonchild Productions, or the Pale Moon project. It's intended purpose is preservation and educational reference. In the case of open source it can be used to find old extensions and breath new life in them via forking. Or hell maybe the original developer can grab the code which they abandoned, freshen it up a bit and submit it to one of the proper Add-ons Sites.
See one of the posts above for a link to the reminding announcement on how Firefox Extensions are not supported despite the fact we continue to let them install via the Dual-GUID devised to allow such a thing back when Pale Moon v25 happened. They are still not supported by us nor do we offer any support for using Firefox-targeted extensions. Because it is a crapshoot if they work at all.
Uhh, This link, viewtopic.php?f=1&t=19727
. Which is not a fundamental change from the status quo but was just a reminder of it.
NewTobinParadign wrote:having Firefox extensions on a live Add-ons Site vs a clearly marked archive is deceptive as it will give a false impression of the add-ons that are supported
I thought, from your prior statement, that "Pale Moon does NOT support Firefox Extensions". If Pale Moon, to the contrary, DOES support Firefox extensions, it's better that the few best and most popular of these Firefox extensions be listed at the Pale Moon add-on site, where these add-ons can be easily found by users. And where the safety and compatibility of this limited number of add-ons can be reviewed realistically by the add-ons team (and by the community). This process is preferable to an archive of thousands of old Firefox add-ons, the safety and compatibility of which has been reviewed only by you, or not at all.
I already explained why we can't just dump or allow others to dump unmodified or improperly forked Firefox extensions on our Add-ons Site both the legal and the technical reasons. As I have already said, Pale Moon does NOT support Firefox Extensions. Because they are Firefox Extensions. We do however allow Firefox targeted extensions to install which is NOT the same thing. To be honest, this entire concept is backwards anyway. Pale Moon does not support extensions. Pale Moon supports extensibility. That is, Pale Moon Extensions support Pale Moon. Firefox extensions don't support Pale Moon and under normal circumstances they would not be installable. But in Pale Moon v25 we introduced the Dual-GUID system that allows Firefox targeted extensions to install however as mentioned for four years all over this forum.. It is a crapshoot if they actually work because by definition, Firefox Extensions support only Firefox. Functionality is the only thing in question. Bottom line here is, extensions support applications, not the other way around. I thought you would have figured that out by now...
Let me say this again so it is absolutely clear. There is a difference between a living Add-ons Site and a static archive for historic and educational purposes. I am NOT reviewing Firefox extensions for the Archive.. I am ARCHIVING them for future generations. Once done it is static and unchanging .. an Archive (unless a verifiable good faith takedown request happens for rights reasons for a specific item).
The Pale Moon Add-ons Site, Future Basilisk Add-ons Site, Future Interlink Add-ons Site, and Future Borealis Add-ons Site are sharing common database and datastore and by some cleaver coding by me will only display extensions and themes to each incarnation of the site based on targetApplication.
Let me say it for a .. fourth time. The Phoenix Extension Archive is NOT an Add-ons Site and has nothing to do with any Add-ons Site or even this project. It is something I am personally going to do on thereisonlyxul.org which is sponsored by Binary Outcast. If I keep getting pushed on this, I might decide not to do it at all and let others handle it since apparently they are so much more preferred over me in your eyes. However, don't count on it. There is more to the big picture than your misconceptions and anti-tobinism, riiis.
ANYWAY, I hope I have cleared up any questions people had even though my faith in that being the case isn't very high. I recall people asking if Basilisk is the new Pale Moon and I shudder.
Here is a helpful graphic!
ALSO, someone should REALLY split this off from this thread cause it has been completely derailed at this point.