The end of uBlock Origin for Google Chrome?

[Karlston]

The end of uBlock Origin for Google Chrome?

There has been lots of talk about Google's proposed changes to the Chrome web browser's extensions system and how these changes would affect content blockers and other extensions.

 

The new manifest file for Chrome extensions could end extensions like uBlock Origin for the web browser. Google changed some parameters after it faced heavy user and developer criticism but did not revert the course completely.

 

Raymond Hill (gorhill), the developer of uBlock Origin revealed recently that Google rejected a new developer version of the extension. Developers upload new extension versions to the Chrome Web Store to replace existing versions; Google runs automated scans of these tools and may also look at the uploaded extensions manually before allowing or rejecting them.

via Raymond Hill / GitHub

In an email to the developer, Google stated that the extension violated one of the Chrome Store's policies that prohibits the bundling of unrelated functionality in extensions.

 

The email provides no information on the actual violation other than that, a practice that Google has been criticized for in the past.

 

Hill, a long-time developer, had no illusions that Google would provide actionable information about the rejection.

No point speculating one way or another, my experience with the CWS in the past is that we will never know why it was labelled "REJECTED", they never disclose the exact "why".

The developer version of the extension is used by fewer users than the stable version which means that the rejection does not affect the bulk of users of the extension yet. The main issue with the rejection is that the next stable version of the extension will be more or less identical to the rejected developer version.

 

While there is still the chance that it will go through, it is more likely that it too will be rejected by Google and that this could effectively end uBlock Origin for Google Chrome.

Since the next uBO release will essentially be what 1.22.5rc2 is, consider that uBO is probably coming to an end of life in the Chrome Web Store -- there is no good reason to believe uBO 1.22.5rc2 would no longer be rejected with only changing the version number to 1.23.0.

Hill recommends that users find another browser that continues to support uBlock Origin if they want to continue using the extension.

 

The latest version of the extension is available for many major browsers including Mozilla Firefox and other Chromium-based web browsers.

Closing Words

It is impossible to know why the extension was rejected from the Chrome Web Store unless Google would provide further information on the issue. While it is certainly possible that the stable extension update would be allowed by Google, it seems more likely that it will be rejected as well by the company.

 

 

Source: The end of uBlock Origin for Google Chrome? (gHacks - Martin Brinkmann)

[steven36]

it  was approved  today so no its not the end yet.

https://old.reddit.com/r/chrome/comments/dgoymg/warning_ubo_ublock_origin_will_possibly_be/f3fwlto/

https://chrome.google.com/webstore/detail/ublock-origin-development/cgbcahbpdhpcegmbfconppldiemgcoii

https://github.com/uBlockOrigin/uBlock-issues/issues/745

 

This not the 1st time it happen ether but gorhill need to contact Simeon instead of posting about it on github he fixed for him

 

dotproto 8 points 3 hours ago*

 

Short answer: No.

Longer answer: Public outcry isn't necessary, but communication is. Run-ins with review are, unfortunately, one of the side effects of centralized stores. Short term I'd strongly encourage u/gorhill4 to reach out to me (preferably via Twitter) when something like this happens so I can jump on it right away. Longer term I'm hopeful that we can improve our developer communications to make it a bit easier on devs and clearer as to what their options are in terms of requesting clarification or contesting review decisions.

EDIT: I accidentally some words.

 

uBlock-user 5 points 3 hours ago 

This isn't the first time that this has happened. Previously gorhill had to rename dev build to development build to get it reinstated and the communication is just borderline trollish, no human contact, just automated replies whenever asked for reason and specifics.

 

dotproto 2 points 2 hours ago 

Before I was hired there was not much of any developer outreach; I suspect that incident happened during a period where there was no human to contact. But I'm here now (hi :]) and doing my best to grease these wheels of communication and to advocate & push for improvements.

 

PS: The end will come when they do like apple did with there browser and update the api were it don't work no more until then  you can always use the unpacked version in developer mode even if removed from the store  or not approved . at lest on chromium and brave you can i don't know about Google Chrome because I  don't use close source browsers. Chromium is not apple you can fork it yourself were it will still work and Brave and others say they was . but we will see.

 

[zanderthunder]

8 hours ago, Karlston said:

Google stated that the extension violated one of the Chrome Store's policies that prohibits the bundling of unrelated functionality in extensions

The reasoning Google used to reject uBlock extension is absurd. The definition of "unrelated functionality" is unclear.

 

8 hours ago, Karlston said:

Hill recommends that users find another browser that continues to support uBlock Origin if they want to continue using the extension.

Don't worry, Hill can provide a .crx file to install uBlock manually if uBlock doesn't allowed anymore in the Store in the future. Besides, Chromium is open-source.

[steven36]

On 10/13/2019 at 12:24 AM, Edward Raja said:

Don't worry, Hill can provide a .crx file to install uBlock manually if uBlock doesn't allowed anymore in the Store in the future. Besides, Chromium is open-source.

He never has provided crx  files expect  for at Google store . He use to never release dev builds to  the store  for a long time they was only stable , on github  he only releases unpacked zips to use in developer mode . I been using it for many  years every since it came to Firefox , Browsers like Brave won't even  let you use crx not from the store  it will disable it  only unpacked in developer mode  will work. any way it was revolved Saturday  its up to rc 4  now at Google store .

[zanderthunder]

30 minutes ago, steven36 said:

Browsers like Brave won't even  let you use crx not from the store

I beg to differ. I'm able to install IDM extension (packed .crx extension) in Brave without using the store. Same goes to other Chromium-based browsers, provided that developer mode is turned on.

 

Besides, Opera also allows installation from Google Web Store as well (provided an extension "Install Chrome Extensions" is installed via Opera Addons) apart from Opera Addons.

[steven36]

12 minutes ago, Edward Raja said:

I beg to differ. I'm able to install IDM extension (packed .crx extension) in Brave without using the store. Same goes to other Chromium-based browsers, provided that developer mode is turned on.

 

Besides, Opera also allows installation from Google Web Store as well (provided an extension "Install Chrome Extensions" is installed via Opera Addons) apart from Opera Addons.

Opera allows if if you install the Opera extension to allow it but not all Google extensions work right in Opera   , The reason IDM  works it's been signed by Google  same as   the IDM xpi have been signed by Mozilla . I used IDM  on windows  since 2006.

[zanderthunder]

1 minute ago, steven36 said:

Opera allows if if you install Oprea extension to allow but not all Google extension work right in Opera

I know the limitations very well, especially the fact that themes can not be used.

[steven36]

8 minutes ago, Edward Raja said:

I know the limitations very well, especially the fact that themes can not be used.

i had  a extension I  use  not in the google store the other day that i use in Firefox  , Brave disabled it  they said it wasn't in the store , so i had get the unpacked version from the repo and  side load it. It has to be signed by Google or you have side load it in a folder unpacked.