Push API – W3C Working Draft

Re:Push API – W3C Working Draft by nailer on Monday October 27, 2014 @04:22AM (#8514418)

We all get phone calls or text messages now when we don't have the associated binary apps open. Isn't this just the same thing for web apps?

[ Parent | on HN ]

Re:Push API – W3C Working Draft by TheOtherHobbes on Monday October 27, 2014 @07:37AM (#8514886)

It's the same things for web apps, with added near-infinite possibilities for spam.

[ Parent | on HN ]

Re:Push API – W3C Working Draft by nailer on Monday October 27, 2014 @08:36AM (#8515090)

It's permission based. Read the linked spec.

[ Parent | on HN ]

Re:Push API – W3C Working Draft by TheOtherHobbes on Monday October 27, 2014 @10:33AM (#8515629)

Are the permissions fine-grained enough to give users the power to say Yes to useful content and No to intrusive marketing messages?

Or is the option to include that choice going to be left to site designers?

[ Parent | on HN ]

Re:Push API – W3C Working Draft by nailer on Monday October 27, 2014 @11:03AM (#8515862)

I can't see that in the spec, so no. Like most things, if you don't like an app, you can revoke it's privileges and uninstall it.

The questions you keep asking are basic things solved by reading the article - you seem to have concerns, but you haven't done the minimum amount of work necessary to determine whether your concerns are valid.

[ Parent | on HN ]

Re:Push API – W3C Working Draft by domenicd on Monday October 27, 2014 @01:39PM (#8516923)

Permissions are per-origin.

[ Parent | on HN ]