#35391: Announce: Intent to drop FCM/GCM token support from PyWebpush
-------------------------------------+-------------------------------------
               Reporter:  jrconlin   |          Owner:  nobody
                   Type:             |         Status:  new
  Uncategorized                      |
              Component:             |        Version:  5.0
  Uncategorized                      |
               Severity:  Normal     |       Keywords:  webpush, web push,
           Triage Stage:             |      Has patch:  0
  Unreviewed                         |
    Needs documentation:  0          |    Needs tests:  0
Patch needs improvement:  0          |  Easy pickings:  0
                  UI/UX:  0          |
-------------------------------------+-------------------------------------
 Hi all,

 Hopefully, this is not a critical issue, but I wanted to announce that [I
 plan on dropping FCM/GCM token support](https://github.com/web-push-
 libs/pywebpush/pull/163) from pywebpush. This should not impact sending
 Push Notifications, since that uses a different mechanism. Legacy FCM/GCM
 support was transitional and Google has [announced that it will terminate
 support](https://firebase.google.com/docs/cloud-messaging/auth-server
 #authorize-legacy-protocol-send-requests) for the feature in June of this
 year.

 I want to give y'all a proper heads up just in case that you might be
 using it.

 If I don't hear back or there's no objection, I plan on merging the PR on
 or about Apr 24.

 Thanks!
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35391>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018ef77cbb06-85f9e174-332c-4562-bcb7-015ad8be2644-000000%40eu-central-1.amazonses.com.

Reply via email to