uBlock Origin works best on Firefox

Post by starwatch » Sat, Apr 10, 2021, 10:32 AM UTC

ehsankia wrote: post #340

starwatch wrote: post #322

Earlier quoted context omitted.

The approval process differs for extensions published to the Firefox and Chrome stores. When submitting to the Firefox store you need to send them your un-minified, un-obfuscated source, along with step by step instructions on how to build. If you get big enough they do review the code in surprising depth. The hash of the compressed file pushed for release, also needs to match that of the compressed file the reviewer…

> You can push up minified, obfuscated code and that's what the reviewers have to work with. Minified maybe, but obfuscated is against the rules, for over 2 years now: https://www.zdnet.com/article/google-to-no-longer-allow-chro... Chrome also does check the code manually, not sure if it's on the same level as Firefox though.

  Code Readability Requirements:

  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. Minification is allowed, including the following forms:

  - Removal of whitespace, newlines, code comments, and block delimiters
  - Shortening of variable and function names
  - Collapsing files together

Post by RealStickman_ » Sat, Apr 10, 2021, 10:40 AM UTC

Youden wrote: post #416

antattack wrote: post #31

I would use Firefox + uBlock Origin over other browsers even if it was half as fast.

In what way is Firefox not fast? I typically run it right alongside Chrome (Firefox for personal stuff, Chrome for work) and don't notice much of a difference switching between them. If anything, Firefox is faster.

Post by Oddskar » Sat, Apr 10, 2021, 11:14 AM UTC

throwaway189262 wrote: post #327

xoa wrote: post #70

Wow, what an awesome dive into some of the technical aspects behind one of my favorite tools for using the web. And I do think of it that way these days, it's fairly stunning on some sites to switch off all the block and see how they become genuinely unbrowsable. I remember seeing Gorhill discuss a few times over the years some of the reqs for uBO during certain times (like why it could no longer work with Safari fol…

I think the future is machine learning based blocking. Ads are obvious, they have to be for users to see them. You could probably use text classification and object recognition to filter ads effectively. And you could do it from the view layer where nothing on the page can tell they've been blocked. This is also my tinfoily theory for why Chrome restricts the API's used by ad blockers. It's to prevent more effective…

Post by roca » Sat, Apr 10, 2021, 11:26 AM UTC

linknoid wrote: post #221

roca wrote: post #189

Earlier quoted context omitted.

Does Netflix not work in Firefox for you? Mozilla and Netflix have worked together a lot to make sure it does work.

Nope, I get Error Code F7701-1003. I have Wildvine enabled, and I tried completely disabling NoScript. It's easier to just use Chrome for that one thing than have to troubleshoot the problem.

Post by davidgerard » Sat, Apr 10, 2021, 11:31 AM UTC

clircle wrote: post #42

This is technical and interesting, but can anyone tell the difference between web browsing with FF/uBo and Chrome/uBo? I personally cannot, other than that the fonts render a bit differently. Webpages load fast and no ads get through in both cases.