cryptomator
Suggestion for how to continue with CLI
It looks like the Cryptomator CLI project isn't getting as much attention as we may have hoped for. I would suggest that given there isn't enough interest in the cli aspect to gain critical mass, it would be better if it wasn't a split project in the first place but instead the primary Cryptomator Java project simply handled detection of no graphical interface and/or console invocation depending on what makes sense for the platform and command line parameters, and acted accordingly. Cryptomator could either take all of the necessary inputs as command line parameters the way it appears CLI was doing, and/or it could provide a REPL for runtime mount/unmount etc. You could run it with screen for the REPL, or we could make a CLI option that connects to a running instance of Cryptomator to launch a REPL. The CLI mode of operation would want to be included in any CICD testing as part of the releases to ensure that changes to the GUI interface and backend code don't break the CLI scenario.
Does this seem like a rational suggestion? The CLI based consumers would have a larger app than they might have got from a dedicated CLI app, but this way they get a maintained app that should remain at parity with the GUI version. In my experience, if you can't keep critical mass the solution is to minimize your deviation from the "upstream" so you don't need as much critical mass.
