Anonymous Source Shared Leaked Google Search API Documents

#1

Post by andrewfong » Tue, May 28, 2024, 3:07 AM UTC

Anonymous Source Shared Leaked Google Search API Documents
sparktoro.com

Re: Anonymous Source Shared Leaked Google Search API Documents

#2

Post by theolivenbaum » Tue, May 28, 2024, 5:20 AM UTC

Seems like a lot of it came from them inadvertently posting some internal API to GitHub: https://github.com/googleapis/elixir-google-api/commit/078b4...

Re: Anonymous Source Shared Leaked Google Search API Documents

#3

Post by ilrwbwrkhv » Tue, May 28, 2024, 5:21 AM UTC

And that's why if a developer doesn't use Firefox and uses Chrome, they are just helping a monopoly take over everything and make a mess.

Re: Anonymous Source Shared Leaked Google Search API Documents

#4

Post by usui » Tue, May 28, 2024, 5:29 AM UTC

> Prior to the email and call, I had neither met nor heard of the person who emailed me about this leak. They asked that their identity remain veiled

And yet the journalist included a screenshot with one of the weakest blurs I've ever seen... Why would you not excise the person's video portion completely? What good does it serve to have it included in the story? Even if that portion is faked, why would you offer potential signals like skin complexion, hair color, background picture, etc.? Why...

Re: Anonymous Source Shared Leaked Google Search API Documents

#5

Post by dgellow » Tue, May 28, 2024, 5:30 AM UTC

ilrwbwrkhv wrote: post #3

And that's why if a developer doesn't use Firefox and uses Chrome, they are just helping a monopoly take over everything and make a mess.

Any user, not just developers

Re: Anonymous Source Shared Leaked Google Search API Documents

#6

Post by Control8894 » Tue, May 28, 2024, 6:05 AM UTC

usui wrote: post #4

> Prior to the email and call, I had neither met nor heard of the person who emailed me about this leak. They asked that their identity remain veiled And yet the journalist included a screenshot with one of the weakest blurs I've ever seen... Why would you not excise the person's video portion completely? What good does it serve to have it included in the story? Even if that portion is faked, why would you offer pote…

It's a fake background.

It's also clearly from Google Meet so... yeah. If he was worried about retribution (from Google, anyway) then they probably wouldn't have been using a Google service.

Re: Anonymous Source Shared Leaked Google Search API Documents

#7

Post by krackers » Tue, May 28, 2024, 6:23 AM UTC

usui wrote: post #4

> Prior to the email and call, I had neither met nor heard of the person who emailed me about this leak. They asked that their identity remain veiled And yet the journalist included a screenshot with one of the weakest blurs I've ever seen... Why would you not excise the person's video portion completely? What good does it serve to have it included in the story? Even if that portion is faked, why would you offer pote…

>weakest blurs I've ever seen

Isn't this the same type of "swirl" blur that Interpol was able to reverse even 10 years back? With advancements since then you're basically handing evidence on a silver platter.

Re: Anonymous Source Shared Leaked Google Search API Documents

#8

Post by ec109685 » Tue, May 28, 2024, 6:48 AM UTC

If anyone is surprised about chrome sending urls to Google, you can turn the “feature” off by unchecking “Make searches and browsing better” in the sync section of Google chrome settings.

Creepy.

Re: Anonymous Source Shared Leaked Google Search API Documents

#9

Post by ec109685 » Tue, May 28, 2024, 6:50 AM UTC

theolivenbaum wrote: post #2

Seems like a lot of it came from them inadvertently posting some internal API to GitHub: https://github.com/googleapis/elixir-google-api/commit/078b4...

Oops, someone’s script was too greedy when uploading those elixir api documents.

Re: Anonymous Source Shared Leaked Google Search API Documents

#10

Post by olliej » Tue, May 28, 2024, 7:01 AM UTC

dgellow wrote: post #5

ilrwbwrkhv wrote: post #3

And that's why if a developer doesn't use Firefox and uses Chrome, they are just helping a monopoly take over everything and make a mess.

Any user, not just developers

Developers just replaced IE as the only thing they develop for with chrome, users then _have_ to use chrome because of web developers who only develop for chrome and consider any behaviour other than "it works in chrome" as a bug in other browsers, just as they did with IE.

Then there's the relentless parade of "alternative browsers" that are just chrome skins - a period IE also went through - that intentionally try to trick people into believing they're not just using chrome but with less security engineering, and more scams.