When clicking the FireFox link, I get this webpage:

[melmakes]

[jamespizzurro]

Looks like I received two emails from Mozilla on May 28th:

Hello,


Your Extension Picket Line Notifier was manually reviewed by the Mozilla Add-ons team in an assessment performed on our own initiative of content that was submitted to Mozilla Add-ons.

Our review found that your content violates the following Mozilla policy or policies:

    - Security, specifically Other security issue: We noticed that the url you're using (https://gitcdn.link/cdn/jamespizzurro/picket-line-notifier/main/data/strikes.json) is not working.



Affected versions: 0.1.0, 1.0.0, 1.0.1

Based on that finding, those versions of your Extension have been disabled on https://addons.mozilla.org/developers/addon/2730610/versions and are no longer available for download from Mozilla Add-ons, anywhere in the world. Users who have previously installed those versions will be able to continue using them.

You may upload a new version which addresses the policy violation(s).


More information about Mozilla's add-on policies can be found at https://extensionworkshop.com/documentation/publish/add-on-policies/.


Thank you for your attention.

Hello,


Your Extension Picket Line Notifier was manually reviewed by the Mozilla Add-ons team in an assessment performed on our own initiative of content that was submitted to Mozilla Add-ons.

Our review found that your content violates the following Mozilla policy or policies:

    - Security, specifically Unsanitized DOM injection: This add-on is creating DOM nodes from HTML strings containing potentially unsanitized data, by assigning to innerHTML, jQuery.html, or through similar means. Aside from being inefficient, this is a major security risk. For more information, see https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Safely_inserting_external_content_into_a_page . Here are some examples that were discovered:
-> popup.js line 51



Affected versions: 1.0.3, 1.1.0, 1.1.1, 1.2.0

Based on that finding, those versions of your Extension have been disabled on https://addons.mozilla.org/ and are no longer available for download from Mozilla Add-ons, anywhere in the world. Users who have previously installed those versions will be able to continue using them.

You may upload a new version which addresses the policy violation(s).


More information about Mozilla's add-on policies can be found at https://extensionworkshop.com/documentation/publish/add-on-policies/.


Thank you for your attention.

We'll need to address these issues before we can get the extension back on Mozilla Add-ons again.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[d-RLY]

Are there any links to download the xpi file to side-load it? I use FF and a fork of it most of the time and would love to have it added.

[jamespizzurro]

Are there any links to download the xpi file to side-load it? I use FF and a fork of it most of the time and would love to have it added.

Initially we distributed an XPI file for this purpose, but it stopped working, so we removed it. And since Firefox doesn't officially support sideloading extensions without them being signed by Mozilla first, we probably won't be able to do that until our extension passes Mozilla's testing to be listed in their add-ons store again again.

In the meantime, maybe try temporarily installing the extension in Firefox using the source code found in this repository? Doing so will require you to toggle on some developer functionality in your browser though.

[katerberg]

For what it's worth, the link referenced also does not load for me.

Would a PR that removes this call and just goes to jsDeliver instead during the failure process be accepted?

I'm happy to do that if so.

[jamespizzurro]

@katerberg Yes, I think that would at least resolve the first issue Mozilla noted, but the second one might require more work, and I think both need to be resolved in order to get us listed on Mozilla Add-ons again. I could take a stab at tackling the second issue though if you were to take on the first one! :)

[katerberg]

Perfect! I'll add it to my to-do over this weekend.

I keep accidentally opening NYT links and would love to have this add-on back!

[jamespizzurro]

With #1036 now done thanks to @katerberg, I'll take a look at resolving the rest this week using this documentation as a guide. Once all changes are in, I'll build and submit a new version of the browser extension to Google, Mozilla, and Microsoft for review for their respective browsers.