Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notification Server #1318

Open
1 of 3 tasks
nikkothari22 opened this issue Feb 7, 2025 · 1 comment
Open
1 of 3 tasks

Notification Server #1318

nikkothari22 opened this issue Feb 7, 2025 · 1 comment
Assignees

Comments

@nikkothari22
Copy link
Member

nikkothari22 commented Feb 7, 2025

We need a notification relay server that is tailored to Raven's use case.

  1. Topic based notifications for channels work, but also send notifications to the sender of the message. Notifications are shown for messages sent by the sender in channels #813 and Notifications - too many #1274
  2. We would like users to be able to decide which kinds of notifications they would want to receive on which device (phone vs laptop). This can only be done if we store notification tokens on the site instead of on the relay.
  3. For privacy, it's best to not store any user information on the relay server. Since user ID's are defaulted to email addresses in Frappe, we cannot store user IDs on the relay server - instead the relay server should just have an API to take in the list of FCM tokens and the message content - this makes it completely anonymous. We can set pricing plans based on max number of devices the notification is sent to instead of users.

To implement this:

Copy link

linear bot commented Feb 7, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant