-
-
Notifications
You must be signed in to change notification settings - Fork 221
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃摬 Unifiedpush #2213
base: master
Are you sure you want to change the base?
馃摬 Unifiedpush #2213
Conversation
Signed-off-by: Jindrich Kolman <kolman.jindrich@gmail.com>
Signed-off-by: Jindrich Kolman <kolman.jindrich@gmail.com>
Signed-off-by: Jindrich Kolman <kolman.jindrich@gmail.com>
Signed-off-by: Jindrich Kolman <kolman.jindrich@gmail.com>
Lint
SpotBugs (new)
SpotBugs (master)
Lint increased! |
Hey @koo5, thank you very much for the time and effort gone into this. We would love to have this implemented in Talk, as it can help our users become more independent from Google infrastructure. Can you write some instructions on how to test this (server + android setup)? |
You can create an ancestor class in the |
Unified push is interesting, but I think that this is the wrong approach. There are more than one option for not-google push message delivery, another that is probably more helpful is https://gitlab.com/Nextcloud-Push which operates server side as a plugin to nextcloud itself, meaning that you install the proxy into your nextcloud instance, and then Nextcloud can push the messages directly to the client itself. Another option would be to work somehow with Nextcloud Files HPB. So the problem then becomes that this approach would lead to the need to publish multiple separate variants of Nextcloud Talk, whereas in my view, a more ideal solution would be to be able to support all of the different push message delivery mechanisms within the SAME variant. Obviously a google variant has to be kept separately from an "everything else" variant in order to include on F-Droid, but in my opinion, it would be more proper for all of the additional delivery mechanisms to be available on BOTH variants. The user should be asked which push delivery mechanism to use during initial setup. |
Sorry for potentially widening the field of option, but linking to the discussion of the Android files app regarding supporting an alternative push solution, see also: nextcloud/android#5510 as well as nextcloud/android#8684 |
This PR adds a new build variant: "unifiedpush".
uses https://unifiedpush.org/developers/android/
works with Gotify-UP - with a yet-unreleased push server
problems:
feedback, ideas and corrections appreciated!