This release is mainly a bug fix release but also contains some important improvements.
GC Cache Propagation
Most importantly, we have found and fixed a problem in our garbage collection algorithm. No files were lost, but the filesystem cache of different SharedSafe installations could go out of sync, causing some internal errors and eventually made synchronizing impossible.
With this version, this problem has been fixed. After installing, the caches are automatically rebuilt and we extended the filesystem to make sure that the caches stay in sync.
Note to users with very old Safes from SharedSafe alpha builds: If you encounter unexpected conflicts, you need to upload these files again to update their Hash-Information.
Please note that once you have updated to 0.7.2382, you need to update all other clients that access the same safes.
Additionally, we improved the verification synchronization. It now rebuilds all the local caches. So if anything goes wrong, use the verification synchronization to get in sync again. In any case, please report problems back to us, so that we can improve SharedSafe.
While testing the complete resynchronization, we found out that GMail sometimes reports a temporary error “NO Some messages could not be FETCHed (Failure)”. Just wait a while, the problem should disappear after some synchronization attempts. We assume that GMail does not like the kind of IMAP request we are using to redownload all filesystem meta data.
HTTP Proxy Authentication
We’ve implemented preliminary support for authentication of HTTP Proxies. If you had troubles connecting to an IMAP server via an HTTP proxy, it should work now. If it does not, ask your system administrator if the proxy allows connecting to the IMAP ports 143 and 993.
If you used a readonly safe, SharedSafe wasn’t properly behaving when new or changed files were detected in the linked folder. With this update, new and changed files are marked as errors and redownloaded once deleted.
Shell Extension Behavior
We had a little trouble with the general behavior of the shell extension. The shell extension sometimes started SharedSafe.exe. That caused several problems, for example within a reinstallation. Now, the shell extension is completely passive and regularly checks if SharedSafe.exe is started. As soon you exit SharedSafe, all overlay icons will disappear, and as soon you start it again, the overlay icons reappear.
New Overlay Icons on Windows XP
We have not found a way to programmatically clear the Windows Explorer Icon Cache on Windows XP installations, so if the new overlay icons do not appear after a reinstallation, please check our FAQ.