We suggest adding a new custom /send_push/ endpoint to djangoldp-notification, to receive the actual notification data. This method will look up a user based on the ID provided in the notification request, and trigger the in-browser notification by calling the send_user_notification method from django-webpush. We will unit test to validate these assumptions.
> Send push notifications
>
> We suggest adding a new custom /send_push/ endpoint to djangoldp-notification, to receive the actual notification data. This method will look up a user based on the ID provided in the notification request, and trigger the in-browser notification by calling the send_user_notification method from django-webpush. We will unit test to validate these assumptions.
Ripped from https://git.startinblox.com/djangoldp-packages/djangoldp/issues/338.
Question: Is there one VAPIDKeySet instance per Hubl instance or per DjangoLDP backend? If user1 is on HublA and user2 is on HublB, do we have VAPIDKeySet1 and VAPIDKeySet2? Or just VAPIDKeyset1 for everything?
Question: Is there one `VAPIDKeySet` instance per Hubl instance or per DjangoLDP backend? If user1 is on HublA and user2 is on HublB, do we have VAPIDKeySet1 and VAPIDKeySet2? Or just VAPIDKeyset1 for everything?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Ripped from https://git.startinblox.com/djangoldp-packages/djangoldp/issues/338.
Question: Is there one
VAPIDKeySetinstance per Hubl instance or per DjangoLDP backend? If user1 is on HublA and user2 is on HublB, do we have VAPIDKeySet1 and VAPIDKeySet2? Or just VAPIDKeyset1 for everything?