Is that true of Pokey of NTFY?
I’m not sure, but here’s what I found in a relavent search based on your question:
no, MIP-05 and Pokey/ntfy are solving the same problem but in completely different ways. Pokey with ntfy bypasses Apple/Google push infrastructure entirely by maintaining its own connection to relays, so the encrypted token and decoy mechanism MIP-05 describes is irrelevant to how they work. MIP-05 is specifically for the Marmot/WhiteNoise ecosystem where push notifications are being sent through Apple/Google, and the privacy engineering is about minimising what the notification server can learn in that scenario.
If anything, the commenter's question highlights a useful distinction you could draw out — there are broadly two strategies here: avoid the Apple/Google push pipeline (Pokey/ntfy/UnifiedPush approach) or use it but strip it of meaningful metadata (MIP-05 approach). Both are valid, with different tradeoffs. Pokey's approach works great on Android but doesn't solve for iOS at all, which is exactly the gap MIP-05 is designed to fill.
no, MIP-05 and Pokey/ntfy are solving the same problem but in completely different ways. Pokey with ntfy bypasses Apple/Google push infrastructure entirely by maintaining its own connection to relays, so the encrypted token and decoy mechanism MIP-05 describes is irrelevant to how they work. MIP-05 is specifically for the Marmot/WhiteNoise ecosystem where push notifications are being sent through Apple/Google, and the privacy engineering is about minimising what the notification server can learn in that scenario.
If anything, the commenter's question highlights a useful distinction you could draw out — there are broadly two strategies here: avoid the Apple/Google push pipeline (Pokey/ntfy/UnifiedPush approach) or use it but strip it of meaningful metadata (MIP-05 approach). Both are valid, with different tradeoffs. Pokey's approach works great on Android but doesn't solve for iOS at all, which is exactly the gap MIP-05 is designed to fill.