Fwd: Chrome Web Store: Removal notification for LibX for Google Chrome (TM)

[LibX Project]

As some of you have already noticed, we've been removed from the Chrome store.  I've attached the message we received from Google below.

Although we haven't updated LibX since 2015 in the store, today Google found that we don't comply with their program policies.  Google believes that we "obfuscate code or conceal functionality," but neither the email nor the developer's console contains any more information about it (that I've found.)

I've sent a reply asking what they are referring to, but haven't heard back from them (and don't expect to, either).

 - Godmar

---------- Forwarded message ---------
From: <chromewebstor...@google.com>
Date: Wed, Apr 10, 2019 at 7:38 AM
Subject: Chrome Web Store: Removal notification for LibX for Google Chrome (TM)
To: <libx...@gmail.com>
Cc: <chromewebstor...@google.com>

Dear Developer,

We have reviewed your item, "LibX for Google Chrome (TM)," with ID: ffkfoaiikoedjcjlpnnaidojhfchiafk and it does not comply with our program policies. Please review this section of our policy:

Developers must not obfuscate code or conceal functionality of their extension. This also applies to any external code or resource fetched by the extension package.

Your item was found to have one or more files that does not comply with this policy.

Please note that minification is allowed in the following forms:

• Removal of whitespace, newlines, code comments, and block delimiters
• Shortening of variable and function names
• Collapsing the number of JavaScript files

For more information, please review these recommended minification techniques for Google Developers. 

Once you have made the compliant changes you may submit and publish a new draft in the developer dashboard. Your draft will be reviewed for policy compliance, which typically takes a few business days. If the outcome of the review is successful, your store listing will remain published. If we find additional issues with your item, we will send you another email with details. If you have any questions about this email, please respond and the Chrome Web Store developer support team will follow up with you.

Thank you for your cooperation.

Google Chrome Web Store team

---------------------------

Developer Terms of Service: 

https://developers.google.com/chrome/web-store/terms

Program Policies:

https://developers.google.com/chrome/web-store/program_policies

Branding Guidelines:

https://developers.google.com/chrome/web-store/branding

 

[Darcy Duke]

So if you don't get a reply, is that the end of LibX? I know there will be a lot of disappointed folks (I've already heard from one), but I understand the tenuousness of the support you are able to provide at this point. :(

Darcy

MIT Libraries

[Senior, Heidi]

We’re continuing to support current/legacy users, at least until we run into a situation where we need to update the plugin. It seems the Edition Builder is also unavailable; is that related to the Chrome problem?

 

Here’s what we currently tell people: https://library.up.edu/productivity-tools/library-browser-plugin.html

 

Cheers,

 

Heidi Senior

 

 

Heidi E. K. Senior

Reference/Instruction Librarian

Clark Library

University of Portland

5000 N. Willamette Blvd.

Portland, OR 97203

sen...@up.edu <> 503-943-8037

ORCiD: http://orcid.org/0000-0001-5139-3092