APS moved away from OpenKeychain to PGPainless some time ago, from before this fork started. While not perfect either (see https://github.com/agrahn/Android-Password-Store/issues/287), PGPainless is being maintained, and from what I can tell from this APS fork's git log, is automatically bumped via their renovate bot (e.g. https://github.com/agrahn/Android-Password-Store/commit/9a6b596199d7eb87b40b53c4cb111ba7a5b48188)

Did you see the Documentation section in the README.md? You basically initialise a password store on your server, and you use an implementation like this to sync (SSH + git) your passwords, which are encrypted via your GPG key.

https://www.passwordstore.org/ has some instructions how to initialise a password store on, for example, your server. Then refer to https://github.com/android-password-store/Android-Password-Store/wiki/First-time-setup to configure the app.

I sadly haven't tracked precise battery usage for both Signal and Molly, to properly compare. I do believe it easily saves me 10 percent on my daily battery life, though.

Thanks for subscribing! :-)

Of course, Signal will be unlinked when using Molly. Molly however supports multiple devices.

I was too! I almost migrated to Vaultwarden, but I'm very thankful this fork is continuing the original maintainer's work.

Does https://pq.cloudflareresearch.com/ confirm your browser is using X25519MLKEM768?

Are you sure you're using an up to date browser? My server is using TLS 1.3 with x25519mlkem768. Most browsers should support this KEM already.