I'd like to see the Blizzboys' faces when they are notified of this. they've sure given us tons of reasons to frown, it's about time we returned the favor.
Actually it's in Blizz's best interest to let this information remain up on Diablofans.com
It's free Hype and PR for them.
Even with it being in alpha testing they can very very easily pull all of the Data files we have access to. All they would need to do is push out a new TFIL file to their alpha testers with either new file locations on their CDNs or it redirected to another CDN then remove it from the current CDNs and *boom* gone from public view. In fact they could probably host it on their own in-house CDN which we have no access to.
lol guys use your brain and google, you can download D3 RoS early Beta binaries from ownedcore.
I wouldn't trust a filebeam URL especially one coming from ownedcore. There are direct download links you can get that use the same CDN servers Blizzards uses and have been uploaded by Blizzard.
What is the source for all this? Where was all this data uploaded to? Usually datamined info is released when the files are uploaded to the PTR servers or LIVE servers, right?
Ok I'll tell you but I'm not going to post links as I'm not sure Diablofans would allow me to do so.
Blizzard has a set of CDNS servers across 3 providers. When you download via their installers or via the launcher there's always a http download stream from one of these servers. It doesn't matter if your installing a PTR , a beta or something that's live , the original source will be on one of these CDN servers. So before it goes live to the PTR , Beta or Live Live it gets uploaded to these servers.
Now each "type" of download has a program identifier. Wow is "Wow" , WoW PTR is "WoWT" , Wow beta is "WowB" , SC2 is "SC2" , SC2 beta is "SC2B" on so on and so forth. So if we were looking for a Diablo 3 beta the identifier would be "D3B"
Now if you know where certain headers are stored and know the arcane art of reading & interpreting them you can use it to glom together a direct download link to patch files and hence download patch files without need of a installer or launcher. That unfortunately isn't me.
But I do have a friend that has a bot that watches for changes in amongst the CDN servers and sends an email out for any changes it sees. On the 10th September @ 21:30 GMT it sent one out "New build for D3B - enUS: 19080" then on the 11th @ 20:50 GMT it sent out another for "New build for D3B - enUS: 19177"
I've been scratching my head over the last two days trying to figure out what it was. The emails do have direct download links to MPQ files but I'm not sure if I'm allowed to post such links. I honestly thought it had something to do with a PC based client for the Console version of Diablo 3 (hey don't hate ! I don't follow the news on Diablo 3 that closely >_> )
But rest assured this info has a very good probability to be true - there are MPQ patch files out there for a "D3B" that , as I've explained above has to do with a Diablo 3 beta.
I'm afraid I'm over my bandwidth cap right now so will be using direct download manual links so I can download at work.
What do I mean by direct links ? Bypassing the Blizzard Launcher that is.
At work I can't install any programs. I can however operate a web browser just fine. Using the MFIL file in the Diablo Public Test file I can construct URLs for the MPQ that make up a bulk of the download.
what's the build number? It'll take me hours to find the files trying one buid number incriments at this rate it seems
Oh hai.
Couldn't catch up with you via our normal ways but there's several reasons why it may not necessarily take you "hours"
1) The builds don't usually jump up that high. Usually less then around 250 - 300 or so. The jump from 9558 to 9858 was the biggest i've seen in Blizzard builds. You won't need to cycle through thousands of them.
2) If a file doesn't exist on the CDN servers it will give a response "Not found" of around 15 bytes.
3) When files are uploaded to the CDN servers they usually mirror to the other CDN servers Blizzard uses. IIRC Blizzard has 3 of them - Blizzard's own CDN , Limelight and Akamai. There might be one more but I haven't looked through patch header files lightly.
So IMHO let's say a few SSH remote terminal sessions with the downloading being spread over the 3 CDNs in blocks and it shouldn't take that long
With Global Play connecting to a region that has a different patch installed causes patch looping issues. So if the Asian forums are getting it on June 7th then all servers will be as well.
Blue posters haven't come forth to say "hey there now you guys don't you download our stuff now!", and it's been 6-8+ hrs since the leak. If they were REALLY bothered by the leak, they'd have said something or warned people the consequences of downloading it before given the go-ahead. The argument "they didn't safeguard it better so it makes it right" isn't exactly a valid argument, but really in all honesty who wasn't surprised there'd be some kinda leak?
^^ This.
It's on one of Blizzard's Akamai streaming servers. If they really wanted to they could delete it off their servers. There's no way they're not aware of it being downloaded right now.
But in saying that I've never had to post something on a CDN or on an Akamai server so I don't know how long it takes to remove something off them and if they need to wait for a delete command to propagate down each and every redundant server.
They wont have to find your bnet account info if you downloaded and ran the Beta profile tool program you've already "bound" your networkcard's MAC adress to that profile, and they could just match it up with info of who has connected too the client downloader.
I doubt they'll do that thou, but if your paranoid i'd dl the client on another pc than the one you ran the profile tool on Or atleast plug in another networkcard
Last time I checked it doesn't log your Mac address or IP address on the beta profile tool. It's just a simple hardware check attached to a web form AFAIK.
As it's being downloaded via a CDN it may be more difficult to track people if the CDN isn't specifically logging IP addresses. Not impossible just slightly more difficult.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
http://www.reddit.com/r/Diablo/comments/1mbqwu/datamine_reaper_of_souls_login_screen_screenshot/
I would go check Reddit's subreddits to see if you can find more info.
Actually it's in Blizz's best interest to let this information remain up on Diablofans.com
It's free Hype and PR for them.
Even with it being in alpha testing they can very very easily pull all of the Data files we have access to. All they would need to do is push out a new TFIL file to their alpha testers with either new file locations on their CDNs or it redirected to another CDN then remove it from the current CDNs and *boom* gone from public view. In fact they could probably host it on their own in-house CDN which we have no access to.
Not by me. I really hate it when people use "100%" as a bludgeon to get their point across or to make their point sound better or more honest.
You can if you like. I'm busy in another Google Docs account so I really don't want to log over to my other email to get them
I wouldn't trust a filebeam URL especially one coming from ownedcore. There are direct download links you can get that use the same CDN servers Blizzards uses and have been uploaded by Blizzard.
Ok I'll tell you but I'm not going to post links as I'm not sure Diablofans would allow me to do so.
Blizzard has a set of CDNS servers across 3 providers. When you download via their installers or via the launcher there's always a http download stream from one of these servers. It doesn't matter if your installing a PTR , a beta or something that's live , the original source will be on one of these CDN servers. So before it goes live to the PTR , Beta or Live Live it gets uploaded to these servers.
Now each "type" of download has a program identifier. Wow is "Wow" , WoW PTR is "WoWT" , Wow beta is "WowB" , SC2 is "SC2" , SC2 beta is "SC2B" on so on and so forth. So if we were looking for a Diablo 3 beta the identifier would be "D3B"
Now if you know where certain headers are stored and know the arcane art of reading & interpreting them you can use it to glom together a direct download link to patch files and hence download patch files without need of a installer or launcher. That unfortunately isn't me.
But I do have a friend that has a bot that watches for changes in amongst the CDN servers and sends an email out for any changes it sees. On the 10th September @ 21:30 GMT it sent one out "New build for D3B - enUS: 19080" then on the 11th @ 20:50 GMT it sent out another for "New build for D3B - enUS: 19177"
I've been scratching my head over the last two days trying to figure out what it was. The emails do have direct download links to MPQ files but I'm not sure if I'm allowed to post such links. I honestly thought it had something to do with a PC based client for the Console version of Diablo 3 (hey don't hate ! I don't follow the news on Diablo 3 that closely >_> )
But rest assured this info has a very good probability to be true - there are MPQ patch files out there for a "D3B" that , as I've explained above has to do with a Diablo 3 beta.
I'm afraid I'm over my bandwidth cap right now so will be using direct download manual links so I can download at work.
What do I mean by direct links ? Bypassing the Blizzard Launcher that is.
At work I can't install any programs. I can however operate a web browser just fine. Using the MFIL file in the Diablo Public Test file I can construct URLs for the MPQ that make up a bulk of the download.
EG
http://dist.blizzard.com.edgesuite.net/d3-pod/public-test/Global/10485.direct/Data_D3/PC/MPQs/base/d3-update-base-12150.MPQ
So I just download every file listed in the MFIL URL manually at work.
Of course if it works once I get all those files home and copied into the appropriate areas is another story
Oh hai.
Couldn't catch up with you via our normal ways but there's several reasons why it may not necessarily take you "hours"
1) The builds don't usually jump up that high. Usually less then around 250 - 300 or so. The jump from 9558 to 9858 was the biggest i've seen in Blizzard builds. You won't need to cycle through thousands of them.
2) If a file doesn't exist on the CDN servers it will give a response "Not found" of around 15 bytes.
3) When files are uploaded to the CDN servers they usually mirror to the other CDN servers Blizzard uses. IIRC Blizzard has 3 of them - Blizzard's own CDN , Limelight and Akamai. There might be one more but I haven't looked through patch header files lightly.
So IMHO let's say a few SSH remote terminal sessions with the downloading being spread over the 3 CDNs in blocks and it shouldn't take that long
Heh that didn't take long
http://translate.google.com/translate?sl=auto&tl=en&js=n&prev=_t&hl=en&ie=UTF-8&layout=2&eotf=1&u=http%3A%2F%2Fkr.battle.net%2Fd3%2Fko%2Fforum%2F1603657%2F
With Global Play connecting to a region that has a different patch installed causes patch looping issues. So if the Asian forums are getting it on June 7th then all servers will be as well.
http://kr.battle.net/d3/ko/forum/topic/1582255623
http://translate.googleusercontent.com/translate_c?hl=en&ie=UTF8&prev=_t&rurl=translate.google.com&sl=auto&tl=en&twu=1&u=http://kr.battle.net/d3/ko/forum/topic/1582255623&usg=ALkJrhijC3bSgso-Zyxdnm6B_TqCVaOKIQ
"1.0.2A PATCH AND RESTARTING THE SERVER GUIDE 31.05 - COMPLETE"
Can someone who can read korean give us a proper translation and not just the google translation ?
Querying the korean patch servers a certain way comes back with build 9858 being live over there . not 9745 as the US servers return.
It's on one of Blizzard's Akamai streaming servers. If they really wanted to they could delete it off their servers. There's no way they're not aware of it being downloaded right now.
But in saying that I've never had to post something on a CDN or on an Akamai server so I don't know how long it takes to remove something off them and if they need to wait for a delete command to propagate down each and every redundant server.
Last time I checked it doesn't log your Mac address or IP address on the beta profile tool. It's just a simple hardware check attached to a web form AFAIK.
As it's being downloaded via a CDN it may be more difficult to track people if the CDN isn't specifically logging IP addresses. Not impossible just slightly more difficult.