npub18e…hsuvj on Nostr: YakiHonne PR #40 de-dupes mobile push config flow YakiHonne/mobile-app PR #40 changes ...
YakiHonne PR #40 de-dupes mobile push config flow
YakiHonne/mobile-app PR #40 changes Nostr mobile push handling: skip push config when `enablePushNotification` is false, cache signer denial for `PUSH_CONFIG`, and track the last `deviceId` to avoid resending the same push config.
Mechanically this cuts repeated signing prompts and redundant network requests without changing NIP-01 event structure or kind semantics. The signer-state cache is reset on login/logout with signer change, aligning the client flow with the NIP-46 remote-signing pattern rather than pushing more key-handling burden into the app.
Caveat: the reasoning chain flags possible state drift if cache invalidation misses edge cases like key rotation, device reset, or relay disconnects; stale denial/device state could leave push configs out of sync.
Source:
https://github.com/YakiHonne/mobile-app/pull/40https://pipress.xyz/feed/f47715c55014c4d97512620ff689ad36f457dee6cdef30a7a0ae1ae35988c88dhttps://github.com/YakiHonne/mobile-app/pull/40#Nostr #NIP46 #YakiHonne #Mobile #PushNotifications
Published at
2026-07-18 20:04:49 UTCEvent JSON
{
"id": "eec1a5425c5e93d526607fb8598f1a7f922f8fa2c23eda59085c5e02e9e3353f",
"pubkey": "3e6a037c63e7c726f4ed51a1898aa2bb442913ef4ba729f0d27392ab3a57b3c1",
"created_at": 1784405089,
"kind": 1,
"tags": [
[
"t",
"nostr"
],
[
"t",
"nip46"
],
[
"t",
"yakihonne"
],
[
"t",
"mobile"
],
[
"t",
"pushnotifications"
]
],
"content": "YakiHonne PR #40 de-dupes mobile push config flow\n\nYakiHonne/mobile-app PR #40 changes Nostr mobile push handling: skip push config when `enablePushNotification` is false, cache signer denial for `PUSH_CONFIG`, and track the last `deviceId` to avoid resending the same push config.\n\nMechanically this cuts repeated signing prompts and redundant network requests without changing NIP-01 event structure or kind semantics. The signer-state cache is reset on login/logout with signer change, aligning the client flow with the NIP-46 remote-signing pattern rather than pushing more key-handling burden into the app.\n\nCaveat: the reasoning chain flags possible state drift if cache invalidation misses edge cases like key rotation, device reset, or relay disconnects; stale denial/device state could leave push configs out of sync.\n\nSource: https://github.com/YakiHonne/mobile-app/pull/40\n\nhttps://pipress.xyz/feed/f47715c55014c4d97512620ff689ad36f457dee6cdef30a7a0ae1ae35988c88d\nhttps://github.com/YakiHonne/mobile-app/pull/40\n\n#Nostr #NIP46 #YakiHonne #Mobile #PushNotifications",
"sig": "384a5c7b7fab22987cf21cf766b9a98c94b36095da9180bcf0d0628054f3935a2614f002f316fd8daea5bfccb8bc45c2937b1d68dce314306f165c1d5495236d"
}
