Thank you! I'd love to know about your experience using it. If you have any questions, comments, feature ideas, feel free to reach out via the support email :)
Thank you for the feedback! At the moment it's not scroll-aware, but it's an excellent idea, thank you.
I won't be able to make it app-aware, given the very rigid security posture (complete sandbox), but I may be able to make it scroll-aware, so at least within the same window it'd move relative to the 'global' position. I'll look into it :)
I think you should indicate this above or below the demo in a smallish typeface. Your explanation makes sense, but the presentation comes off as sketchy without that info. Maybe it's just me. Thanks for responding.
And I'd love to make it for iPads too, just struggling to find the optimal UX for enabling and disabling the overlay.
On macOS you can just use the global hotkey or the app menu, on iPad I'd have to wire it up somehow else - supper happy to get ideas on what would feel seamless and unobtrusive for you. I'll definitely implement it then!
What about a control center toggle? Works alright for toggling the windowing system. In general having shortcuts to set it on/off/toggle would be great.
To me this looks strictly worse than if they just used s/mime with some magic to integrate in the Gmail client for ux.
As I read it[1] - Gmail users are given a hidden s/mime key pair, possibly with secret key stored in a hw token/on device.
I can only assume that when mailing an external user without guest/Gmail account, Gmail will generate a (temporary?) key pair for the recipient, encrypt the message under temporary public key of the recipient - then when recipient creates the guest account - either generate a new key pair and re-encrypt or assign the key pair held for the user? To allow Gmail to decrypt the mail in the browser? As well as implicitly trust the sender key for verification?
I struggle to see how this is e2e in any meaningful sense?
When I log into a public terminal at my library - how will the browser access my keys?
Let's Encrypt issues DV (domain-validated) certs, some people need OV (organisation-validated) certs.
But you're right that Let's Encrypt can cover a vast majority of usecases these days.