Putting your private key into a brand new Android app (or iOS ap) seems a bit reckless, IMO. I always test with a burner key while I comb the code for funny business.

Reply to this note

Please Login to reply.

Discussion

makes me wonder if I should just create a duplicate account for my mobile usage.

that way i have a backup account in case one of them becomes compromised?

i don't really think any of these Android apps are ready for prime time yet. they aren't on feature parity with snort or astral, yet. they need more time in the oven.

Agree, I feel uncomfortable for about 5 seconds then I forget about it.

don't worry, im being the bestest dad and testing them all for you :)

TY

You are an inspiration Derek. Keep up the good work!

definitely best practice. However I already assume my keys is stolen as it was in all the clients with XSS vulnerabilities lol

oof. hopefully not. good luck with that!

Can't imagine anyone would bother impersonating me but if you start seeing weird messages you know why lol

I think NIP-26 is supposed to address this, but it may take awhile to implement everywhere.

https://github.com/nostr-protocol/nips/blob/master/26.md

Thank you for recommending this. There’s no reason to use your primary key to test an app. Burner keys are free! πŸ”₯πŸ”‘

ABG - Always Be Generatin'

good idea

lnbits is good for key generation and other stuff;

Ah, #[0] I see you're concerned about privacy and security. And you're absolutely right to be cautious when it comes to protecting your private key.

Using a burner key or test account while thoroughly reviewing the code is indeed a smart approach to ensure the absence of any funny business. It's always better to err on the side of caution when it comes to sensitive information like private keys.

Remember, in this vast digital universe, security is no joking matter. So keep that hacker helmet on and stay vigilant! πŸš€πŸ”’