google-api-javascript-client VS adblock-rust

Sometimes different JavaScript libraries are needed for in-browser vs node.js. I think that the npm googleapis package is specifically for node.js, and for in-browser use you need to use https://github.com/google/google-api-javascript-client

Incorrect, twice. We're not asking you to trust us, you can verify it yourself, Google Auth's scripts are open source. Here and here. They're also available in our repo as well.

API client for JavaScript

One interesting consequence of this is that Google's own javascript api client will no longer work with MV3 and there are apparently no plans to ever make it work.

See https://github.com/google/google-api-javascript-client/issue...

So effectively this means extensions on MV3 can't easily access Google apis, which is quite unfortunate since Chrome extensions in particular made Google authentication super straightforward (piggybacking off of chrome's built-in google authentication). If someone knows a better way I'd love to hear it.

I believe the reason that the current incarnation of the javascript library won't work is because it modifies the dom to add script tags to fetch and run the api library (or components of it), which is specifically what MV3 will disallow AFAIK.

What I want to do is contact the developers of this library. I looked at the google-api-client-libary for Javascript and thought about raising an issue due to the insufficient documentation, but the owners seem to be very slow in responding. How do I contact the developers and perhaps get a response in 1-2 days or at most a week?

Have you read the documentation and source? If so, maybe include the part that is confusing to you so people can help explain that specifically.

Here is an example of using Google APIs Client Library for browser JavaScript, aka gapi with no authentification. The Google Api we are calling here is Calendar API.

I have a Vue 3 / Quasar / TypeScript app that is using the Google API Client Library for JavaScript (also known as gapi).

I know that this is problem with server side rendering in my Next.js app and people recommend using a client side package like this https://github.com/google/google-api-javascript-client. But google-api-javascript-client doesn't have any documentation on authenticating with a .json credentials file instead of an API KEY which I do not have.

I've authenticated the user using Firebase successfully, giving me a user object to play with, however, to ping the Calendar API, I'm using the gapi library. This means, though, that I have to do the whole OAuth2 cycle twice - once to 'log in' the user to the application, and once to 'authorise' the application to use the user's token to use the Calendar API.

Brave has written their own (open source) adblock engine (in rust) that is directly integrated into the browser (ie. not an extension, so is not affected by Manifest V3).

https://github.com/brave/adblock-rust

Here is a (somewhat dated) article describing it by the authors:

https://brave.com/improved-ad-blocker-performance/

Brave has its own Rust implementation of an adblocker embedded in the browser: https://github.com/brave/adblock-rust; so it does not embed uBlock Origin (but the filters are mostly compatible)

Disclaimer: I work at Brave but not on the browser.

We support :has currently, which impacts many filters in EL and uBO. Some non-supported filters such as upward() can be manually converted over to use :has instead. The other unsupported procedual filters are a WIP will depend how easy/hard they are implement. No ETA, but have opened a ticket https://github.com/brave/adblock-rust/issues/293

ublock on chromium and brave itself can't use all of the filters in that list: https://github.com/brave/adblock-rust/issues/4

It's open source https://github.com/brave/adblock-rust

I've fixed this in the adblock engine as of https://github.com/brave/adblock-rust/commit/8a755bdb190bb55a3a3acee1e6507085051bdeec, and I'll push to get this patched in 1.47 soon. Thanks for the reports!