|
|
|
|
|
|
by suhail
1973 days ago
|
|
|
Buried in depths of their documentation? It’s also worked for years too. Google has docs that are completely outdated and neglected. Chrome Extension docs didn’t get updated for 5+ years until recently. Why put it in the console then? Why have tool tips that say “Access to this API is enabled.” There’s no improvement to security. This will be a cake walk to reverse engineer. I don’t see how my point is invalid. |
|
|
You mean right in the instructions on how to acquire them?
> It’s also worked for years too.
It was tolerated for years, but it was always on very shaky ground. Now Google pulled the rug. I'm annoyed because that means my Chromium AUR package stops working, and I'll have to pry the tokens from a release build, but this isn't unexpected.
> Why put it in the console then? Why have tool tips that say “Access to this API is enabled.”
For outside developers who want to work on Chromium. This is also CLEARLY stated in their docs.
> There’s no improvement to security. This will be a cake walk to reverse engineer.
They didn't say it was about security.