- From: Peter Beverloo <notifications@github.com>
- Date: Mon, 25 Jul 2016 07:00:35 -0700
- To: w3c/push-api <push-api@noreply.github.com>
Received on Monday, 25 July 2016 14:03:21 UTC
Thank you for the suggestion! This is a [protocol](https://tools.ietf.org/html/draft-ietf-webpush-protocol)-level issue that would be appropriately scoped to the [IETF Web Push WG](https://www.ietf.org/mailman/listinfo/webpush), but is considered out of scope for the current milestones. To give you the gist of why this isn't available— payloads. The protocol mandates use of end-to-end encryption per [draft-ietf-webpush-encryption](https://tools.ietf.org/html/draft-ietf-webpush-encryption), which is a model that _can't_ work for messages having multiple recipients. As such, I'll close this issue. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/push-api/issues/208#issuecomment-234961230
Received on Monday, 25 July 2016 14:03:21 UTC