Event JSON
{
"id": "e3f14e50659888fd5e83f29db7604e6b788d7689343110551a9e1d688c27f2db",
"pubkey": "530f362e805e9f27258d0b6f3d60d98209119ce578a0932fa19ed8028eaf9af3",
"created_at": 1702564178,
"kind": 1,
"tags": [
[
"p",
"73eea2a2be552b046e5ce8baf04b58db1cdd02051a53222e35ed4d08f869e3e1",
"wss://relay.mostr.pub"
],
[
"p",
"20502883ace25666fa4de12ff6fc01b2a6a654d89e28342ed523c3d262c4a2fc",
"wss://relay.mostr.pub"
],
[
"e",
"4fee463c40e6660526753ebf8bc5314b270cc0ae242825a9fe586d78012c97d7",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://infosec.exchange/users/_dm/statuses/111579245999161380",
"activitypub"
]
],
"content": "nostr:npub1w0h29g47254sgmjuaza0qj6cmvwd6qs9rffjyt34a4xs37rfu0sskruwua Sure, but isn't that battery cost amortized across all the apps that use FCM? In comparison, if your app brings its own independent push notification connection, that's one more connection and one more background process--with the associated CPU and radio wake-ups, etc. Right?\n\nPut differently: if users already have FCM messaging enabled, they will notice ~zero marginal battery impact from adding one more FCM client, but they will notice a significant marginal impact from adding a new, non-FCM service. \n\nWhat am I missing here?",
"sig": "c05c29ea7952cebbac6a8e8036ae038f8a452889fa435c98c0c0149da79d008bb05e720311100045469906dc1dc696f18ba34cade3f0398eea322cc95f2afc7d"
}