LOL the article has nothing to do with primal it’s nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn β€˜s

https://primal.net/e/naddr1qqxnzdenxyenvdesxvmrvwp4qgsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgsrqsqqqa28dvqyja

Reply to this note

Please Login to reply.

Discussion

I've read the article. I just wish primal supported amber.

i think they’ve been working on it

They're more concerned with rolling out their premium tier than with protecting their users' nsecs. Allowing sign-in with Amber should have been enabled long before v2.0.

You’re comparing their speed of implementation to android specific clients, keep in mind they’re working simultaneously on web, iOS & android.

they also released android like 4 months ago compared to the ones you’re thinking of that have been around for longer than a year and have a shit ton of contributors lol

give it a years time, and everything will be left in the dust.

I get what you're saying. It's really a matter of priorities. And while I believe I may have prioritized things differently, I'm not privy to their thought process, and their reasoning for choosing to prioritize certain things over others. It's just frustrating to me because I see external signer support as a fundamental feature that every client should support on day one.

Unfortunately I’m on IOS so I haven’t experienced external signer support from any IOS client, I’ve had to raw dog my nsec into every single one of them..

i agree that it should be at the top of the list idk why it isn’t, if it’s because it’s harder to implement then i understand but if it’s bc it’s not a popular request then I don’t..

Coming soon!