New features coming soon!

I’d like to thank everyone who has tried Jungle Disk and sent their feedback - so far the beta has gone very well with only a few minor problems reported. We’re working hard on a follow up beta release with some new functionality that has been highly requested. After that has baked we’ll be ready to “go 1.0″.

Here’s a sneak peek at some of the features we are planning for the next release:

  • Ability to set the cache directory and maximum cache size
  • HTTP Proxy support
  • Option to use a custom encryption key instead of the AWS secret key
  • Automatic backup / folder sync support
  • Ability to cancel all outstanding queued operations
  • Plus some minor tweaks and bug fixes

If there are other features that you want to see in Jungle Disk, please tell us on our Feature Requests forum.

5 Comments »

  1. Alex Choo said,

    June 3, 2006 @ 12:07 pm

    Great work guys!

    Have you considered open sourcing Jungle Disk? I’m sure more features can be added at a faster pace, and it’ll be the best S3 application out there.

    I’ve not been able to use Jungle Disk because it doesn’t enable me to mark files as public. :( Been waiting for this feature for a long time.

  2. Ryan said,

    June 4, 2006 @ 6:22 am

    great software at this early stage…looking forward to the next release!

  3. Tomas said,

    June 7, 2006 @ 11:28 pm

    i really like jungledisk - the only thing that bothers me is that localhost server - i would like it to be named Jungledisk (or so). would that be possible?

  4. Jungle Dave said,

    June 8, 2006 @ 8:30 am

    Tomas - We haven’t documented this, but you can actually use “http://my.jungledisk.com:2667″ instead if you prefer. It’s just a DNS alias to 127.0.0.1. Note that you’ll need to create the My Jungle Disk shortcut using the instructions on the help menu.

  5. Tomas said,

    June 8, 2006 @ 9:39 am

    heya dave, that’s great. can’t wait for the next version. would be awesome if it had more advanced preferences in terms of setting the drive name, list of buckets, location of the cache and maybe max. cache size - that’s all we might need. and also a way how to donate you through paypal maybe :-)

RSS feed for comments on this post · TrackBack URI

Leave a Comment