Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Please consider using UnifiedPush for notifications as a Push Provider #9337

Closed
emorrp1 opened this issue Feb 6, 2021 · 4 comments
Closed

Comments

@emorrp1
Copy link

emorrp1 commented Feb 6, 2021

I would like to be able to use android without google services. Currently notifications must use FCM unless each app developer hosts a notification gateway which drains battery. I suggest using UnifiedPush, the community successor to OpenPush. Although UnifiedPush is (really) brand new, I'm not aware of any other app-independent implementation.

The only currently available UnifiedPush app is FluffyChat, but there is a request for Element support and it would be neat if the user didn't have to host yet another personal server. I believe the technical approach would be for synapse to act as a Push Provider, since it's already an always-online service and then a "distributor" app could use the homeserver url as a backend.

@tulir
Copy link
Member

tulir commented Feb 6, 2021

This doesn't sound like a Synapse issue. If the existing push gateway system doesn't work, there needs to be a spec proposal before Synapse can be changed.

@reivilibre
Copy link
Contributor

This seems more like something for Sygnal or perhaps another push gateway implementation still.

@Sorunome
Copy link
Contributor

Sorunome commented Feb 6, 2021

The push gateway can already be anything, see matrix-org/matrix-spec-proposals#2970 as proposal to remove the path requirement.

@emorrp1
Copy link
Author

emorrp1 commented Feb 6, 2021

Ah yes, since Matrix already has a defined notifications endpoint, this isn't actually needed. Thanks @tulir

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

No branches or pull requests

4 participants