- From: chaals <notifications@github.com>
- Date: Tue, 20 Jun 2017 11:10:09 -0700
- To: w3c/push-api <push-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 20 June 2017 18:11:08 UTC
@beverloo wrote: > The ability to have subscriptions with multiple Push Services doesn't change that however, it just moves the problem to another actor. Sure. But it seems to me that not having a choice of actors is a pretty major limitation. While an app developer does not have access to the payloads, having a mandated pathway for messages seems like a pretty significant opportunity on the part of whoever controls that pathway to collect user metadata, and a pretty central point of attack for a malicious third party. I understand there is a trade-off in terms of user interface design, and power consumption, but I'm not convinced that the architectural choice to sacrifice a lot of control over privacy is the right one. -- 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/258#issuecomment-309841799
Received on Tuesday, 20 June 2017 18:11:08 UTC