вт, 2 окт. 2018 г. в 19:47, Sam Whited <s...@samwhited.com>: > > On Tue, Oct 2, 2018, at 09:08, Ненахов Андрей wrote: > > Could someone please explain logic behind XSF workflow? 'Inactivity'? How > > exactly do you measure that, no updates to XEP? > > That's correct, no updates for 12 months when in the experimental stage. > > > We use XEP-0357 to send notifications to Xabber iOS, Web and Android, and > > it's kinda not ok for it to be just gone for no reason. > > It's not gone, the link will remain available and deferred just means "we're > not sure if anyone is working on this or advocating for its advancement", it > doesn't necessarily mean "don't use it". If you'd like to nominate it for > advancement to draft or make changes, this one definitely seems widely used > and would probably be a good candidate.
Ok, I nominate XEP-0357 for advancement to draft status. It is the only standard way to deliver push notifications to FCM, APNS and possibly to other push services. There are existing server and client implementations. Is this enough, or is there some sort of special procedure for a nomination? -- Ненахов Андрей Директор ООО "Редсолюшн" (Челябинск) (351) 750-50-04 http://www.redsolution.ru _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
