So I’m developing a mobile client using React Native, where I’m utilizing Lemmy’s messaging functionality as well. This makes it extremely crucial to have notification support (including push notifications).
How are you guys dealing with this problem? This is what I think an elegant solution could look like. We would need to achieve two things:
- Bring back websockets only for notifications by directly changing lemmy server side code.
- Find where the email notification code is at, and simply implement expo notifications there.
Whaddya think?
Ideally it would support WebPush which would allow your app to register with any push notification service that supports WebPush.
WebSockets would drain battery and also add a lot of load on the servers to handle all those connections. Implementing specific notification services directly on Lemmy isn’t quite where it belongs. Plus you don’t want all Lemmy admins to have to register to Apple Push and Google’s FCM and potentially others. With WebPush you can have your own server as a relay and then dispatch to expo/APN/FCM as needed.
There’s a discussion here https://github.com/LemmyNet/lemmy/issues/2631
@UraniumBlazer@lemm.ee
Other apps are currently just polling for notifications every hour or so, works fine for now
Oh, so does it already do this?
I don’t think it supports WebPush at the moment, no. But it would be the technically correct way to implement this. It’s an open standard that’s not tied to any particular company and ecosystem.
Sorry, I know I should look this up (trust me, I tried but couldn’t find an answer), but does Novu use the webpush protocol/standard/whatever it is? I’m interested in Novu as it does seem to be supporting Expo notifications.