Yes, our signer is built on the standard NIP-46 spec. We follow the spec precisely, there is nothing proprietary in our implementation.
You don't need to trust Primal with your nsec; our entire stack is open, so you can see precisely how we handling it. The idea behind building a signer is precisely to minimize the need for our users to paste their nsec into any new nostr app they wish to try.
Thanks for reporting and apologies for the outage. It seems to affect a small subset of our users but we were just able to reproduce it and are working on a fix. Aiming to deploy it first thing tomorrow.
I think it's a good idea to prompt the user to confirm if pasting the fully qualified URL is what they actually wanted.
We never want to assume we are smarter than the user and just automatically replace the content they pasted, but prompting seems like the right balance in this case.
We got these reports before and weโve had a hard time reproducing them. Weโd really appreciate if you could help us with this. Some immediate questions:
1. Are you consistently seeing these issues, or intermittently?
2. If you login into the Primal web app, does everything load quickly?
all primal clients always generate nostr nevent references for mentioned notes. the only way to end up with a primal url is to deliberately paste it in the note.