Skip to Content

WoW Insider has the latest on the Mists of Pandaria!
  • Xandrir
  • Member Since Dec 6th, 2010

Are you Xandrir? If So, Login Here.

WoW14 Comments

Recent Comments:

Heart of the Aspects video and giveaway {WoW}

Feb 15th 2012 9:46AM Mount plzkthx!

Gold Capped: A tailoring leveling guide {WoW}

Dec 23rd 2011 5:02PM Good point, predets. This article was more about how to level the profession to make money, not mainly level the profession. Wasn't trying to troll, just provide useful information. :)

Gold Capped: A tailoring leveling guide {WoW}

Dec 23rd 2011 4:38PM Excellent article, however...

Been using this for any profession leveling I need to do on any character.

12 Days of Winter Veil Giveaway: BlizzCon Exclusive Murkablo {WoW}

Dec 15th 2011 5:37PM Yes please and thank you!

Blizzard releases third-party API usage policy {WoW}

Dec 14th 2011 9:03PM "So basically, Blizzard wants people to work for free (or for whatever pittance advertisement views pay).

That's entirely their prerogative, but it certainly puts a damper on the incentive to provide innovative services."

All Blizzard is saying is that you can't charge a price for access to the data. Makes good business sense, once you think about it. If someone is out there making money hand over fist because of a service that you (as a business) provide, and you aren't seeing a dime, you'd either A) shut them down immediately or B) work out a deal where you get a cut of revenue. Since the API is publicly available, Blizzard isn't going to make you have a business deal with them just to use the API, so they simply make you agree not to charge for access to said service/data.

It's a business decision, and a very common one these days concerning public API's. As a software developer, services like this are awesome to have on hand. Blizzard is not enforcing you to work for free. If you want to make a website that creates revenue, Blizzard is simply stating that you cannot put their data behind your cost of access.

I can certainly see where non-developers would see this as undesirable, but trust me. As a developer, these kinds of restrictions and open source licensing agreements are pretty standard, and this in particular is rather common.