bjornstar / intercept-redirect

Skip tracking redirects that serve no purpose other than to waste your precious time.
https://intercept-redirect.bjornstar.com
MIT License
26 stars 4 forks source link

Publish v5.1.2 on the Chrome Web Store #15

Closed bjornstar closed 4 years ago

bjornstar commented 4 years ago

Currently blocked by #11

bjornstar commented 4 years ago

Since v5.0.0 was rejected I can attempt to publish v5.1.2

The description reads:

Supported Domains

  • *.curseforge.com
  • *.digidip.net
  • disq.us
  • console.ebsta.com
  • exit.sc
  • l.facebook.com
  • gate.sc
  • www.google.co.jp
  • news.url.google.com
  • plus.url.google.com
  • www.google.com
  • l.instagram.com
  • www.javlibrary.com
  • l.messenger.com
  • outgoing.prod.mozaws.net
  • gcc01.safelinks.protection.outlook.com
  • slack-redir.net
  • steamcommunity.com
  • twitter.com
  • t.umblr.com
  • vk.com
  • workable.com
  • www.youtube.com

For Firefox - https://intercept-redirect.firefox.bjornstar.com

For Opera - https://intercept-redirect.opera.bjornstar.com

When this version fails to be published I will take the extension private and stop attempting to distribute it publicly on the Chrome Web Store.

bjornstar commented 4 years ago

v5.1.2 was rejected by the Chrome Web Store with the following message:

Dear Developer,

Your recent publish request for Google Chrome item "Intercept Redirect" with ID: kdjmiebhgaleboaamnehjbamlghkoedf was rejected because it did not comply with our policies.

If you already have a published version of this item on the Chrome Web Store, it has not been affected and is still available.

Your item did not comply with the following section of our Program Policies:

"Spam and Placement in the Store"

Do not use irrelevant, misleading, or excessive keywords in item descriptions, titles, or metadata. Please ensure that your item has a description that clearly and directly relates to its functionality.

Once your item complies with Chrome Web Store policies, you may request re-publication in the Chrome Web Store Developer Dashboard. Your item will be reviewed for policy compliance prior to re-publication.

If you have any questions about this email, please respond and the Chrome Web Store Developer Support team will follow up with you.

Important Note:

Repeated or egregious policy violations in the Chrome Web Store may result in your developer account being suspended or could lead to a ban from using the Chrome Web Store platform.

This may also result in the suspension of related Google services associated with your Google account.

Sincerely,

Chrome Web Store Developer Support

I haven't heard anything for 2 days from @dotproto.

At this point I have to admit defeat. I will take my extensions down from the Chrome Web Store.

bjornstar commented 4 years ago

I'm a glutton for punishment, I tried one more time with a revised description:

Some websites use a redirect service to track outbound links. This puts an extra obfuscated hop between you and the destination of those links.

This extension will intercept network requests on supported sites and instantly send you to the intended destination.

For a list of domains that are supported by this extension, please visit https://github.com/bjornstar/intercept-redirect

For Firefox users - https://intercept-redirect.firefox.bjornstar.com

For Opera users - https://intercept-redirect.opera.bjornstar.com

bjornstar commented 4 years ago

And of course after I do that, I magically get a reply @dotproto in the Chromium Extensions Group:

Bjorn, I just a look at your most recent submission and I believe you've addressed the problem. As such, I have requested a second opinion on your most recent verdict.

All of this trouble just so Google can avoid answering questions directly.

Submission is still pending...

bjornstar commented 4 years ago

It was rejected last night with the exact same form mail:

Dear Developer,

Your recent publish request for Google Chrome item "Intercept Redirect" with ID: kdjmiebhgaleboaamnehjbamlghkoedf was rejected because it did not comply with our policies.

If you already have a published version of this item on the Chrome Web Store, it has not been affected and is still available.

Your item did not comply with the following section of our Program Policies:

"Spam and Placement in the Store"

Do not use irrelevant, misleading, or excessive keywords in item descriptions, titles, or metadata. Please ensure that your item has a description that clearly and directly relates to its functionality.

Once your item complies with Chrome Web Store policies, you may request re-publication in the Chrome Web Store Developer Dashboard. Your item will be reviewed for policy compliance prior to re-publication.

If you have any questions about this email, please respond and the Chrome Web Store Developer Support team will follow up with you.

Important Note:

Repeated or egregious policy violations in the Chrome Web Store may result in your developer account being suspended or could lead to a ban from using the Chrome Web Store platform.

This may also result in the suspension of related Google services associated with your Google account.

Sincerely,

Chrome Web Store Developer Support

I replied to this form mail with:

Could you please tell me more details so that I can fix the problem? I am unable to guess what is wrong based on the information provided here.

bjornstar commented 4 years ago

I also posted on the Chromium Extensions Group:

I have once again received the exact same "Spam and Placement in the Store" rejection notification that I have gotten for the past 2 months.

I cannot tell what is wrong. The repeated form mail rejection notifications are worse than helpful.

This whole experience has been extremely frustrating and nothing I do seems to have any effect. It makes me want to remove my extensions from the Chrome Web Store.

bjornstar commented 4 years ago

I also posted a tweet since there's no centralized place to follow the progress:

Once again rejected with the same "Spam and Placement in the Store" violation. No idea what's going on here, but I'm certainly being dissuaded from publishing on the Chrome Web Store.

bjornstar commented 4 years ago

I did get a response from @dotproto yesterday:

For the moment please hold off on editing your draft or submitting another version. I believe the changes you've already made have addressed the violation. Review may be able to publish a previously rejected version so long as the draft hasn't changed since the last rejection.

Which is the only forward progress I have heard in this months long saga to publish and updated version on the Chrome Web Store.

bjornstar commented 4 years ago

At some point in the past few days it was approved and made public without any explanation whatsoever.

So now it's published, pretty awful developer experience.

bjornstar commented 4 years ago

Hilariously, the Chrome Web Store sent an e-mail at 90 minutes after I posted here which said:

Dear Developer,

Thank you for reaching out to us. Upon a subsequent review, we’ve reinstated your item and it is available in the Chrome Web Store.

Thank you for your cooperation,

Chrome Web Store team

I'm so disappointed by the Chrome Web Store. There are so many ways they could do better.