4 ms·
Their acceptable use policy seems to be fishy > Innovate, don't duplicate > Don’t make a substitute for Google Photos or use this API to create, train, or imp
by abhisuri97 8y ago
Their acceptable use policy seems to be fishy
> Innovate, don't duplicate
> Don’t make a substitute for Google Photos or use this API to create, train, or improve (directly or indirectly) a similar or competing product or service. For instance, if your app’s primary aim is to provide a general purpose photo gallery app, it’s a substitute for Google Photos.
- reitanqild 8y agoOuch. I didn't catch that. IANAL, but this seems to rule out the use of this API in a number of places where it would be useful (plugin for open source photo management seems to be directly targeted etc). I can understand why they don't want to allow me to train my image recognition software using their API, but this phrasing makes me really wonder what it is for except syncing.
- ldcdc 8y agoThanks, that's helpful feedback. If you have a specific use case in mind, please drop us a note through the partner program and our team can provide you with specific guidance: https://developers.google.com/photos/partner-program/ https://developers.google.com/photos/partner-program/
- reitanqild 8y agoNot a partner so not sure my feedback is relevant there, but an obvious use case would be integration, probably as a plugin into all kind of open source galleries, photo browsers, organizers etc. Also, generally the wording is vague enough to cover almost anything, which means at some point, sooner or later you might have to rely on the judgement of some random future googler to prevent all your integrations being destroyed.
- deleted 8y ago[deleted]
- superioritycplx 8y ago> Don't be evil. Leave that to us.