Ever since I've known AT, it has been in the Beta stage. Are you planning to launch the "full" site? What would it have apart from the Beta?

Wow! amazed at the level of tech that went into making this site. I'll stick to plowshare as I've become a bit familiar with it ( also sounds a lot better than writing to TCP lol ). Thanks for taking the time admin. Keep it up ;)

Firefox, by default, has a soft limit of 50MB for IndexedDB storage (soft limit = asks for permission to get larger, but no hard limit after that), but I presume anyone who uses Mega would just agree to it.
I haven't checked, but I'd imagine that IndexedDB storage would come under Firefox's "Offline Website Data" (or maybe "Cookies") or Chrome's "cookies and other site and plug-in data", so clearing that regularly could help. Depending on your browser usage pattern, you may choose to get the browser to clear it on exit.

I'd say it's just a bug / lazy coding rather than anything nefarious. There are a million smarter ways to track you (not saying they aren't).
Writing the file to an IndexedDB is a somewhat ugly way to do things, but I suppose there isn't really much else you can do in Javascript. Perhaps a custom desktop downloader won't have the issue.

Thanks for sharing the info!

Recovering GBs of hard disk space after using Mega.co.nz

I just recovered 42GB of hard disk space from dead files that Mega left after downloading.  And I don't use that Mega often.   I didn't find any information about this at Mega or with a Google search, so I thought I'd share the how and why with any here at AT who are interested:

1. How to recover space: Delete the folder "https+++mega.co.nz" that Mega creates on your hard drive during downloads.  For Firefox users the folder is located at:

For Win7:

c:\Users\"Username"\AppData\Roaming\Mozilla\Firefox\Profiles\"xxxxxxxx".default\indexedDB\https+++mega.co.nz


For WinXD:

c:\Documents and Settings\"Username"\Application Data\Mozilla\Firefox\Profiles\"xxxxxxxx".default\indexedDB\https+++mega.co.nz


(The info in quotes varies by person.)


So far Mega has never cleaned up these files on the machines I use.  Firefox doesn't either.

2. The why: (Optional info)  When you use Mega it creates it's own un-moderated folder, copies your downloads to that folder in a metadata/database format and when the download is complete then copies the database files from that folder to the browser, converting the information back into the original file format.  The problem is it doesn't delete the database files after it's done, leaving them as dead weight on your hard drive.  If you want the space back, you have to find the database folder and delete the files manually.

3. The Why of the why: Why doesn't Mega clean up after itself?  Sloppy implementation?  Maybe tracking your use for a future plea-bargain.

IE and Chrome: You'll have to find out for yourself if you have the same problem and where the folder is.

Okay that makes sense then.
Unless you have a specific reason not to, I don't see the problem in using plowshare.

The script writes to TCP sockets directly. cURL provides nice abstractions for HTTP, but doesn't exactly provide enough flexibility that's needed here.
I'm not sure how I'd help you with interacting with upload sites. It's largely about understanding how HTTP works and replicating and automating it.