4 ms·
>Google offers contracts and standard business relationships for some commercial uses of their API. Workflow could have reached out to the appropriate Google pr
by kharms 10y ago
>Google offers contracts and standard business relationships for some commercial uses of their API. Workflow could have reached out to the appropriate Google product person/lawyer, instead of sending a generic email as Marco speculates, if they were keen to use Google Translate instead of switching to Microsoft Translate.
Sounds like you're speculating about details based on a second hand retelling of a podcast host's individual experience. A host who presumably doesn't have an "appropriate person/lawyer."
- canuckintime 10y agoI was actually listening to the ATP podcast live as they were recording and I heard Marco's words in real time. My remarks of the possibility of standardizing their Translation API use aren't speculation; Google's terms/offers are pretty public: https://cloud.google.com/translate/faq https://cloud.google.com/translate/faq While Marco tried to put a nice spin on it, it should be obvious why Workflow dropped Google services