So you want to list your add-on on the Add-ons Site?

[New Tobin Paradigm]

So, you decided to bring your add-on to Pale Moon officially, have forked your own version for us, or have simply been awesome and created something new? That is fantastic . You have (or will) let the community chew it up a bit and think it is ready for a proper release.. So what's the next step?

Well, you have a several options but each must be considered carefully.

Remember that you should have a proper Pale Moon application block in your install.rdf with our GUID targeting min and max versions for Pale Moon and make sure it does fully work with us and the version range you have set.

See the developer wiki for instructions: http://developer.palemoon.org/Add-ons:Site

Moderator note: This post has been significantly changed since its creation, with most of the information it previously contained being moved to the Add-ons section of the Pale Moon Developer site.

[GMforker]

Hello,
this option isn't specified:
https://github.com/janekptacijarabaci/greasemonkey/releases/latest (probably temporary "fork")
(Option 3 - somehow this isn't quite the same...)

If my assumption is valid:
This "version" will not be published.


I thought maybe it would be worth mentioning here:
These options are unsupported options: ...

Thank you.

[CharmCityCrab]

Thanks. This will be a good thread to point people towards when they ask about how to go about listing their add-on for Pale Moon, which I've seen a lot of in other threads. Previously, we've all just had to say "Get in touch with Matt". Now we can show them exactly what their options are and how to pursue them with one link to the original post in the thread. This should help grow the Pale Moon add-on ecosystem a lot.

In case anyone is reading this later and wondering which option to use, I personally as a user would prefer option 2. If it's hosted on Pale Moon's site, that means Mozilla can't pull the rug out from under it as in option 1, and that the guys who I trust security wise with my browser (i.e. the Pale Moon devs) have approved the listing of the add-on, rather than risking downloading from an unknown unreviewed source as in option 3, which potentially presents a greater security risk because no one outside add-on development for that specific add-on would have looked at the add-on in advance of it being listed if it's not hosted here. Option 2 seems to present the best combination of visibility to Pale Moon users, and giving Pale Moon users the peace of mind that comes with knowing that a listing has been approved and hosted by the people we already trust with the core of the browser we use. It also helps ensure full compatibility with Pale Moon.

[New Tobin Paradigm]

When it comes to option 3.. I am still gonna give it a cursory review.. If someone would pull something.. The external would be removed from our site.

[ChoGGi]

Hello,
I am interested in adding my addon to the Pale Moon list (using Option 3), I was wondering if I need to use an updateKey along with the updateURL or is just the url fine?


https://addons.mozilla.org/addon/5878/

[squarefractal]

I was wondering if I need to use an updateKey along with the updateURL or is just the url fine?

updatekey isn't required.

[New Tobin Paradigm]

I was wondering if I need to use an updateKey along with the updateURL or is just the url fine?

updatekey isn't required.

Option 3 would require it if you plan to serve it over plain http.

updateKey

To ensure the security of update rdf data that is retrieved over plain http you must use a digital signature to verify the contents of the data. In order to do so you must include the public part of the cryptographic key in an updateKey entry in the install.rdf of the add-on. This can be generated using the McCoy tool. Any line breaks and whitespace as part of this entry are ignored.

However, if it is on AMO that isn't option 3.. That is option 1 and I haven't discussed option 1 yet

[ChoGGi]

Thank you for the clarification

[LimboSlam]

Hello.

I didn't find any of this information on APMO. Will this be added at some point? Just wondering, as a buddy of mine is interested in coding for add-ons (just a thought in his head and we had a causal talk about browsers) and he wanted to know his options on hosting his innovations for Pale Moon.

[back0rifize]

Hello!

I have a question. Yesterday, I've sent a request to add my extension at APMO. So, can you tell me, please: how long will it take to check it? I'm not in a hurry, just asking to know .

Thank you!

[Lootyhoof]

Hello!

I have a question. Yesterday, I've sent a request to add my extension at APMO. So, can you tell me, please: how long will it take to check it? I'm not in a hurry, just asking to know .

Thank you!

To whom did you send it to? Both myself and Andrew can process add-on submissions.

[back0rifize]

I sent it to Andrew with private message.

[back0rifize]

Sorry, but I have one more question: I made an update for my extension, and uploaded it to ftp. I've tried to use both passive and normal modes, but when I check an extension, it stays as it was before (I mean, if there was version "3.0", it stays in "3.0"). Other words, it seems, that there is no auto-update from ftp.

[Lootyhoof]

Sorry, but I have one more question: I made an update for my extension, and uploaded it to ftp. I've tried to use both passive and normal modes, but when I check an extension, it stays as it was before (I mean, if there was version "3.0", it stays in "3.0"). Other words, it seems, that there is no auto-update from ftp.

Did you update phoebus.manifest also? If you don't, the issue you described will happen as the server won't know that there is an update.

[back0rifize]

Oops, I have forgotten to do it! Thank you!

M-m-m... Sorry, but do you have an adequately explanation about this "phoebus.manifest" and "phoebus.content". Yes, I saw and read description at http://developer.palemoon.org/Add-ons:Site about Xⁿ⁺¹-times, and I don't understand at all, what the hell does it mean! Do you have some "visual" (or whatever) sane examples? Not this senseless text strings, which can be understood by only their authors, but a real examples, like Mozilla usually do it?

[gracious1]

Hello,
I am interested in adding my addon to the Pale Moon list
https://addons.mozilla.org/addon/5878/

Were you able to work out whatever the issue was? I don't see your addon on the Pale Moon website yet, but I would like to!

[Lootyhoof]

Oops, I have forgotten to do it! Thank you!

M-m-m... Sorry, but do you have an adequately explanation about this "phoebus.manifest" and "phoebus.content". Yes, I saw and read description at http://developer.palemoon.org/Add-ons:Site about Xⁿ⁺¹-times, and I don't understand at all, what the hell does it mean! Do you have some "visual" (or whatever) sane examples? Not this senseless text strings, which can be understood by only their authors, but a real examples, like Mozilla usually do it?

As a brief example of phoebus.manifest, say for instance your manifest looked like this currently:

Code: Select all

[addon]
type="extension"
id="example@id"
release="example-1.0.xpi"

[metadata]
name="Example Addon"
slug="example"
author="Example Author"
shortDescription="Example description."
licence="example-licence"
homepageURL="http://example.here"
supportURL="http://example.here"

[example-1.0.xpi]
version="1.0"
minAppVersion="27.0.0"
maxAppVersion="27.*"

If you were to then upload the new version (for this example, this is version 2.0), leaving the older XPI intact, you would edit this to look like this:

Code: Select all

[addon]
type="extension"
id="example@id"
release="example-2.0.xpi"

[metadata]
name="Example Addon"
slug="example"
author="Example Author"
shortDescription="Example description."
licence="example-licence"
homepageURL="http://example.here"
supportURL="http://example.here"

[example-2.0.xpi]
version="2.0"
minAppVersion="27.0.0"
maxAppVersion="27.*"

[example-1.0.xpi]
version="1.0"
minAppVersion="27.0.0"
maxAppVersion="27.*"

As for phoebus.content, this uses BBcode-alike styling, much the same as this forum does. Style it as you would a forum post.