CloudMounter for Mac 4.0 reviews
Cloud drives mounted locally on your macOS desktop
•2 reviews•243 followers
Subscribe
Sign in
243 followers
Hey there, Darun Tim and the CloudMounter team! 📌 Congratulations on the release of CloudMounter 4.0! It's fantastic to see the progress and improvements you've made, and a big thank you to Chris Messina for bringing attention to this exciting release. The increased compatibility with Google Drive and Amazon S3 is definitely a noteworthy update. It's great to hear that CloudMounter now works even faster with these services, and the ability to create Drive links and control file access with Amazon IAM adds an extra layer of convenience and security. However, what really caught my attention is the new native mount mode. This feature allows users to work with files offline, without the need for an internet connection, and updates the cloud storage automatically once reconnected. This is incredibly useful, especially in situations where network stability may be a concern. It's clear that you've put a lot of thought into addressing user needs and providing a seamless experience. Overall, this release is indeed a big deal! I'm sure users will appreciate the enhanced performance, expanded compatibility, and the convenience of the native mount mode. Thank you for continuously striving to improve CloudMounter and deliver valuable updates to your users. I'm definitely intrigued by the 30% discount offer, and I'll make sure to check out the link you've provided. Keep up the great work, and here's to the continued success of CloudMounter!
I expected a lot from the addition of native mount support, but I'm a little disappointed... 😕 - The first big downside is that my servers in my Finder sidebar are now called "CloudMounter - [name]" and there is no way to change it... so frustrating! - When I want to download a folder in my server I have these error messages that appear: "The operation could not be completed. File or directory does not exist." or "The file ".DS_Store" does not exist.". The only solution I was offered was to change the type of mount... Too bad, the native mount was a gamechanger for me!