Files
Amber/app
Claude 145ff51559 Refactor encrypt/decrypt permissions to be by EncryptedDataKind
Instead of storing permissions as nip04_encrypt, nip44_encrypt, etc.
(grouped by encryption algorithm), permissions are now stored based on
the type of data being encrypted or decrypted:

- ENCRYPT_CLEAR_TEXT / DECRYPT_CLEAR_TEXT (text messages)
- ENCRYPT_EVENT / DECRYPT_EVENT (nostr events)
- ENCRYPT_TAG_ARRAY / DECRYPT_TAG_ARRAY (tag arrays)
- DECRYPT_ZAP_EVENT (private zap events, unchanged)

This allows more granular permission control based on what data is
being processed rather than which NIP algorithm is used. Backward
compatibility is maintained by falling back to old NIP-based
permission types during lookup.

Key changes:
- EncryptedDataKind.kt: add toPermissionType(), toPermissionTypeString(),
  permissionTypeFromContent() helpers
- AmberUtils.acceptPermission(): use EncryptedDataKind-based type when storing
- BunkerRequestUtils/IntentUtils: pass encryptedData to acceptPermission
- BunkerSingleEventHomeScreen/IntentSingleEventHomeScreen: look up permissions
  by EncryptedDataKind type with NIP-based fallbacks
- SignerProvider: classify content to determine permission type before lookup
- BasicPermissions/Permission: add new permission types and string resources

https://claude.ai/code/session_01Q7XBgjPSfeVdiQ3smLw7YC
2026-03-13 14:59:01 +00:00
..
2024-03-01 06:56:32 -03:00
2023-07-26 16:44:33 -03:00
2026-03-11 14:34:41 -03:00