#[0] did you change something in how direct encrypted messages were parsed? Previously, messages I had sent with noscl weren't able to be decrypted in nostrgram, but now I am seeing those messages showing up.
Discussion
So you sent encrypted messages that you couldn't decrypt before but now you can decrypt? Is that correct? Sounds like your priv key is working and you are letting everyone know that.
Yes
No the code for encrypting/decrypting messages hasn't changed since I first implemented it.
Thanks. I think the only thing I've changed is use of the getAlby extension instead of NOS2X.
It's odd because in my dev environment with the web server running on my laptop Alby doesn't work. It throws an error when I try to use it. But Nos2x works fine. But on the public web server Alby works just fine and I've had a few people say Nos2x doesn't work for them. I'm not sure what's different since all the extension is doing is injecting code onto the page to provide access to an object on the window. It's not complicated, so I'm not sure why it's so finicky.
Interesting. You're probably better sandboxed. I have other extensions running and maybe one of these is causing a conflict