[Django] #35391: Announce: Intent to drop FCM/GCM token support from PyWebpush

13 views
Skip to first unread message

Django

unread,
Apr 19, 2024, 1:52:16 PM4/19/24
to django-...@googlegroups.com
#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.

Django

unread,
Apr 19, 2024, 4:34:07 PM4/19/24
to django-...@googlegroups.com
#35391: Announce: Intent to drop FCM/GCM token support from PyWebpush
------------------------------------+--------------------------------------
Reporter: JR Conlin | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 5.0
Severity: Normal | Resolution: invalid
Keywords: webpush, web push, | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):

* resolution: => invalid
* status: new => closed

Comment:

I'm not sure if and how this is related with Django. Django doesn't use
`pywebpush`.
--
Ticket URL: <https://code.djangoproject.com/ticket/35391#comment:1>
Reply all
Reply to author
Forward
0 new messages