![bitcasa infinite drive bitcasa infinite drive](http://www.wincore.ru/uploads/posts/2012-12/1356075413_image-3112129.jpg)
It is really just a wrapper around Python's standard library HTTP package, but it is much simpler to use. Requests is used to upload the files via POST requests made to the web portal. Package RequirementsĬurrently, this script needs only one non-standard library package to function. Currently, I know of no way to create new directories via the web portal. Because it uses the web portal to upload the files, it is restricted by the limitations of the web portal. This script uses the Bitcasa Web Portal to navigate your Bitcasa Drive and upload files. My plan is to expand the script into a command line utility and possibly a GUI. This is a rough python script that I threw together that can upload files to your Bitcasa Infinite Drive. Improvements and new ideas are always welcome.
#BITCASA INFINITE DRIVE FREE#
So feel free to change, tinker, remix, and make it your own. That being said, I'm releasing this under the GPLv3 license. I make no promises of data safety or secruity. Copyright ©2022 ExtremeTech unless otherwise noted.This is just a script I made for myself that I wanted to share.
![bitcasa infinite drive bitcasa infinite drive](https://www.cloudwards.net/wp-content/uploads/2013/03/06-bitcasa-copy-files-270x135.jpg)
I think the company chose a small cache size by default to minimize the problem, but the bottom line is that file copies don’t happen nearly as quickly as they seem to. I have to admit that I’m skeptical that this was just an oversight. The current implementation makes it seem as though files have been uploaded at hypersonic velocities but then saturates network bandwidth for hours as it struggles to fulfill the request with decidedly non-magical equipment. This is only a problem when the size of the file to be uploaded fits entirely within Bitcasa’s defined cache, but it’s still a nasty loophole. Bitcasa doesn’t throw up a warning flag on the play. Once the file has been copied, there’s nothing to prevent the end-user from deleting the original. It’s not a problem that’s unique to Bitcasa, by any means. What is troubling, however, is the way Windows’ file copy system is leveraged to make it seem as though a file has been uploaded, even when it hasn’t been. That reality puts a damper on these sorts of services. I suspect this is a problem with NB itself, but this app needs a watchdog to play nice with others. I tried using a third-party tool to limit upload bandwidth, but NetBalancer wasn’t able to control Bitcasa’s speeds. Using Bitcasa to upload a file effectively shut off my ‘net for any other task. The bad news is that routers respond remarkably poorly to upload saturation, and mine is no exception. The good news is that upload speeds are excellent - my system was able to sustain a 100KB/s connection to Bitcasa, fully saturating my own upload bandwidth. This application sucks bandwidth like a fat kid on cake and it doesn’t like to share. That brings us to another problem - Bitcasa is an extraordinarily bad bandwidth citizen. At 100KB/sec, it’ll take me nearly two days to upload these files. In reality, however, the file copy has barely begun.
#BITCASA INFINITE DRIVE MOVIE#
If I click on the movie from the I:\ location, it starts to play.
![bitcasa infinite drive bitcasa infinite drive](https://i.gzn.jp/img/2013/08/27/bitcasa-infinite-drive/41_m.png)
![bitcasa infinite drive bitcasa infinite drive](https://imag.malavida.com/mvimgbig/download-fs/bitcasa-11942-2.jpg)
There’s a file on my I:\, the file copy dialog has closed. The real problem here is that as far as the end-user can tell, the file copy is actually complete.