Shaun, I personally find this implementation a little disturbing. First it should have been communicated better. I found it by reading a thrid party blog. My issue is if I would have implemented this on my school site then I would have been in a lot of trouble. We have strict policies about advertising on our websites to the point that its almost an act of congress to link out to almost any website that is not a Goverment, Library or other non-profit. I would have had some explaining to do. I'm sure I'm not the only one who runs a DNN site in a Educational or Goverment entity that probably have similar polices in place.

Second its possible if this had been implemented and the right people within the state of Georgia found out about it, then they would probably come after DotNetNuke Corp for payment of Bandwidth usage. Its happened before just do a search for Georgia sues for Seti Software. Just something to think about.

Now I personally would not mind donating a portion of Adsense revenue back to the project, but there needs to be an option and since I use my Adsense revenue to pay for hosting and buying an occasional gift for my wife, I could not donate it all, but I would not mind a percentage. This can be done through code and there are several Wordpress plugins that do this very thing.

Bruce

I am also wondering this implementation is ok with Adsense TOS, it also makes some skins' layouts dirty. Need to fix :(

I'm quite pleased to see the multiple search target option, though I agree that this could have been better communicated and perhaps configured FALSE by default.  But hey, we are where we are and there's plenty of info about how to 'repair' skins to disable the web search box.  I have some sites where this would be appropriate and some that are not.

Turning the sentiment around to be positive; I have a question about how to fix skins that are broken by this new feature.  I've been unable to track down how to fix the css referred to in by this change.  Is there a note somewhere about how to do this?  Would this 'fix' work for html, ascx and css-centric skins? 

The break I refer to manifests itself as a wide white box around the each radio button itself, and completely spoils the search box/td layout.