Skip to content

Alexis Perot

My feedback

7 results found

  1. 19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Alexis Perot supported this idea  · 
  2. 99 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Alexis Perot commented  · 

    Adding a concrete Linux data point, since the request so far describes mainly the Windows/macOS experience.

    Environment: Proton Mail desktop app on Fedora Linux (F44, current stable build). The built-in spellchecker runs in one language only (US English) and there is no setting anywhere in the app to change it: neither in Settings nor in the composer, neither globally nor per message. Writing mail in several languages therefore floods the composer with false positives in every language except American English.

    The technical asymmetry is easy to state precisely:

    The Proton Mail web app delegates spellchecking to the browser's engine. In Firefox on Linux that engine reads the system hunspell dictionaries, so mail.proton.me in a browser spellchecks correctly in any language the user has installed and configured. The browser also lets the user switch languages by right-clicking a text field.
    The desktop app is Electron, so its spellchecker is Chromium's bundled engine, disconnected from system dictionaries and, in the current build, from any user-facing language option. Chromium's own API (session.setSpellCheckerLanguages) supports per-language and multi-language selection; the capability exists in the framework and is simply not exposed in the Proton UI.

    Requested behavior, in order of usefulness:

    A spellcheck language picker in Settings (app-wide default), and ideally per-composer override, matching what the browser experience already provides.
    Multi-language checking, since many users compose in more than one language.
    Alternatively, a documented setting (flag, config file) that exposes setSpellCheckerLanguages for those willing to edit it.

    Until this exists, the practical consequence is that the desktop app is strictly worse than the website for multilingual users on Linux: the same account, same machine, correct spellchecking in the browser and a locked US-English checker in the app. That inversion (install the native app, lose functionality) is worth fixing regardless of platform.

    Alexis Perot supported this idea  · 
  3. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Alexis Perot supported this idea  · 
  4. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Alexis Perot supported this idea  · 
  5. 315 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Alexis Perot supported this idea  · 
  6. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Alexis Perot supported this idea  · 
  7. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Alexis Perot supported this idea  · 
    An error occurred while saving the comment
    Alexis Perot commented  · 

    Another data point in favor of this: PPPoE-based fiber connections have a hard path MTU of 1492 bytes. When ICMP "frag needed" messages are filtered anywhere along the path (common ISP behavior), the app's default tunnel MTU fails silently; sites partially load, requests time out, and users conclude the VPN is broken.

    Currently the only workaround is manual WireGuard config files with MTU = 1400 under [Interface], losing all app conveniences (server switching, Secure Core, kill switch, split tunneling) just to set one number.

    I'd also second Juha's suggestion above of simplifying the title to "Adjustable MTU"; both auto-negotiation and a manual override field solve the same user problem from different ends, and a broader title would aggregate these votes instead of splitting them.

    Concrete ask: Settings → Connection → "Override tunnel MTU" (desktop apps, Linux particularly), or auto-clamping via path-MTU discovery. The config-file ecosystem already supports the concept, so the GUI just needs to expose it.