It's been a few years since I last encrypted a message via the web interface (https://keybase.io/encrypt), but now I get the error Error: Cannot find a public key for '<username>' for most users I've checked, including myself—but can still encrypt messages to them via the desktop app or CLI, and can still decrypt messages sent to me via the web interface.
No JS console or network errors are visible in the browser dev tools.
In case it's helpful, I received the same error when attempting to encrypt messages to hellobot, @malgorithms, and a handful of other randomly selected users, but did successfully encrypt a message to @maxtaco (but could not sign it—got the same error if I tried). So it's not completely broken! :)
(Note: decryption via the web interface only works for PGP messages: saltpack messages (like the desktop app produces) fail in the web interface with the message Error: no header found. Presumably saltpack just isn't supported via the web interface, but the web UI and error message are unclear.)
It's been a few years since I last encrypted a message via the web interface (https://keybase.io/encrypt), but now I get the error
Error: Cannot find a public key for '<username>'for most users I've checked, including myself—but can still encrypt messages to them via the desktop app or CLI, and can still decrypt messages sent to me via the web interface.No JS console or network errors are visible in the browser dev tools.
In case it's helpful, I received the same error when attempting to encrypt messages to hellobot, @malgorithms, and a handful of other randomly selected users, but did successfully encrypt a message to @maxtaco (but could not sign it—got the same error if I tried). So it's not completely broken! :)
(Note: decryption via the web interface only works for PGP messages: saltpack messages (like the desktop app produces) fail in the web interface with the message
Error: no header found. Presumably saltpack just isn't supported via the web interface, but the web UI and error message are unclear.)