The download using Mega looks interesting. Seems that it is using the HTML5 FileSystem API to first download the file to a temporary location, without even showing a browser download dialog to the user.
In case anyone is interested, the reason it does that is that the file is encrypted on the server and decrypted clientside in javascript. The decryption key is in the link's hashtag.
I can say when I saw that I candled out and just started torrenting it. It is a large file and I rather know where it was going and not on my ssd system drive.
Comments
The download using Mega looks interesting. Seems that it is using the HTML5 FileSystem API to first download the file to a temporary location, without even showing a browser download dialog to the user.
Someone created a thread on stackoverflow about this, but unfortunately it was closed: http://stackoverflow.com/questions/14923098/how-does-mega-co...
In case anyone is interested, the reason it does that is that the file is encrypted on the server and decrypted clientside in javascript. The decryption key is in the link's hashtag.
I can say when I saw that I candled out and just started torrenting it. It is a large file and I rather know where it was going and not on my ssd system drive.
Downloading from mega failed for me with an "encryption error". So using Bittorrent seems to be the better option here anyway.
I'm not familiar with that use of the verb "candle"? Is that a regional thing?
It is indeed, then it will use blob uris to switch to a normal "download", which really will copy the file locally on your drive.