Question could have been phrased better (I think fairly obvious there's some humor to it), but the fan-boy swarm here is discouraging.
If the community really cares about E2EE adoption, then gaslighting users about performance is counter-productive. Can confirm the experience on both desktop macOS and Android is going to be prohibitively slow for mass adoption (which, if it brings paid subscribers, would be helping the Proton project).
It is telling that a search through the docs and support for "cache" and "caching" produces no results other than copy/paste instructions for clearing browser cache (which, for PWA installs, should A) be irrelevant because the service-worker should be using isolated cache storage, and B) therefore if anything actually be counter-productive, because in a single-use PWA you WANT the cache to speed up loading).
Netflix et al DRM media platforms are streaming you encrypted video data in real-time, which is your first clue all the hand-waving about encryption in these threads is likely not from cryptographers.
The speed is a legitimate concern for usability. Caching seems the obvious first point of discussion. Either make at least some configuration editable by the user, or beef up the documentation to explain the blocker.
burron
Question could have been phrased better (I think fairly obvious there's some humor to it), but the fan-boy swarm here is discouraging.
If the community really cares about E2EE adoption, then gaslighting users about performance is counter-productive. Can confirm the experience on both desktop macOS and Android is going to be prohibitively slow for mass adoption (which, if it brings paid subscribers, would be helping the Proton project).
It is telling that a search through the docs and support for "cache" and "caching" produces no results other than copy/paste instructions for clearing browser cache (which, for PWA installs, should A) be irrelevant because the service-worker should be using isolated cache storage, and B) therefore if anything actually be counter-productive, because in a single-use PWA you WANT the cache to speed up loading).
Netflix et al DRM media platforms are streaming you encrypted video data in real-time, which is your first clue all the hand-waving about encryption in these threads is likely not from cryptographers.
The speed is a legitimate concern for usability. Caching seems the obvious first point of discussion. Either make at least some configuration editable by the user, or beef up the documentation to explain the blocker.
FR should be taken more seriously.