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

Push Notification on Google-Free Smartphones #12490

Closed
4 tasks done
genofire opened this issue Oct 3, 2022 · 6 comments
Closed
4 tasks done

Push Notification on Google-Free Smartphones #12490

genofire opened this issue Oct 3, 2022 · 6 comments

Comments

@genofire
Copy link

genofire commented Oct 3, 2022

Google independent generic push system:
https://unifiedpush.org/

Switch to UnifiedPush with FCM embedded support:
https://unifiedpush.org/developers/embedded_fcm/

@genofire
Copy link
Author

genofire commented Oct 4, 2022

Okay, to close an issue with no text or commant from an maintainer is also a statement.

@greyson-signal
Copy link
Contributor

Apologies for the lack of comment, but we don't anticipate doing this work. We reserve github for bug reports not feature requests, which is why it was closed before.

Signal does work without play services. What confuses people is that we do not guarantee that Signal works with fake play services. When there's no play services installed at all, we will fallback to a persistent websocket connection to deliver notifications.

@genofire
Copy link
Author

genofire commented Oct 5, 2022

I understand that this is not direct an bug, i could formulate that as an Bug: e.g. Websocket is not (re)connected after a while.

Do you have not a default snippet for such closing?

In the End, i not feeling understand:

  • Forum has not get any official answer
  • linked Issue was not closed, because the Opener do not believe that Signal would do anything
  • this Issue close without commant
  • you call an OpenStandard as fake play service (see next part)

We do not talk about fake play services. There is an official standard called UnifiedPush, for Applications and ApplicationServer. So not every Application needs to create a Websocker, SSE, HTTP-Poll or any TCP connection (together with an Notification).

UnifiedPush has a library where is FCM inside, so that if the user has not installed/setup any UnifiedPush Provider. It will fallback to the Google Play Service.

So please do not call it fake play service, because it does not try to reimplement google - it is an open standard for push notification (which works outside of android, like Linux also).
It would be really nice, that Signal use OpenStandards for Notification and do not use propriare (Google and own Websocket implementation).

@metaphys
Copy link

I confirm what genofire is saying, this isn’t a fake gplay but an open implementation. This means also that users could then choose their notification server or even self-host it. (nextcloud for instance offer this functionnality)

@rightsaidfred99
Copy link

One wonders about open source software that still uses proprietary standards. a shame.

@uberhalit
Copy link

Proof enough that the original Signal app cannot be trusted. Use Molly instead: https://github.com/mollyim/mollyim-android

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

No branches or pull requests

6 participants