rich1.0SkyLords (npub16n…ty8ka)https://nostr.ae/npub16ntyfte9h8u2pjpc90su57gcw2f9c7yzsjx6uyfpmaq3tfuxk7lq8ty8kanjumphttps://nostr.aeSkySigner is still very much in development, and the approval model is actually one of the things I am rethinking right now. My original idea was to ask again for sensitive permissions, but at the moment it ends up asking for approval for almost everything. After using it myself for a while, even I started getting tired of clicking approve 😄 So I am leaning toward a middle ground: trust or whitelist a client for routine operations, but still ask again when it requests something more sensitive or a capability it has not used before. The funny part is that every time I think I have finished one piece, another compatibility issue appears. Some clients still use NIP-04 for messaging, while others use newer approaches such as NIP-17, so fixing one workflow often reveals another one that needs support. That has basically been the SkySigner development experience so far: one step forward, discover another NIP, back to the code 😄