hydroxide

I've been thinking about this over the past few days - If AI is as capable as people here claim - enough to replace junior or intermediate developers - could it be used to maintain semi-abandoned open-source projects? There is a fair number of abandoned OSS with 1 or 2 major issues that prevent them from continuing to work and isn't too difficult to fix - just requires time. If users pooled context (issues, code, docs) and tokens, I'm inclined to believe an AI agent could resolve them. Here's an example: hydroxide [0] is a ProtonMail to IMAP/SMTP bridge that no longer works due to upstream API changes [1]. Working implementations are available, just in a different language [2]. All an AI would have to do is reference the current implementation and the alternative implementation, then migrate over to the new API format. Perhaps use an mit

Another option would be to try this hydroxide patch (that i need to find time to review...): https://github.com/emersion/hydroxide/pull/282

the devs seem to blame go-imap (https://github.com/emersion/go-imap). at a quick glance the library itself doesn't seem to have an open issue describing the problem. curious if that author's (deprecated) protonmail bridge hydroxide (https://github.com/emersion/hydroxide) has the same problem.

For those who like using other mail clients there is the official Protonmail Bridge[1] (for paid customers). There is also Hydroxide[2] (which I use). I am able to use Apple Mail on mobile, Aerc[3] command line mail client on desktop (MacOS and Linux), and sync with the CardDav instance for contacts. Understandably, this is not an ideal solution for everyone -- it works awesome for me! Just a PSA for those not aware. [1] https://proton.me/mail/bridge [2] https://github.com/emersion/hydroxide [3] https://aerc-mail.org/

That is a very interesting claim on their part considering that they hold the private PGP keys used by their service. I'll have to figure out what they mean by this. Edit: Ok I see. They store the PGP keys encrypted with your password. Like you said, they could just as well inject javascript to phish your password from your session. But this does seem to mean that if one uses their API directly it would be possible to securely use their service. Thanks for the heads up. There is a third party open source bridge that reverse engineers their API. I think I will look into it to see how authentication is done. https://github.com/emersion/hydroxide

You could try a third party bridge: https://github.com/emersion/hydroxide

For those without premium accounts, I have good experiences with https://github.com/emersion/hydroxide

I've been developing such a thing, mainly for git-send-email and CardDAV sync: https://github.com/emersion/hydroxide