Support 3rd Party Push Notification Services such as Pushy
Google Play Services and GCM is blocked in China. This means that users that are not on VPN cannot get push notifications. The only known workarounds that I know of are using a 3rd party Push Notification service such as Baidu (http://push.baidu.com/doc/android/api) or Pushy (https://pushy.me/) or to run your own push notification service. I wish I didn't have to make this suggestion, but MatterMost is severely crippled by this and I dont see the geopolitics changing anytime soon.
Nick
shared this idea
-
François Borowiec commented
From https://github.com/mattermost/mattermost-mobile/issues/6673
User rudism's comment:
Supporting unified push would have several benefits:
Push notifications would become available on devices without Google Services.
Client builds from 3rd parties (such as F-Droid) would gain push notification capabilities.
Team Edition self-hosters could also self-host push servers without needing to compile their own client apps.
Opening up to other 3rd party unified push providers would reduce the burden/dependency on the official Mattermost TPNS.
Unified push is already used and battle-tested by many other FOSS projects (clients for Matrix, Mastodon, NextCloud, and so on). -
Raphaël
commented
-
Raphaël
commented
Somehow related: the mobile application currently bundles a mattermost.com specific Google GCM/Firebase key.
This implies that any other Mattermost instance (providing a difference push-proxy) needs a recompiled corresponding mobile application.The possibility to override google-services.json file at runtime would remove this burden making the official Mattermost mobile application ubiquitous and compatible with any other (push-enabled) instance.