On 2018-04-08 at 06:38:14, Mike Hommey wrote: > We're using the same API key as the chromium in Debian, so presumably > the same problem applies to the chromium package.
Yes, presumably the Chromium package has the same problem. I did a quick check and none of the test entries from http://testsafebrowsing.appspot.com work. Chromium doesn't have the same debugging capabilities as Firefox though, so I don't have as much visibility into what's going on. > Why should we need a *different* API key? By "different", I didn't different from the chromium package. I meant, another API key. Nobody knows the Project ID for the current API key, so I can't request a quota increase for it. Once Debian has an API key with a higher quota, I'd certainly suggest that the chromium package also switch to it. You're right, there's no need to have two different keys in Debian. Francois -- https://fmarier.org/
