I wrote 'some developers', so i'm not blaming all of them. On May 27, 4:39 pm, Zdravko Gligic <zgli...@gmail.com> wrote: > Please do not blame all developers because (like in any other > business) some abuse the situation. I for one, have stated many times > that I was even willing TO PAY to cover the costs of someone from GOOG > taking a look and evaluating my own use cases and compliance - JUST TO > MAKE SURE that I was. > > In fact, what GOOG just did to the honorable and compliant individuals > is far worse than what abusers have been doing to it. The issue of > abusers is as plain as night and day. The issue of running Translate > v1 and not learning anything from it and then introducing v2 and with > it sending out a totally wrong signal is TOTALLY IRRESPONSIBLE. > > Now, if that was not enough, they introduced the "ask for more quota" > process and that in itself suggested that while we may end up being > fed with a medicine dispensing droplet, IT DID SUGGEST that v2 would > be around FOREVER for at least the use cases that made business sense > to them. > > What I believe to be happening and have been curious about for a very, > very long time (hence my willingness to pay costs of evaluation of my > own use cases and compliance) is that I could not see how anyone can > make any money with any type of API that serves pure data, such as > what Translate API does. No matter how hard I tried, I could not see > how they could make any money with that, NO MATTER HOW BIG I MADE > THEIR "POWERED BY GOOGLE" LOGO. > > Having said that, if an old timer from COBOL and PUNCHED CARD days can > see and question such as business model then what on earth are they > paying for to their own business suits to do, if not to evaluate such > cases. Sure, tech people have done incredible work and for that I > respect them. The problem is most likely that the suits have not been > doing their part by constantly evaluating and business sense modelling > what the tech folks are cooking up. > > NEVER IN MY LIFE HAVE I HAD A MORE UNDERHANDED AND A MORE DISHONEST > EXPERIENCE THEN THIS ONE. > > > > > > > > On Fri, May 27, 2011 at 10:17 AM, urukay <radovan.be...@gmail.com> wrote: > > And the worst thing for me is that it looks like Google even haven't > > even tried to find better solution to this situation, maybe charge > > people for using API, for reasonable price of course. A lot of people > > and companies would buy access to Translate API. > > Well it's a shame. No more developer friendly Google. But on the other > > hand this abuse of Translation API has been made by some developers, > > so both sides take responsibility for this situation. > > > On May 27, 3:58 pm, Zdravko Gligic <zgli...@gmail.com> wrote: > >> Jeremy, that is indeed what I understood to be the case BUT ONLY AFTER > >> RADOVAN POINTED IT OUT and the reason why I asked is because I can not > >> believe that GOOG would be that irresponsible. This is worse than any > >> sort of malicious "bait and switch" that I have ever seen ANYWHARE! > > >> If they are shutting down ALL versions of Translate API then they have > >> engaged in an incredible case of SUCKER PUNCHING many of us out of > >> existence because the day when they announced v2 with it they sent out > >> an unmistakable signal that not only will Translate API NEVER BE SHUT > >> DOWN but that in fact it is BEING MADE BETTER. > > >> If that is the case then I am stopping all of my GOOG relaed > >> development, INCLUDING YOUTUBE, where I have been doing lots of great > >> work. > >> If that is the case then GOOG has just replace $MS$ as my new poster > >> child of GREED and BUSINESS STUPIDITY. > > >> Jeremy, please tell me THAT IT AINT SO ?!? > >> Please, at least tell me that they would have had decency to say so - > >> more explicitly. > >> Please, tell me that this is just one bad dream. > >> Please, tell me ANYTHING that would make me feel OK again, about them > >> as HUMAN BEINGS. > >> Please Jeremy! > > >> On Fri, May 27, 2011 at 9:47 AM, Jeremy Geerdes <jrgeer...@gmail.com> > >> wrote: > >> > You asked "how come they are not being equally explicit about it." My > >> > answer: because they're discontinuing BOTH versions of the Translate API. > > >> > Jeremy R. Geerdes > >> > Generally Cool Guy > >> > Des Moines, IA > > >> > For more information or a project quote: > >> > jrgeer...@gmail.com > > >> > If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan > >> > Church! > > >> > On May 27, 2011, at 8:42 AM, Zdravko Gligic wrote: > > >> >> Said with greatest personal respect ... > >> >> What the ____ are you saying Jeremy ?!? > > >> >> On Fri, May 27, 2011 at 9:36 AM, Jeremy Geerdes <jrgeer...@gmail.com> > >> >> wrote: > >> >>> Because they put deprecation notices on BOTH the v1 and v2 > >> >>> documentation. I.e., BOTH versions of the Translate API have been > >> >>> deprecated and will be discontinued come December. > > >> >>> Jeremy R. Geerdes > >> >>> Generally Cool Guy > >> >>> Des Moines, IA > > >> >>> For more information or a project quote: > >> >>> jrgeer...@gmail.com > > >> >>> If you're in the Des Moines, IA, area, check out Debra Heights > >> >>> Wesleyan Church! > > >> >>> On May 27, 2011, at 8:34 AM, Zdravko Gligic wrote: > > >> >>>> If in that link we zero in on this peice of text "... Safe Browsing > >> >>>> API (v1 only), Translate API, ..." then one gets sense that there is > >> >>>> more than one "Safe Browsing" version - so they are being very > >> >>>> explicit that only v1 is being shut down. Since we know that there is > >> >>>> more than one version of Translate API, how come they are not being > >> >>>> equally explicit about it. > > >> >>>> So, Radovan i correct. > > >> >>>> Pozdrav, > >> >>>> Zdravko > > >> >>>> On Fri, May 27, 2011 at 8:07 AM, urukay <radovan.be...@gmail.com> > >> >>>> wrote: > >> >>>>> but according > >> >>>>> thishttp://googlecode.blogspot.com/2011/05/spring-cleaning-for-some-of-ou... > >> >>>>> it looks like both version will be shutted down. > >> >>>>> Guess we will have to wait to see "how the story really goes". > >> >>>>> But thanks for bringing some light :) > > >> >>>>> Radovan > > >> >>>>> On May 27, 1:56 pm, Jeremy Geerdes <jrgeer...@gmail.com> wrote: > >> >>>>>> Correct. > > >> >>>>>> Jeremy R. Geerdes > >> >>>>>> Generally Cool Guy > >> >>>>>> Des Moines, IA > > >> >>>>>> For more information or a project quote: > >> >>>>>> jrgeer...@gmail.com > > >> >>>>>> If you're in the Des Moines, IA, area, check out Debra Heights > >> >>>>>> Wesleyan Church! > > >> >>>>>> On May 27, 2011, at 6:55 AM, urukay wrote: > > >> >>>>>>> So if I understand this right, API V2 will be available also after > >> >>>>>>> December? > > >> >>>>>>> On May 27, 1:47 pm, Jeremy Geerdes <jrgeer...@gmail.com> wrote: > >> >>>>>>>> The API will no longer be supported, effective immediately. In > >> >>>>>>>> other words, they will not be adding new features, and they will > >> >>>>>>>> not be fixing bugs. And the service will be terminated completely > >> >>>>>>>> in December. > > >> >>>>>>>> That said, this only affects the v1 Language APIs family. You can > >> >>>>>>>> still use the Translate API v2, for which you can sign up > >> >>>>>>>> athttp://code.google.com/apis/console. > > >> >>>>>>>> Jeremy R. Geerdes > >> >>>>>>>> Generally Cool Guy > >> >>>>>>>> Des Moines, IA > > >> >>>>>>>> For more information or a project quote: > >> >>>>>>>> jrgeer...@gmail.com > > >> >>>>>>>> If you're in the Des Moines, IA, area, check out Debra Heights > >> >>>>>>>> Wesleyan Church! > > >> >>>>>>>> On May 27, 2011, at 4:43 AM, urukay wrote: > > >> >>>>>>>>> well maybe both, but the problem is if API will be useless after > >> >>>>>>>>> 1st > >> >>>>>>>>> of December or not. Som Far it looks like we can use API, but > >> >>>>>>>>> under > >> >>>>>>>>> limited restrictions. The thing that confuses me that here > >> >>>>>>>>>http://code.google.com/intl/sk/apis/language/translate/overview.html > >> >>>>>>>>> the claim that there wil be shut off on 1st of December but here > >> >>>>>>>>>http://code.google.com/intl/sk/apis/language/translate/v2/getting_sta... > >> >>>>>>>>> there's only that they will not support it. So for me the main > >> >>>>>>>>> question is, can I use this API after December or not. If not i > >> >>>>>>>>> will > >> >>>>>>>>> stop using it right now. > > >> >>>>>>>>> I really don't like this announcement. > > >> >>>>>>>>> On 27. Máj, 11:37 h., Alex <alexander.mar...@gmail.com> wrote: > >> >>>>>>>>>> Does this affect only version 1 or also version 2? > > >> >>>>>>>>>> On May 27, 11:21 am, urukay <radovan.be...@gmail.com> wrote: > > >> >>>>>>>>>>> Google announced, that the Translate API will be depreceated > >> >>>>>>>>>>> from 1st > >> >>>>>>>>>>> Dec 2011, so it means that we will be not able to use it > >> >>>>>>>>>>> anymore or > >> >>>>>>>>>>> just Google will no longer maintain the API? > > >> >>>>>>>>>>> Thanks > > >> >>>>>>>>>>> R. > > >> >>>>>>>>> -- > >> >>>>>>>>> You received this message because you are subscribed to the > >> >>>>>>>>> Google Groups "Google AJAX APIs" group. > >> >>>>>>>>> To post to this group, send email to > >> >>>>>>>>> google-ajax-search-api@googlegroups.com. > >> >>>>>>>>> To unsubscribe from this group, send email to > >> >>>>>>>>> google-ajax-search-api+unsubscr...@googlegroups.com. > >> >>>>>>>>> For more options, visit this group > >> >>>>>>>>> athttp://groups.google.com/group/google-ajax-search-api?hl=en. > > >> >>>>>>> -- > >> >>>>>>> You received this message because you are subscribed to the Google > >> >>>>>>> Groups "Google AJAX APIs" group. > >> >>>>>>> To post to this group, send email to > >> >>>>>>> google-ajax-search-api@googlegroups.com. > >> >>>>>>> To unsubscribe from this group, send email to > >> >>>>>>> google-ajax-search-api+unsubscr...@googlegroups.com. > >> >>>>>>> For more options, visit this group > >> >>>>>>> athttp://groups.google.com/group/google-ajax-search-api?hl=en. > > >> >>>>> -- > >> >>>>> You received this message because you are subscribed to the Google > >> >>>>> Groups "Google AJAX APIs" group. > >> >>>>> To post to this group, send email to > >> >>>>> google-ajax-search-api@googlegroups.com. > >> >>>>> To unsubscribe from this group, send email to > >> >>>>> google-ajax-search-api+unsubscr...@googlegroups.com. > >> >>>>> For more options, visit this group > >> >>>>> athttp://groups.google.com/group/google-ajax-search-api?hl=en. > > >> >>>> -- > >> >>>> You received this message because you are subscribed to the Google > >> >>>> Groups "Google AJAX APIs" group. > >> >>>> To post to this group, send email to > >> >>>> google-ajax-search-api@googlegroups.com. > >> >>>> To unsubscribe from this group, send email to > >> >>>> google-ajax-search-api+unsubscr...@googlegroups.com. > > ... > > read more »
-- You received this message because you are subscribed to the Google Groups "Google AJAX APIs" group. To post to this group, send email to google-ajax-search-api@googlegroups.com. To unsubscribe from this group, send email to google-ajax-search-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-ajax-search-api?hl=en.
