The Switcher: bring your connections with you
The reason people stay with a mount app is not loyalty — it is twenty-odd connections already configured somewhere else. Mountit now reads them.
Nobody switches mount apps for features. They stay because their
connections live somewhere else — an rclone.conf with two dozen
remotes, a Cyberduck bookmark list, Transmit favourites, Finder’s own
“Connect to Server” history. Re-typing all of that by hand is the real
switching cost, so we built the importer first and called it what it is:
the Switcher.
It reads rclone.conf (passwords included — the
obscure encoding is implemented and verified against a real
rclone binary, differentially), Cyberduck and Mountain Duck bookmarks,
Transmit and ForkLift favourites, ExpanDrive drives, and the servers macOS
itself remembers. Nothing is imported silently: you get a dry-run plan that
lists every item, imported or skipped, with the reason, and only a step you
take after that creates anything.
Two details matter more than the list of formats.
An rclone type = crypt remote — client-side-encrypted
storage — works on the day you import it, because our crypt layer is
byte-compatible with rclone’s. The importer does not take that on faith:
for each crypt remote it derives the keys from your password and round-trips
a filename through our own cipher before saying the remote will mount.
And your own OAuth credentials are yours. rclone’s documentation tells Google Drive and OneDrive users to create their own client id and secret; those import verbatim, which makes those backends work with no registration of ours in existence. rclone’s built-in client credentials are the opposite case: they are never shipped, never reused, fingerprinted and stripped on import, with a test that fails if a candidate ever carries one.
The Switcher is built and tested; it reaches you when Mountit does. The changelog is the honest ledger of when that is.