<story><title>Push API – W3C Working Draft</title><url>http://www.w3.org/TR/2014/WD-push-api-20141007/#example</url><text></text></story><parent_chain></parent_chain><comment><author>mike-cardwell</author><text>This should have mandatory crypto built in from the beginning so that third party push providers can be used without causing privacy&amp;#x2F;security concerns.&lt;p&gt;The browser and the web server should negotiate an encryption key, or set of encryption keys during setup, and any push messages signed and encrypted. That way, any third party push provider can&amp;#x27;t inpect the messages.&lt;p&gt;Also, pigs should learn to fly.</text></comment>
<story><title>Push API – W3C Working Draft</title><url>http://www.w3.org/TR/2014/WD-push-api-20141007/#example</url><text></text></story><parent_chain></parent_chain><comment><author>Beltiras</author><text>It&amp;#x27;s great that there are some standardization efforts in this space but for this to be useful we would need wide coverage of clients implementing it.  Stuck using websockets for the next decade I suppose ....</text></comment>