aes128gcm WebPush Support
Posted: 2019-01-30, 20:49
I just started looking into this stuff, and sorta glad I waited with the mess this standard is in. It looks like the 8188 and 8292 whitepapers are finalized, and somehow VAPID survived it all...
And so I noticed, PushCrypto.jsm is looking a bit out-of-date now. I'd write a pull request myself, but I'm writing the server side right now and for the life of me, I can't get Google to play nice (the all-too-vague UnauthorizedRegistration error), so I apparently have more to learn before I go writing or porting an agent's implementation. It should only take four or five tweaks to get it done, and in all honesty it seems like aesgcm128 could be phased out... and probably aesgcm as well (pretty sure the drafts expired on it).
I was also sorta wondering, do you have plans to make a subscription service separate from Mozilla and enable Service Workers and Push by default, or is Pale Moon gonna stay out of the webapp fad?
And so I noticed, PushCrypto.jsm is looking a bit out-of-date now. I'd write a pull request myself, but I'm writing the server side right now and for the life of me, I can't get Google to play nice (the all-too-vague UnauthorizedRegistration error), so I apparently have more to learn before I go writing or porting an agent's implementation. It should only take four or five tweaks to get it done, and in all honesty it seems like aesgcm128 could be phased out... and probably aesgcm as well (pretty sure the drafts expired on it).
I was also sorta wondering, do you have plans to make a subscription service separate from Mozilla and enable Service Workers and Push by default, or is Pale Moon gonna stay out of the webapp fad?