News for hackers. Stuff that matters.
Re:Push API – W3C Working Draft by SynchrotronZ on Monday October 27, 2014 @03:32AM (#8514304)
I'm... not sure I want this. It sounds pretty useful/fun form a programmers perspective.

But from an end-user perspective I fear that it will lead too various "features" hogging resources. I would assume I could block them client-side, but I'm also the family-tech and quite frankly I don't expect my grandparents to do the same.

Re:Push API – W3C Working Draft by mmahemoff on Monday October 27, 2014 @03:45AM (#8514333)
"User agents must not provide Push API access to webapps without the express permission of the use"

I share your concern. but I share a great fear that web apps will become increasingly irrelevant if they remain just documents that can't do anything when they're not explicitly in a running tab/window.

The permission requirement is the same one that allows for local storage, which could have caused great problems, but has so far held up well.

Re:Push API – W3C Working Draft by dspillett on Monday October 27, 2014 @08:18AM (#8515033)
> The permission requirement is the same one that allows for local storage

Assuming this does not allow the push of UI interaction, then yes. If it would allow UI responses to be pushed then we would be one XSS vulnerability or "uneducated users" away from a new set of exploits for forcing pop-under advertising , and other potentially more insidious problems, through.

Local Storage and Index DB are storage only so the only attack routes are DoS-due-to-disk-full-errors which is generally less attractive (you can make more money pushing stuff to people than pushing people off the network).

Re:Push API – W3C Working Draft by travisby on Monday October 27, 2014 @07:16AM (#8514824)
And the Ask toolbar doesn't get installed without expressed permission, either.
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?
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.
Re:Push API – W3C Working Draft by nailer on Monday October 27, 2014 @08:36AM (#8515090)
It's permission based. Read the linked spec.
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?

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.

Re:Push API – W3C Working Draft by domenicd on Monday October 27, 2014 @01:39PM (#8516923)
Permissions are per-origin.
Re:Push API – W3C Working Draft by vbezhenar on Monday October 27, 2014 @03:45AM (#8514334)
Safari supports push notifications from websites for a while. I've found it convenient for the news websites I often visit just to check for new content. It's like RSS integrated into OS. One can misuse it, but generally it's useful.