3 ms·
Geez did you guys even look at the URLs? https://safebrowsing.google.com/safebrowsing/downloads?client=Iceweasel&appver=38.1.0&pver=2.2&key=no-google-api-key h
by takeda 11y ago
Geez did you guys even look at the URLs?
https://safebrowsing.google.com/safebrowsing/downloads?client=Iceweasel&appver=38.1.0&pver=2.2&key=no-google-api-key https://safebrowsing.google.com/safebrowsing/downloads?clien...
Isn't the API key your fingerprint? The key is not shown here, because the author was showing what the requests look like on first run, subsequent requests would contain your unique ID in them.
Not picking on you specifically, I saw several responses saying the same thing.
- magicalist 11y ago> Isn't the API key your fingerprint? No, it's a per-application key, so in this case it would be IceWeasel's key.
- takeda 11y agoIn that case why would it make a request with "key=no-google-api-key" then why not use the IceWeasel key right from the start?
- magicalist 11y agoNo clue, but it's not like we have to guess about what it is. It's all covered in the Safe Browsing docs: https://developers.google.com/safe-browsing/lookup_guide#GettingStarted https://developers.google.com/safe-browsing/lookup_guide#Get...