cryptomator / cryptomator/cryptomator.github.io

The two download options are confusing and without explanation regarding "WinFsp"

Open
#93 4 comments 0 reactions 0 assignees View on GitHub
type:enhancement
Dominant language
HTML
Stars
23
Forks
9
PR merge metrics
No merged PRs in 30d

Description

### Please agree to the following

- [X] I have searched [existing issues](https://github.com/cryptomator/cryptomator/issues?q=) for duplicates
- [X] I agree to follow this project's [Code of Conduct](https://github.com/cryptomator/cryptomator/blob/develop/.github/CODE_OF_CONDUCT.md)

### Summary

There are two download choices (other than portable) but no clear explanation or reasoning of the difference.

### What software is involved?

Download section of website says:
"This installer includes the third-party driver WinFsp. You can also download the MSI installer without dependencies."

Hmm...ok. Well this makes zero sense off the bat.

Thus a person has two possible download options? So now I try to figure out what this means. (Cryptomator didn't USED to have 2 choices and I'm already confused and this tells me nothing else.)

As a computer/tech person (I'm not 'general' audience level) I read and stare at that text and have zero idea what it means or what choice I'm supposed to make and the consequences or differences thereof. This is bad user interaction.

Saying that an installer doesn't have a DEPENDENCY is not the same as saying the resulting INSTALLATION has different FUNCTIONALITY. So then I go glance at the WinFsp page it seems to be doing some sort of entire alternate file-system-thing. Um, Ok. But what does that mean? How is it different when I get the MSI without 'dependencies". Why is this WinFsp thing and option included in one and not the other? and do I need it? What breaks if I dont have it? Am I better off without it?

Am I supposed to now go research the WinFsp framework now to answer the question? etc etc
(Maybe there is a page elsewhere on the Cryptomator site explaining this, but it shouldn't be 'elsewhere', it should be right there at the download.)

My suggestion is that this choice/situation be briefly explained on the download page in plain english. Why the two downloads, what does 'no dependencies' mean (since by definition it doesn't mean functionality changes, it just means something is 'all encompassing' or 'self contained'). Can we make this better so people know how to choose? Thanks.

### Volume Type

Dokany

### Steps to Reproduce

.

### Expected Behavior

.

### Actual Behavior

.

### Reproducibility

Always

### Relevant Log Output

```shell
.
```

### Anything else?

.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the website's download section and review the wording for the two Windows installer choices, including the WinFsp and dependency references. Done means the page explains in plain English why the options differ, what functionality each provides, and how visitors should choose between them.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation, web-dev
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.