2 ms·
> Some time ago, I was looking for a research target in Google and was digging through the Internal People API (Staging) discovery document Should... should th
by philipwhiuk 2y ago
> Some time ago, I was looking for a research target in Google and was digging through the Internal People API (Staging) discovery document
Should... should this just be public: https://staging-people-pa.sandbox.googleapis.com/$discovery/rest?key=AIzaSyBOh-LSTdP2ddSgqPk6ceLEKTb8viTIvdw https://staging-people-pa.sandbox.googleapis.com/$discovery/...
- kccqzy 2y agoIt's just an automatically translated schema file from their internal .proto definition. Google relies on real cryptography not security through obscurity. Furthermore the discovery endpoint is publicly documented[0] and specifically meant for external users. Nobody internal would read the discovery endpoint: they would just pull up the .proto file through code search. Another observation: from my experience at Google it took multiple weeks of effort fighting against the bureaucracy to be able to expose an API to the public. It's not like an AWS S3 bucket that could just be accidentally public. The team knew this is public and had fought the bureaucracy to make it public. [0]: https://developers.google.com/discovery/v1/getting_started https://developers.google.com/discovery/v1/getting_started