Path: csiph.com!aioe.org!.POSTED!not-for-mail From: Richard Maher Newsgroups: comp.os.vms,comp.lang.javascript,comp.lang.java.programmer Subject: Re: Firebase Cloud Messaging (FCM) blows the W3C/IETF Success Prevention Depts out of the water! Date: Wed, 5 Apr 2017 20:49:48 +0800 Organization: Aioe.org NNTP Server Lines: 43 Message-ID: References: NNTP-Posting-Host: jOhPn0KFjrxwuMc9OPMmCw.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.os.vms:66587 comp.lang.javascript:32939 comp.lang.java.programmer:36428 On 28-Mar-17 7:14 PM, Richard Maher wrote: > Broadcast Messaging and Topic Based subscription is now available to > your WebApp just like native Apps thanks to FCM. > > https://firebase.google.com/docs/cloud-messaging/js/send-multiple > > I am absolutely ecstatic about this, as we all should be, and equally > grateful to FCM for having managed to bypass the recalcitrance and sheer > bloody-mindedness of spec-authors to provide functionality that everyone > outside the ivory-towers was begging for. > > I thought WhatWG was set up to challenge the delusional elite a la mode > de HTML5? Why the silence? > > Anyway rejoice and be glad as Native Apps have one less stick to beat us > over the head with. And you Firefox fans are no longer stuck with > Mozilla's third-rate AutoPush! > > Now if we can only get background geolocation with ServiceWorkers > nothing can stop WebApps: - > https://github.com/w3c/ServiceWorker/issues/745 > > Happy Days!!! > > Cheers Richard Maher > > PS. The cognoscente are once more assembling on April 4-5 for a Japanese > junket on ServiceWorkers to yet again wax bollocks on "offline first" :-( > > Please lobby the names that can be found in the hall of shame here: - > https://github.com/w3c/ServiceWorker/issues/1053 For those hoping that W3C/IETF will wake up to the background geolocation requirement, I'm afraid the answer is "Not this year" :-( https://github.com/w3c/ServiceWorker/issues/1053 Still, at least the sponsors are getting value for their money and quality F2F time in Tokyo: - https://twitter.com/jaffathecake/status/848018836922093570 You just can't be that productive via email or a conference call!