Matrix Notifications Existential Crisis
-
I'm attempting to port a matrix client, and trying to add notifications.
I noticed that cinny (cinny-click-packaging) uses the url "https://push.ubports.com:5003/_matrix/push/v1/notify" (which is awesome btw).
BUT, I cannot find a single shred of evidence that this api exists anywhere, yet I can see its live and working because it gives me a 400 error when pinging it (also the fact that cinny works).
I've looked through the documentation, the code for the lomiri-push-service (which I'm guessing is the server implementation), and just googling "ubports" and "matrix" brings up nothing.
I've also attempted to just steal the cinny code, but its not working for me... And using the regular push notification example code doesnt work for this api (but does for the normal one).
Am I missing something super obvious? Where is the documentation!?
-
The docs you linked has the API on sending a push notification from the server. The URL used in Cinny seems to be a modified or specific one. The thing is, push notifications should be implemented in the server. They're supposed to be sent by the server. The app just has to handle them which is explained the linked docs. Not sure what Cinny exactly does. It might be doing a hacky approach of sending notifications by the app itself or UBports actually has a configuration for matrix push notifications and you may need to contact them about it.
-
@kugiigi Thanks for the reply.
Perhaps I should have given a little more context. Matrix (server protocol) has an option for custom push notification apis. What Cinny seems to be doing, is sending the api url to the server, which the matrix server then uses to send the push notifications.
Evidently UBports realizes this use-case and created an endpoint to accept the matrix-formatted api call. But I cannot find any documentation.
Does anyone know anything about this?
Or who specifically to contact?
-
@ari I see. That makes more sense. I guess the developer of Cinny or Florian.