Instead of being mothballed, perhaps they should in some way be set up on GAE, where its usage could be metered and billed. Perhaps a decent free amount of use would be allocated and then maybe even some preferential rates applied - if there are any economies of scale, where many apps are using common infrastructure.
Has any of this been considered ?!? If not then what about at least doing the next best honorable thing and releasing both the software and data - where it could be, such as likely in Translate API. Perhaps then its upkeep could continue as open source projects. Or perhaps you are afraid that somebody else may end up making it work and using it in a business model - because they bothered to come up with a business model. All of this reminds me of WAVE. What a fantastic piece of work and what a fantastic concept. Too bad that nobody at GOOG bothered to AGAIN come up with a business model that would be feasible. Heck, all one needs to look at is FACEBOOK, where gazzilions of people are wasting their lives doing totally useless things. Throw in the WAVE and integrate it will GOO's other vast reaching infrastructure and in no time EVEN I could come up with dozens of feasible models. THE MORE THAT I THINK ABOUT ALL OF THIS THE MORE I AM GETTING TOTALLY DISGUSTED WITH THE WHOLE SAD EXPERIENCE ! On Fri, May 27, 2011 at 2:32 PM, Joshua Pilkington <joshua.pilking...@gmail.com> wrote: > Perhaps these APIs should be set up in a way that requires user > authentication, such as the Facebook and Flickr APIs. That should cut > down on the abuse. > > On May 27, 2:22 pm, Adam Feldman <adam.feld...@google.com> wrote: >> Hi Mark, >> >> When we created the Search APIs many years ago, we hoped that they would >> help developers create innovative websites and applications that provide >> value to end users. Unfortunately, we've found that most requests to these >> APIs involve scraping, data mining, or other usage that doesn't improve the >> end users' experience. Because we've failed in this respect, we've decided >> to deprecate them. I understand that not everyone was misusing them in >> these ways - and certainly don't mean to imply otherwise! I feel for those >> who are doing great things here, but there simply aren't enough of you to >> allow us to continue supporting these APIs. >> >> Thanks for your understanding, >> Adam >> >> On Fri, May 27, 2011 at 9:21 AM, Mark Essel (@victusfate) >> <mes...@gmail.com>wrote: >> >> >> >> >> >> >> >> > Anyone understand why this is being deprecated? Read the official post >> > and specifics but no details. >> >> > Well used Apis become infrastructure, the removal of apis sends a >> > clear signal for the future. >> >> > -- >> > 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. > > -- > 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. > > -- 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.
