2011-05-09, 08:29 PM
MS right now reminds me alot of Diablo 1. The thing was a paradise for people modifying how the program sent data because a huge portion of the program ran client side.
What confuses me more then anything, I can understand why MS uses so much clientside processing. making the user do more work means cheaper server costs. But when this has become such a common occurance you'd think they'd have more then faulty and easily avoided countermesures. You can spend 5 min on GK and see just how easy it is to counteract all their safeguards.
The problem has become endemic though. A portion of the userbase likes it because it reduces the cost of things, letting them get better equips at a much lower cost. Actually stopping the hackers would realisticly require a complete recode of MS's client and server engines. obviously way beyond what any smart company is willing to do.
So you need to reactively deal with situations. Fine. but why in gods name, when you know this problem has come up do you wait 3 days, THEN deal with the situation with a response that basicly became harsher by your own inaction? :f6:
This is the part that confuses me, why wait? Why not push the big red stop button days ago, call in the coders from the weekend and fix the problem before you have to inconvince EVERYONE for your own inaction/stupidity?
Sadly it's easy to figure out why though. It doesn't matter. The small number of people who were actually negatively effected by this are a fraction of their users and their money.
It's pretty obvious as long as they keep making money they could care less, and thats really irritating. No amount of angry e-mails will change that.
What confuses me more then anything, I can understand why MS uses so much clientside processing. making the user do more work means cheaper server costs. But when this has become such a common occurance you'd think they'd have more then faulty and easily avoided countermesures. You can spend 5 min on GK and see just how easy it is to counteract all their safeguards.
The problem has become endemic though. A portion of the userbase likes it because it reduces the cost of things, letting them get better equips at a much lower cost. Actually stopping the hackers would realisticly require a complete recode of MS's client and server engines. obviously way beyond what any smart company is willing to do.
So you need to reactively deal with situations. Fine. but why in gods name, when you know this problem has come up do you wait 3 days, THEN deal with the situation with a response that basicly became harsher by your own inaction? :f6:
This is the part that confuses me, why wait? Why not push the big red stop button days ago, call in the coders from the weekend and fix the problem before you have to inconvince EVERYONE for your own inaction/stupidity?
Sadly it's easy to figure out why though. It doesn't matter. The small number of people who were actually negatively effected by this are a fraction of their users and their money.
It's pretty obvious as long as they keep making money they could care less, and thats really irritating. No amount of angry e-mails will change that.