All #Nostr apps where a user is expected to log-in or sign any event with their private key, should support NIP-46. All Nostr apps on Android should support NIP-55 in addition to NIP-46. All Nostr web apps should support NIP-07 in addition to NIP-46. We need a local signing standard for iOS similar to NIP-55 for Android. Is that part of what you are working on @Terry Yiu ? NIP-46 should be the standard, and other options available based on the platform. Not sure if bare nsec login should be entirely deprecated, or just strongly discouraged at this point. Open to be convinced either way. Anyone have thoughts on that? #asknostr

A friend of mine asked a question that I wasn't expecting: "Is it possible to make a post with zaps turned off for just that post?" The only thing that I could thing of would be to remove his lightning address from his profile, but that would remove the ability to zap ANY of his posts, not just that individual post, and there isn't any guarantee that all copies of his profile on all relays would be updated to no longer show his lightning address, so some folks might still be able to zap him. I also wondered why anyone would ever want to turn zaps off for a single post. Turns out, he'd like to post drone footage, but there is a hefty fine if you monetize it without a commercial license. Now, something tells me, this is probably talking about charging customers to create drone footage for them rather than getting tipped 21 sats for a cool video posted to Nostr, but I can see other instances where folks might not want to accept zaps for something they are posting. For instance, if they are sharing something that someone else created, so they don't feel like they should be able to collect value from others for value they didn't personally put in the proof of work to provide. Is this something we could add? Some kind of tag that would indicate to clients that a post should not be zappable? #asknostr #nostrdevs