CloudServices/Notifications/Push: Difference between revisions

m
No edit summary
 
(5 intermediate revisions by one other user not shown)
Line 34: Line 34:
A user no longer wishes to receive alerts for a given notification. The user  
A user no longer wishes to receive alerts for a given notification. The user  
loads their admin and control panel and disables the queue. The user can either temporarily silence a given notification queue (in which case, notifications are still collected, but not immediately alerted to the user) or delete the queue (in which case, incoming notifications are rejected, existing notifications are removed, and the queue is no longer associated with the user.)
loads their admin and control panel and disables the queue. The user can either temporarily silence a given notification queue (in which case, notifications are still collected, but not immediately alerted to the user) or delete the queue (in which case, incoming notifications are rejected, existing notifications are removed, and the queue is no longer associated with the user.)
==UX and Design==
[[Services/Notifications/Push/UX]]
==Etherpads==
Security Review:
https://etherpad.mozilla.org/NotificationsSecReview
UX and Design:
https://etherpad.mozilla.org/NotificationsDesign
https://etherpad.mozilla.org/NotificationsUsers - Desires and Detractors for various parties associated with Notifications (End User, Notification Provider, etc.)
Stand alone demo server:
https://etherpad.mozilla.org/NotificationsInABox
AWS Websocket maximum connection count discoveries:
https://etherpad.mozilla.org/AWS-Socket-Discoveries
canmove, Confirmed users
1,173

edits