[BS] BlogSenseWp switches from Google Translation API service to Bing Translation API service.

BlogSense supports Bing Translation API! Hello! Over the last month, anyone working with the translation features of BlogSense may have noticed that campaigns were halted because of the inability to translate content. The news related to this phenomenon is that Google has disabled their free API based translation service in favor for a paid translation service. It is our intention to eventually offer the option to either use Bing’s free service or Google’s paid service, but for now we have introduced Bing’s API based service to restore translation features back to BlogSense users. Which service is better? I have no clue and have done zero case studies. One would think that because of weath & pride, Google would produce a superior translation service, but hey, Microsoft is a pretty altruistic and powerful company as well. It just might be that Bing’s service is superior! API limitations and throttling BlogSense does provide an application ID for global use, but there are use limitations available to each APIKey. It might be prudent to grab your own APIKey from Bing.com. BlogSense provides a settings area within the Automation->Global Settings area where you can paste in and overwrite the default api key with your [...]

BlogSenseWp switches from Google Translation API service to Bing Translation API service.