google-api-javascript-client VS ruffle

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.

Some of you may know ruffle (https://ruffle.rs).

The memories…

I often wondered what would happen to those wonderful Orisinal mini games after Flash's death, without actually checking out the site. Would Ferry Halim find the time to port them to "HTML5"? Would they just… disappear forever?

It turns out that they know run in Ruffle[1], a Rust/WASM based Flash Player emulator I've never heard of (or forgotten about). The handful of them that I have tested work flawlessly.

[1] https://ruffle.rs/

shrug It finds its uses. It's just not that overstated.

sandspiel is quite popular and is built using WASM: https://sandspiel.club/

Google Earth - https://blog.chromium.org/2019/06/webassembly-brings-google-...

Ruffle (the "make Flash run safely" tool) - https://ruffle.rs/

Ableton's Learning Synths - https://learningsynths.ableton.com/

etc etc. It's just hard to tell when something is using WASM when it "just works" and is indistinguishable from optimized JavaScript

I was amazed that the site still runs, apparently still using the same engine.

But it seems that it was a flash site (of course), and archive.org seems to replace Flash Player with "Ruffle" [1]. Either that, or someone of Tobin's team replaced Flash with Ruffle >= 2019.

[1] https://ruffle.rs/

Out of curiosity a couple months ago I wondered if I could play my old Proximity flash game on Newgrounds from the browser within the Quest 3 VR headset, and it worked great!

That led me to do a little searching, and I discovered that originally the game didn't work in Ruffle, as I apparently did something with the play game button that wasn't normal. But someone put a fix in it back in 2020[1] in order to get my game working again. That was pretty neat. Felt kind of nice that people still cared enough about my old game to make sure it still works in an emulator.

Still working on a more in-depth sequel (using Monogame), and I'm way overdue to make a new web version of the original. Might knock that out once I get closer to getting the sequel out there.

[1]: https://github.com/ruffle-rs/ruffle/pull/1024

i believe it's using Ruffle[0] and that's already happened[1]

[0] https://github.com/ruffle-rs/ruffle

This is all using a really cool Flash emulator called https://github.com/ruffle-rs/ruffle