GEncfsM / MEncfsM Differences
I wrote the Molch Encfs Manager to be as close to the Gnome Encfs Manager as possible while incorporating the knowledge I gained from GEncfsM. Hence MEncfsM will most likely feel familiar or even the same in many places. The changes are mostly under the hood, but some are more visible to end users. I wanted GEncfsM to compile and work even with several years old distributions, which means that I always had to make a trade-off. At the end I decided to be conservative and pretty much stopped adding new features due to that since the Gnome Encfs Manager is quite widely used nowadays and reliability is way more important than new features. Just imagine yourself not being able to start working in the morning because GEncfsM doesn't start up or something…

The Keyring

While the Gnome Encfs Manager only uses the Gnome keyring, MEncfsM integrates with the KWallet on KDE and uses libsecret on all other desktops. Libsecret was the approach by GNOME and KDE developers to unify the keyring access, but apparently it was never implemented on KDE and the keyring folders don't work with it on GNOME as the time of writing. It might in the future though and one of the things that made GEncfsM hard to maintain are the desktop and distribution-specific hacks I had to come up with over the years.

Mount Detection

The Gnome Encfs Manager uses the GNOME infrastructure to detect mounted drives while MEncfsM is more low level and waits for changes on /proc/mounts. This means that it is platform-agnostic and works flawlessly on across all desktops. It will now also detect mounts outside the media and home directories. A drawback is, that it doesn't detect GVFS mounts anymore (e.g. when you mount a network drive in nautilus), but since that feature was unreliable to begin with (network drives might still need some time to actually let you read things after mounting etc.), I decided to cut that feature off the list for now.

Encfs configuration files

The work with encfs configuration files at custom locations has significantly improved. You can now set it during stash creation and MEncfsM will first create the stash in a temporary folder and then move the encfs file to the right place. It will also import the stash if you select the stash folder together with an existing encfs configuration file.

Improved interface

MEncfsM organizes its dialogs in pages which you can switch by enabling the sidebar (the small button at the bottom left on the dialogs). This is a vast improvement because it allows to better distribute the features and give them more space.

Colorize the tray icon when a stash is mounted

This feature has also been requested but was not trivial to implement because of the used library and compatibility issues. You can now set stashes to colorize the tray icon when the stash is mounted.

Other differences

MEncfsM isn't intended to be scripted. It lead to very hard to maintain code in GEncfsM, hard to reproduce crashes and memory leaks. MencfsM only allows you to mount, unmount and list your stashes on the command line, since those are the features that are actually used by people as far as I know. You can still add custom commands to the stashes, which should give more than enough flexibility, but the configuration is now left with the graphical interface. On the plus side, MEncfsM is now really asynchronous, which means that it mounts your stashes simultaneously and they are only queued if the password isn't in the keyring. The help is also better structured now and doesn't depend on any external application to show.