Jan 1st 2009 2:45AM The obvious answer would be those who refuse to run Windows.
Nov 11th 2008 10:13PM Moar QQ. Please.
Yeah, I'm guessing something bad happened at Bliz. Happens when you made the sad choice to hire people. They make mistakes, or fail to predict the future perfectly.
The whiners should check the burgers they're flipping. I'd bet some of them are burned.
And I'll bet a burger Bliz responds to the screwup honorably. It's what they always do.
Oct 2nd 2008 5:41PM As I recall Northrend is about twice the size of Outland.
Oct 2nd 2008 5:40PM As I recall Northrend is about twice the size of Outland.
Aug 30th 2008 2:49PM I think you've missed a path for DK's - I very much suspect there will be groups / guilds who work their existing mains to 80, then go back and power level a DK with friends. That's certainly our plan, and while that does mean your points about running the Outland instances and learning to play the DK class are correct, those power leveled DK's will start to show up en masse in Northrend after a delay for the 80's to level.
Jul 25th 2008 10:26AM Say what? Addons are incapable of doing I/O except to saved variables, and they don't load until well after you've typed the password and the authenticator code. Whatever happened in the case cited in the article, it wasn't the fault of an addon.
The *closest* your comment gets to being on topic is that there have and can be problems with the automatic updaters some sites promote, and some of the addon sites have had malware injected (such as through hosted advertising). If you use an autoupdater, which is an exe on a PC, you're an idiot asking to be owned. That exe could contain anything, and you have no way to know.
Beyond that, Blizz would only be better protected aginst malware injection if they're site staff is well trained in security procedures. There's nothing inherent in owning the game IP that would make their site more secure.
My vote for what happened is a combination of a keylogger and a mistake by a support rep.
Jul 11th 2008 7:51PM Keep me in mind when you get owned, because it's just a matter of time until you do, and mocking really is a spectator sport. No anti-spyware, no anti-virus - how would you actually *know* you're not already owned?
Anyhow, our authenticators came today, and I discovered something I'd now known about them - they also secure access to account management on the Bliz site. Sweet.
Jun 28th 2008 8:51PM Similar devices have been defeated. One of the attacks is called man in the middle - it amounts to getting into the network flow between user and server, and letting you compromise things for yourself. It can be done, such as by a successful hack of the DNS servers.
Likely? I don't know. Possible? Yes, and without compromising your computer itself. Don't ever think there's going to be uncrackable security.
Jun 8th 2008 1:17PM There are so many things you can do with macros by using /script. Did you ever wonder how much network bandwidth WoW uses? Try this macro. There are two lines, each starting with /script. Results are in 1000's of bits per second.
/script DEFAULT_CHAT_FRAME:AddMessage(format("In: %i Kbps, Out: %i Kbps, Latency: %i ms",i*8,o*8,l))
Mar 8th 2008 9:29PM This doesn't make complete sense. If you know it's in progress, why can't you immediately change the PW on the Blizz site, then log in. That dumps the current player, and with the account PW changed they're locked out.
So how does this make sense as told?