• 0 Posts
  • 127 Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle




  • Aah, now I understand.

    There is no such setting that I’m immediately aware of - but I am automatically getting messages for my folders. So I’m assuming it’s doing something in the background: most likely a periodic sync for the entire account.

    Definitely doesn’t sound like the behavior you wanted, my bad. But, at least there are notifications on the folders once mail is received. 😅

    Edit: In the repo for their sync engine it explains:

    Mailspring uses a fairly basic syncing algorithm, which runs on two threads with two open connections to the mail server. Within each thread, work is performed synchronously.

    Background Worker: Periodically iterates over folders and (depending on the supported IMAP features) uses CONDSTORE / XYZRESYNC to check for mail or performs either a “local” or “deep” sync of part of the folder’s UID space.

    Foreground Worker: Idles on the primary folder and wakes to syncs changes. Also wakes to perform other tasks, like fetching message bodies the user clicks.

    So the foreground worker only idles on the primary folder, but it does slowly iterate over all folders in the background.

    No settings have been added for this functionality (that I’m aware of).

    Edit 2: Went back and read your original comment; hadn’t noticed the PR was yours. If that’s the case then you’re probably aware of how the sync works anyway. My bad if I’ve posted stuff you’re already aware of.


  • Fastmail.

    Can you choose which folders use real-time push vs which folders use polling?

    I’m afraid not. I’m pretty sure the entire account uses polling. I’ll usually open the app and hit F5 to quickly poll for results, otherwise I’m waiting for the next sync.

    Having said that, the unread counter works fine for sub-folders:

    Edit: I was wrong, Mailspring uses the IMAP IDLE extension to wait for new mail delivery. Still doesn’t stop me from spamming F5 when I’m waiting for new mail to arrive.












  • The not cool parts just relate to any sort of hosted bridge. If you don’t trust them with decrypting messages on their end, then don’t give them your data - there are no bridges capable of doing that, anywhere.

    So it really comes down to “trust someone else with your data, or host it yourself”; and if you’re - understandably - frustrated with those options blame companies like WhatsApp or Discord that make it nigh impossible to integrate their services with outside networks.

    Functionally, these bridges just forward your content to a library acting like a headless client - there’s no way to encrypt that as the reverse engineered clients are not libraries and need to take raw input. You can’t end to end encrypt it as the client is one of the “ends”.

    As an example, the WhatsApp bridge uses WhatsApp web as a backend, and has all the limitations of WA web.

    As a result, I find the expectations to be a bit unrealistic.


  • I am worried about that acquisition, to be honest.

    I’ve been supporting them via Github sponsors for about a year, now - as I only use their open source software; I’ve no intention of touching the service or closed source client.

    As a result, I’d be lying if I didn’t say I was anxious about their new owners basically telling them “hey, why are you releasing all your bridges for free, anyway?”

    Really hope that doesn’t happen, as their bridges have been my primary communication channels for a long time, now. I love not having to keep WhatsApp or Discord installed on my phone.