Live data from Hacker News

Google Cloud Vision API enters Beta

googlecloudplatform.blogspot.com

41–50 of 110 posts

Re: Google Cloud Vision API enters Beta

#41
post #30

Earlier quoted context omitted.

I donno. If I'm composing music, and I heard your music before that, is my music implicitly derived? Your music certainly had some infinitesimal affect on me.

Absolutely, but any music you compose probably also has an element of originality in it, or at least draws inspiration from something that is non-musical in nature. For a trained AI, the entire model is just a derivative work of all the training data. It's not as though the AI had a lover who left them and drew inspiration from that experience to become a more effective AI.

>but any music you compose probably also has an element of originality in it

Is deep dream original in your opinion?

Re: Google Cloud Vision API enters Beta

#42
post #10

Just tried a couple of images with digits to test out the OCR w/ the TEXT_DETECTION setting, unfortunately it assumes what it reads is a defined language with words. I am looking into using this for digit-recognition and only digits, but that doesn't seem to be a use case (as it is now). Does anybody know of another service/API that can do reliable digits-only OCR on (not the finest clear quality) images?

I hope to play with this also tomorrow, as I want to see if it can extract numbers from pictures of a street. The docs say

"TEXT_DETECTION 1024 x 768 OCR requires more resolution to detect characters"

How big were the images you used?

Re: Google Cloud Vision API enters Beta

#43
post #39
post #33

I couldn't find a specific legal SLA for this new service. Does anyone know if: 1) by using the service you grant Google use of the uploaded images. (e.g. they can use your image to increase their corpus, improve the service or use it for advertising, or use it to extract street numbers for their maps, or its always private and never stored) 2) What the resulting copyright is of the returned data. If you were to buil…

If there's no service specific T&Cs for this, it falls under their general cloud T&Cs: https://cloud.google.com/terms/ . s.5: > 5.1 Intellectual Property Rights. Except as expressly set forth in this Agreement, this Agreement does not grant either party any rights, implied or otherwise, to the other’s content or any of the other’s intellectual property. As between the parties, Customer owns all Intellectual Property…

Thanks! I also note that the API pages each state "This is a Beta release of Google Cloud Vision. This API is not covered by any SLA"

Re: Google Cloud Vision API enters Beta

#44
post #3

I feel like this is some really compelling tech. It would be so amazing to build stuff with this in mind. I wouldn't be comfortable doing it, though. This sort of API is available only until Google decide that they don't want it to be available. There's not really anything close to equivalent that you could drop in to replace it if it were being shut down, the price were being hiked, or you had some sort of other iss…

I have all kinds of product ideas from this API, but have the same fears as you.. can't rely on an API. So for now, my best idea is to use it to build something fun with my kids. If only Google would adopt some sort of policy where they would let you download the dataset+code when they shut something off...

Want to share some of those ideas? :)

Re: Google Cloud Vision API enters Beta

#46
post #43
post #39

Earlier quoted context omitted.

If there's no service specific T&Cs for this, it falls under their general cloud T&Cs: https://cloud.google.com/terms/ . s.5: > 5.1 Intellectual Property Rights. Except as expressly set forth in this Agreement, this Agreement does not grant either party any rights, implied or otherwise, to the other’s content or any of the other’s intellectual property. As between the parties, Customer owns all Intellectual Property…

Thanks! I also note that the API pages each state "This is a Beta release of Google Cloud Vision. This API is not covered by any SLA"

SLA is not the same as T&C. No SLA means there is no uptime guarantee.

Re: Google Cloud Vision API enters Beta

#47
post #33

I couldn't find a specific legal SLA for this new service. Does anyone know if: 1) by using the service you grant Google use of the uploaded images. (e.g. they can use your image to increase their corpus, improve the service or use it for advertising, or use it to extract street numbers for their maps, or its always private and never stored) 2) What the resulting copyright is of the returned data. If you were to buil…

Re (2): The answer to that sort of question doesn't even seem clear for other, more widely used Google products. I'm thinking Google Translate or the fonts in their office suite. Both things that most people probably don't think too much about the copyright implications of, but possibly should.

Re: Google Cloud Vision API enters Beta

#48
post #3

I feel like this is some really compelling tech. It would be so amazing to build stuff with this in mind. I wouldn't be comfortable doing it, though. This sort of API is available only until Google decide that they don't want it to be available. There's not really anything close to equivalent that you could drop in to replace it if it were being shut down, the price were being hiked, or you had some sort of other iss…

You are creating a double bind for yourself and others by posting these types of comments. Your comment indicates you want the experience making things with it which would be amazing, but you are also speculating (based on historical evidence) that Google may "take away" the amazing thing from you later.

> I'm not trying to pick on Google for shutting things down

People usually say what they are thinking. In this case, I can certainly appreciate and respect questioning what Google's actions will be in the future, but the problem at hand is that none of us can tell the future. By attempting to do so, and creating a situation where we literally believe two conflicting things at once, we get mired down in illogical arguments that end up making zero sense. Worse, when we post those illogical arguments, others get dragged into the dissonance and end up making similar arguments that make no sense and the result of that is others get lost in the mess we made. For example:

> I think Google understands how big this could be (well, why else do they do anything I suppose?)

Do we really know Google understands how big this could be, or is that just us wishing they wouldn't "shut it down later"? Both thoughts are speculative, at best.

As for me, I have no way to know if I can trust Google will leave these APIs up for as long as I need them or will not change the methods in the APIs at some point breaking my code I've written to talk to it. The latter happens to me all the time!

I realize this comment may stir some emotional responses. All I would ask is that we consider alternative ways of thinking about these illogically binding "feelings" and expand our awareness to the fact that what we really want is our software, regardless of who wrote it, to be open, transparent, trustworthy and capable of running wherever and whenever we want it, regardless of when that is.

Obviously we have a long ways to go before that statement can be a reality. One can hope though!

Post reply on HN