freitasm:

Talkiet: Found this in the privacy policy...

"Your data is encrypted by you before upload to our system and therefore we do not and cannot access that content unless we are provided with the decryption key. You may give access to others by providing them with a link and decryption key and you shall be responsible for their compliance with this Policy."

So I guess the local uploader also sends a hash made from a common algorithm.

If that's the case, then someone on Mega's network could collect hashes from popular current torrent files themselves and learn what is being uploaded.

Yeah, I love a good conspiracy theory :-)

Cheers -N

It could be done like that. But I still don't understand one thing: if they create an encryption key (probably a private/public pair) where is the key stored? If they store the key somewhere then they have access to it and can decrypt the files. If they store in the browser then it can easily disappear with all the data being lost forever if the browser is removed (computer fault, etc).

sorceror: they would only store the public key and associate it with your account/uploaded file, whereas the private key would be generated client side from the password.

DjShadow: Has anyone received a confirmation e-mail from signing up to a free account? I'm still waiting for mine from 5 hours ago

DjShadow: Has anyone received a confirmation e-mail from signing up to a free account? I'm still waiting for mine from 5 hours ago

DjShadow: Has anyone received a confirmation e-mail from signing up to a free account? I'm still waiting for mine from 5 hours ago

Development roadmap

Time flies when building a website, and unfortunately, half of the launch feature list that we envisioned when we started implementing MEGA back in September has now turned into a post-launch development roadmap. These are the essentials that we will work on next:

Developer documentation enhancements:

• Properly reformat and comment the JavaScript reference implementation so that it becomes more readable
• Add missing command-specific documentation to the API reference

 

File transfer queue enhancements:

• Vertical resizing
• Drag & Drop to modify transfer sequence
• Multiselect
• Clicking on a pending transfer navigates to/marks the source file or the target folder
• Stop/continue buttons

 

File manager enhancements:

• Re-implement from scratch without underlying third-party UI framework for better performance
• Adaptively eliminate the leftmost file path buttons at the top to maintain visibility of the upload and search buttons (we have a hack in place for this, but it only works in Chrome)
• "Properties" option in the file context menu

 

Collaboration feature enhancements:

• MEGA user-to-user messaging with file attachments, plus external RFC 4880/OpenPGP and S/MIME gateway for secure off-site e-mail communication
• MEGA user-to-user instant messaging
• Exported link enhancements
• Allow for the creation of folder links (with associated crypto key) which then display the folder content live
• Secure unauthenticated delivery web widget
• Allow unauthenticated users to securely deliver files to MEGA users' inboxes, e.g. to submit very large files to print shops

 

Filesystem enhancements:

• Activate storing all block MACs on the server (encrypted) after an upload to allow for integrity-checked partial reading. Right now, the file has to be downloaded fully to be checked.
• Enable forking encrypted time-stamped delta file support to allow for random writing to existing files with full rollback capability

 

SDK enhancements

• Complete the API documentation
• Provide client libraries in various languages

 

Client applications

• A Windows filesystem mount is currently in beta and will be available shortly
• Linux/MacOS X filesystem mounts
• Mobile access
• Sync tools for all major platforms

 

Integrated on-site applications

• Calendar
• Word processing
• Spreadsheet

 

MEGA as a local "appliance"

• Load a third-party audited version of the MEGA JavaScript files from a machine that you control
• Be immune against new bugs of any kind

MattR: Those of you still waiting for the confirmation email, you wouldn't happen to be using Microsoft email addresses, would you? It looks like MS aren't delivering mega's email.

Try a google email address, it'll come through very quickly.

Anybody having trouble trying to get to the website, try https://mega.co.nz

gareth41: upload speed to mega fluctuating a bit and im on UFB, started at around 60kb/s, now upto 250kb/s.