Sebastian Stenzel

> out of necessity to stay Java-8-compatible Well you can create multi-release jars, where the `module-info.class` file only gets included inside `META-INF/versions/9` and is therefore invisible for old¹ class loaders....

> Could it be possible for the new version to simply replace the existing version, without having to remove and reboot ? That's for example quite a difficult operation on...

With the changes in eb8ee73, does this error persist?

While we're at it, it's also worth mentioning, that cryptomator/cryptomator#119 is an accepted risk and a fix have unacceptable impact on I/O.

> Add `runasoriginaluser` flag According to [the documentation](http://www.jrsoftware.org/ishelp/index.php?topic=runsection#Flags) this shouldn't be necessary when `postinstall` is already present: > This is the default behavior when the postinstall flag is used.

Cryptomator is case-sensitive. This is inevitable due to deterministic filename encryption (see explanation in cryptomator/cryptomator#622). There is the possibility to add a case-insensitive mode, which will take O(n*m) instead of...

From a technical perspective this is possible. However, I see some organizational as well as legal difficulties here: 1. Under certain circumstances we are required to refresh the site with...

Some possible solutions discussed in https://github.com/dokan-dev/dokany/issues/51

#19 is more severe than #3. If we can figure out how to ask the user whether all settings should be deleted, this would be ideal. Otherwise this is a...

WinFSP is an optional but recommended component. As you claim to be using Dokany, you would not need it. We try to steer new users to use WinFSP, hence the...