Where can I get the .xpi about firefox-feedly-rss HOT 2 OPEN

Why?

from firefox-feedly-rss.

At the time, because Feedly quit supporting the older subscribe link, and that needed to be changed, though they did end up restoring support later.

Unfortunately, a poor choice I made regarding how the keys were added to the Firefox config store* made upgrading the extension risky, so I held off based on that and the additional requirement for code signing on newer versions.

Now, the problem is that I use platform APIs that aren't supported in the new extension model. var {Cc, Ci} = require("chrome"); is pretty much verbatim what they say the new model doesn't support, and is what I used to register the handler.

I am absolutely happy to have someone fork this, though they should fix the keystore issue I describe below, probably by saving off the ID of the handler that this add-on manages into an add-on-specific key.

And the behavior is available in Feedly Notifier, who did effectively fork this with his inclusion of the code. Assuming he doesn't run into a support issue with the chrome APIs being used, then that's where I'd go for this functionality.

• I counted on my add-on being the only one manipulating the keys to add a handler by that exact name and URL, and it used that assumption to handle upgrade/disable/uninstall changes to the keystore. Someone else (Feedly Notifier) ended up including my add-on code directly in their add-on without changing that value--they had no way to know that was significant--so now we had two add-ons potentially manipulating those keys without knowledge of each other. That could cause a bunch of unexpected behavior on upgrade.

from firefox-feedly-rss.