On 25/02/18 03:10 PM, René Ladan wrote:
> On 25-02-2018 23:32, Jan Beich wrote:
>> Francois Marier <franc...@mozilla.com> writes:
>>
>>>> Our gecko@ team shares Google API key with chromium@ team. rene@ was the
>>>> one who originally obtained
On 17/11/17 10:01 AM, Jan Beich wrote:
> Not sure why Firefox 56 didn't switch to v4 but 57 atm doesn't work.
The mechanism that 56 used to switch to V4 is Shield experiments, which
might be disabled in your builds (either explicitly or implicitly
because they're not official builds).
> Chromium
> Our gecko@ team shares Google API key with chromium@ team. rene@ was the
> one who originally obtained the key, so maybe he still has the project ID.
René, are you able to lookup the Project ID in your Google Account?
To do that go to https://console.developers.google.com and then get the
On 08/09/17 01:42 AM, Jan Beich wrote:
> Jan Beich <jbe...@freebsd.org> writes:
>
>> Francois Marier <franc...@mozilla.com> writes:
>>
>>>>> I just verified your API key in a custom build of Firefox and it will
>>>>> work
On 01/09/17 04:39 PM, Jan Beich wrote:
> No, for now. Other downstream maintainers do, see
> https://bugzilla.mozilla.org/show_bug.cgi?id=1352981
Good. Your API key will work fine as long as you build with
MOZILLA_OFFICIAL=0.
If you ever need to change that, let me know and we can figure out a
On 07/08/17 09:37 PM, Jan Beich wrote:
>> If you are indeed already including a Google API key in your builds,
>> then all you need to do is to add the Safe Browsing API to it, see
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1377987#c0.
>
> Does SafeBrowsing require defining MOZILLA_OFFICIAL
Hi,
I'm responsible for Safe Browsing in Firefox and I am reaching out to
make sure that FreeBSD is ready for Firefox 56 (to be released on
2017-09-26).
In that version, we will be switching to the latest version of the Safe
Browsing API for our malware/phishing protection and that requires a
