I wanted to share some details about how we will manage the 1p APIs for signing into Chrome and Chrome OS going forward. Instead of relying on a quota for requests to those APIs, we’re asking you to join google-browser-si...@chromium.org with the accounts you will use for testing those APIs.
There won’t be additional restrictions at this time, i.e., for an account subscribed to this mailing list, you can sign in without additional quota on a chromium build as long as it has a valid OAuth 2.0 client id and secret (note that you can also set them via environment variables).
Accounts not on this mailing list won’t be able to sign in at all on chromium builds with OAuth 2.0 client ids and secrets soon after March 15.
Please note that this quota implementation can change at any point in the future.