Safe for public games yet?

I apologize if this was covered earlier, I did lok back several pages but couldn't find anything.

Ahem, Hi all,

Now I was a huge fan of D2 back in the day and played more than one really should. We're talking like waking up super earlier before the bus came to do baal runs. I know I am probably not alone in that but you see where I'm coming from in my enthusiasm for the series.

Now I played and beat D3 with my barb (although only just reached the last act in Nightmare) and I'm hitting a wall. For me the fun of D2 was in its multiplayer. I loved going through that list of games of "trist runs," "Itelebaals," and the like. However this is missing from D3. I miss being able to create a game and have people join. Now I know you can make your game public but last I heard (granted I've been out of touch for a while now) it was unsafe and could lead to your account being hacked if you made you games public.

Now I know people will probably say tings like "get an authenticator" or something but I remember in an earlier topic weeks ago that even people with authenticators were being hacked. All I want to know is can I play with other people? The game quickly loses its fun if I'm slogging through this by myself and my friends have stopped playing.

It's just a real bummer that I've (we've) waited so long and yet I can't yet fully enjoy it. I mean times have changed, my D2 obsession is at least six or seven years behind me and I don't have the fre time of a high school student to play... but damn. I mean the game is a blast to play but as I said, playing alone really just doesn't do it for me anymore.

People never got hacked from public games. That's impossible. People got hacked most likely because they registered to different websites with the same username/password as their battle.net account, and those websites in turn got hacked. Same thing happened alot in WoW because of random questionable guildsites and whatnot.

You're safe now, one of Blizzard's many patches covered up the session ID weakness that bypassed authenthicators. When the similar thing in Diablo 2 went down they went sort of public with what happened and how they fixed it, but they weren't part of "HUSH, EVERYTHING IS FINE" Activision then.

You're safe now, one of Blizzard's many patches covered up the session ID weakness that bypassed authenthicators. When the similar thing in Diablo 2 went down they went sort of public with what happened and how they fixed it, but they weren't part of "HUSH, EVERYTHING IS FINE" Activision then.

There wasn't one instance reported of someone with an authenticator getting hacked.

You're safe now, one of Blizzard's many patches covered up the session ID weakness that bypassed authenthicators. When the similar thing in Diablo 2 went down they went sort of public with what happened and how they fixed it, but they weren't part of "HUSH, EVERYTHING IS FINE" Activision then.

That session ID stuff was made up technically incompetent people. It never happened and all of the compromised accounts were due to stolen passwords.

You're safe now, one of Blizzard's many patches covered up the session ID weakness that bypassed authenthicators. When the similar thing in Diablo 2 went down they went sort of public with what happened and how they fixed it, but they weren't part of "HUSH, EVERYTHING IS FINE" Activision then.

Know what i've never seen or heard of? One youtube video showing someone doing the session ID hijacking thing. Not one. You're telling me that if this was a real thing that could be done, no one would document doing it for posterity? Diablo 2 had way more client side activity going on the 3 does. That's one of the reasons Blizzard went the route they did with 3.