Hey Carter -- The CSE Element was launched at Google I/O, and it was announced with ads. It has never not had ads, so we're not serving up an unwanted surprise. I apologize if there was any confusion.
Thanks, Ben On Tue, Aug 11, 2009 at 6:04 AM, Vision Jinx <[email protected]> wrote: > > Hey Jeremy! :) > > Yeah, that's what I kinda figured as well. I was helping someone with > a CSE example and the first draft when I posted it didn't show ads but > when I went back to add some updates to it PLOP ads in my face once > again. > > I do get that some ppl want to add ads in the API so can see Google > adding the ability for revenue sharing but I sure hope they are not > forcing them on us (like in the early days) and I am interested to see > how they plan on adding them in the RESTful API since I can parse the > JSON data how I wish and there is/was no stipulation saying I much > parse and use all the json data provided. > > But on the other hand I don't like these surprises at all and if I was > using the Google loaders in my apps then with out notice I had ads > once again that would (for me anyways) be a sure fire way to drop this > API once and for all. Also, since so many people have added this api > to their sites then to make an un-announced change like this is pretty > low IMHO. :/ Just like how Digg did the URL hijacking after millions > have used their URL shortner service to point to their pages/articles > only to later have Digg redirect them all to their site (to increase > the number of ads they serve) or the same with AT&T recently modifying > their TOS with out notice to prevent people from filing class action > law suits against them... This just makes one loose all trust in a > company with these techniques. (again IMHO) > > Well, anyways hoping to hear what Ben has to say on it and will chat > with ya more in the IRC man! :P > > > On Aug 11, 6:29 am, Jeremy Geerdes <[email protected]> wrote: > > Well, I have good news and bad news. The good news is that the example > > you linked to is a CSE Custom Search Control. Since one of the big > > reasons people use the Custom Search Engine is to take advantage of > > its ability to utilize AdSense, and CSE results have ads in them > > either way, it seems an appropriate addition to the Custom Search > > Control. The bottom line here is that ads are not (yet?) included with > > a default search control or other search results. The second url that > > you provided would appear to be an as-yet undocumented Ads API which > > is apparently designed as a companion to the Search API. > > > > That said, the bad news is that the Search API's TOU do clearly > > indicate that Google has the right to include ads among the results. > > So there is no guarantee that they won't end up forcing ads on us at > > some point in the future. > > > > Jeremy R. Geerdes > > Effective website design & development > > Des Moines, IA > > > > For more information or a project quote:http:/ > /jgeerdes.home.mchsi.comhttp://jgeerdes.blogspot.comhttp:// > jgeerdes.wordpress.com > > [email protected] > > > > Unless otherwise noted, any price quotes contained within this > > communication are given in US dollars. > > > > If you're in the Des Moines, IA, area, check out Debra Heights > > Wesleyan Church! > > > > And check out my blog, Adventures in Web Development, athttp:// > jgeerdes.blogspot.com > > ! > > > > On Aug 11, 2009, at 3:51 AM, Vision Jinx wrote: > > > > > > > > > I remember in the very early days of this API there use to be ads and > > > after a lot of posts against them Google removed them from the API. > > > > > Now I am seeing these ads again across the top and side bar. (run a > > > search for 'ajax') > > > > >http://savedbythegoog.appspot.com/?id=ag5zYXZlZGJ5dGhlZ29vZ3ISCxIJU2F. > .. > > > > > I hate ads (as much as jgeerdes hates IE) and want to know if Google > > > is going to be forcing ads on ppl again. If this is so, I would like > > > to know asap so I can drop yet another Google service once and for all > > > and will no longer be supporting this API either as a result (just > > > like I did with the Gadgets API). > > > > > Also, if using the JSON/JSONP Restful api do I need to display them > > > again like in the old days or opt to not at all? Has there been an un- > > > announced TOS change regarding this and what are Googles plans for > > > this? Since I am not doing this as part of AdSense revenue sharing I > > > don't want ads at all on my site, while I can see those who insist on > > > plastering their results with advertisements have asked for this > > > ability. Fine, I don't have to use their pages or results but > > > seriously don't want them in mine. > > > > > Google (Ben), can you please comment on this for me (or send me an > > > email), you know I have been an API supporter since day one but this > > > will be a deal breaker for me I am afraid. > > > > > Also, what other aspect of this API do you plan on plastering unwanted > > > ads in (feed, translation etc etc)? > > > > > Offending code is this... > > > > >http://ajax.googleapis.com/ajax/services/ads/afs?q=ajax&hl=en&ad=n4&s. > .. > > > > > This is exactly why I don't use the Google loaders and only use the > > > RESTful aspects of the API so I don't get these unwanted surprises. > > > Time to check out Bing or something else I guess. But I really hate > > > these un-announced surprised and am losing a lot of respect for Google > > > as a result. :( > > > > > Regards, > > > Vision Jinx > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google AJAX APIs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-AJAX-Search-API?hl=en -~----------~----~----~----~------~----~------~--~---
